About
Courses by Annyce
-
Introduction to Career Skills in Software Development2h 2m
Introduction to Career Skills in Software Development
By: Annyce Davis
Articles by Annyce
-
Speaking at Tech Conferences: What You Should Know
Speaking at Tech Conferences: What You Should Know
I started speaking at Technical Conferences a year ago and I’ve learned so many things since then. Things about the…
7 Comments
Activity
54K followers
-
Annyce Davis shared thisA little while ago, I shared that I built an AI tool recommender to help me decide when to use Copilot, Codex, Ollama, Aider, or ChatGPT. At the time, I thought I was solving a tool-selection problem. I wasn’t. Token limits were quietly changing the way I architect my entire AI workflow. I started paying more attention to context size, long-running sessions, terminal output, model choice, local compute, and whether every task really needed the most capable model available. And the interesting part? I can actually see the difference in my token usage. I wrote up what I’ve learned in Tokens Rule Everything Around Me — including the routing strategy I’m using now and why I’m becoming much more interested in context engineering than prompt engineering. https://lnkd.in/ecKpn8-T C.R.E.A.M., apparently, has a 2026 edition. 😅 #AIEngineering #ContextEngineering #DeveloperProductivity #GitHubCopilot #AIWorkflow
-
Annyce Davis shared thisI’ve been getting much more deliberate about which AI tool I use for which task. 🤖 Not every coding task needs the most capable model. Not every repo can be sent to every tool. And AI usage isn’t an unlimited resource. So I built an AI skill that recommends the tool + model I should use based on the work I’m about to do. It considers things like privacy constraints, whether I’m working across one or multiple repos, the type and complexity of the task, cost, and which models are actually available. In this example, I wanted to update a few files in an enterprise repo. The skill eliminated tools that weren’t appropriate for that code, scored the remaining options, and recommended GitHub Copilot + Claude Sonnet 5. For another task, the answer might be Codex, Aider + Ollama, or something else. I used to ask: “Which AI coding tool is best?” Increasingly, I think the better question is: “What’s the right AI resource for this particular job?” I’m starting to think of this as AI workload routing — matching the work to the right level of intelligence, context, privacy, and cost instead of defaulting to the same tool every time. 🛠️ Still experimenting with the framework, but it’s already changing how I use AI. #AIEngineering #SoftwareEngineering #DeveloperProductivity #AIWorkloadRouting
-
Annyce Davis shared thisAnnual planning and budgeting need to die. 😬 Well, not planning itself. But the idea that we can set priorities months in advance, lock in the budget, and expect those decisions to still make sense when the world changes. The speed of change makes that harder to defend every year. I wrote about what I think needs to change. 👇🏾 https://lnkd.in/eHirRTSa #Leadership #Strategy #Planning
-
Annyce Davis posted thisI built a tool to track my time at work. Let's just say I got roasted. 😅 I used to think I knew where my hours actually went. So I got suspicious, and instead of doing the healthy thing and just noticing, I built a local-first pipeline that tracks my activity and generates daily and weekly reports. All on my machine, no data leaving the laptop. Then it handed me the receipts: 🔀 416 context switches in one week — 204 app-hops a day, when the healthy max is 150. I was tool-hopping like it was cardio. 📅 8 meetings a day. 17 back-to-back. 22 I "multitasked through" (read: answering Teams while nodding on camera). 🎯 Average deep work session: 10 minutes. Turns out you can't think a big thought in the gap between two calendar invites. 🌙 871 minutes of weekend work. Recommended max: 60. My own laptop gently suggested I remove email from my phone. Bold. Here's the part I didn't expect: none of it felt really like a problem in the moment. Every switch was "just checking one thing." Every weekend hour was "just wrapping things up." The data didn't lie — my sense of my own week did. And the lesson wasn't "work harder." My best week wasn't the busiest one — it was the one with fewer switches and longer blocks of focus. The bottleneck was never effort. It was fragmentation. More activity doesn't fix that. 🤷🏾♂️ Better signals do. You can't improve what you can't see, and most of us genuinely can't see how we spend our time. Measuring it is humbling, and a little addictive. I'd love to hear — what would your data say about you? Built with Python, SQLite, and a decent amount of self-awareness. 🐍 #Leadership #EngineeringLeadership #DeepWork #Productivity #BuildInPublic #Communication
-
Annyce Davis shared thisI used to believe that if you did great work, people would notice. Experience has taught me otherwise. I've coached engineers who were far more capable than their résumés suggested. I've seen leaders struggle to get buy-in for great ideas because they couldn't clearly communicate the "why." And lately, as I've been building AI tools, I've realized something unexpected... AI has the same problem. It can only work with the signals we give it. The better the signals, the better the outcomes. That realization connected three things I've been thinking about a lot lately: - Making your impact visible - Learning to adapt your communication to different people - Watching AI expose communication gaps that were always there The common thread isn't AI. It's communication. The engineers and leaders who stand out over the next few years won't necessarily be the ones who know the most. They'll be the ones who make their thinking, decisions, and impact easier for others to understand. I wrote more about that in my latest newsletter, Building Signals 👉🏼 https://lnkd.in/em7iERDe I'd love to hear your thoughts. #Leadership #EngineeringLeadership #ArtificialIntelligence #CareerGrowth #Communication #InvisibleSignals
-
Annyce Davis shared this🚨 I've seen brilliant engineers get overlooked. Not because they lacked capability. Because they sent weak signals. A resume that hides impact. An interview answer that buries ownership. A promotion packet full of activities instead of outcomes. People can't evaluate what they can't see. That's the idea behind Invisible Signals™: understanding the signals we send through our resumes, interviews, leadership communication, and everyday work. 📝 https://lnkd.in/evTPaqRk What's the strongest career signal you've seen someone send? 👇 #SoftwareEngineering #EngineeringLeadership #CareerGrowth #Leadership #TechCareersInvisible Signals: Why Smart Engineers Still Get OverlookedInvisible Signals: Why Smart Engineers Still Get Overlooked
-
Annyce Davis reposted thisAnnyce Davis reposted this🚨 Save the date: DevFest DC is back on Friday, August 28, 2026!! After 800 attendees and 30+ sessions made last year's DevFest DC one of the most talked-about tech gatherings in the DMV, we're doing it again. This year we are going bigger, deeper, and with even more of what made 2025 special. Whether you ship AI features, vibe code, run cloud infra, or are just learning your first framework; there’s a seat for you on August 28. 🗓️ Friday, August 28, 2026 · 9:00am 📍 Fuse at Mason Square, Arlington VA 🎟️ Registration opens Tuesday, May 26 🎤 Speaker applications opening soon next week Follow this page to be the first to know when tickets and the CFP go live! Google Antonio Zugaldia Jared Sheehan Annyce Davis Chida Sadayappan Rachel Koretsky Darius Clair Google Developers Group Naveen Nigam Google Developers Group #DevFestDC #GDG #DCtech
-
Annyce Davis liked thisAnnyce Davis liked thisAt Android Dev Summit in Mountain View this year, I'm helping out with a hands-on workshop using the Jetpack XR SDK we're running. There's also a whole track of XR talks, hands-on demos, a chance to connect with the team, & much more! Space is limited, so RSVP right away if you can make it: https://lnkd.in/e2YgaZNi There's also an event on Oct 28th in London for those that can't make it to Mountain View: https://lnkd.in/e5jYdHPv We won't be doing the workshop there, but Egor & Jay are going to give a talk on generating procedural 3D geometry that I highly recommend (plus way more exciting talks and chances to meet great people) 😎 #AndroidDevSummit
-
Annyce Davis reacted on thisAnnyce Davis reacted on thisHi friends, over the last 2 years I had the once in a lifetime opportunity to not only work at Airbnb but lead the rollout of AI to thousands of developers. I came to work excited everyday to see folks learn a new way to code and do their jobs. This is my last week wearing that hat as I’m leaving for a much needed career break. It’s wild to look back at what is now a 20 (well 19) year career that started in web, hit its stride in mobile and finally landed in the wild world of dev prod and AI My plan is to spend the next few months enjoying life outside of ai, mostly with my wife and two kids. Past that who knows! Ping me if you’re doing anything fun that helps humans ❤️
-
Annyce Davis reacted on thisAnnyce Davis reacted on thisAah, I am more than grateful and am just reflecting on an incredible experience speaking at LeadDev New York! It was a privilege to take the stage and share my thoughts on building a security-first framework for evaluating AI in software engineering. The energy from the engineering leadership community was truly inspiring. A massive thank you to my VP and Director, for championing my work and approving this talk; having leadership support to share these insights makes all the difference. While the slides for this specific presentation won't be made publicly available, I am so grateful for the phenomenal feedback and the deep, thought-provoking conversations I had with so many of you afterward. Hearing how the framework resonated with your own engineering and AI integration challenges was the absolute highlight of the event. Thank you to everyone who attended, asked questions, and shared their perspectives. Let’s keep the conversation going! Also, thank you to Annyce Davis for your support and bringing be along. #LeadDev #SoftwareEngineering #ArtificialIntelligence #EngineeringLeadership
-
Annyce Davis liked thisAnnyce Davis liked thisThis is a Senior Principal Engineer at AWS. In just 20 minutes, she explains why most teams get 10-20% from coding agents while Amazon pilots hit a median of 4.5x, and sometimes even more than 10x. Amazon gave 50 regular teams the same AI tools. The teams that just added the tool to their old process barely sped up. The teams that changed how they worked shipped much faster. The difference: they stopped pairing with the agent all day. They set the work up, let it run, and often ran more than one agent at a time 🤖 Those teams did 5 unglamorous things: → Write down what used to live in Slack → Slow down to make the repo agent-ready → Give agents a way to self-check → Lock intent in a spec before generating code, and → Move tests left so the loop is fast enough to leave alone. Together with this playbook, you can put that workflow into Claude Code & turn it into your Chief of Staff (specs, context, & parallel threads instead of one messy chat): https://lnkd.in/dW9K8hDq If you’re building AI agents, this is a must-watch. P.S. also check out How to Use Jev AI: The Complete Guide to TypeSafe's System One Model 🤖: https://lnkd.in/dxNeiCaA
-
Annyce Davis liked thisAnnyce Davis liked thisOne thing I've noticed since I started working more with AI coding agents: My development process changed more than my coding speed. I recently looked at my personal GitHub activity through AgentStats: 🔗 https://lnkd.in/gdaJFjup The numbers are interesting, but I don't think “more lines of code” = “more productivity.” What actually changed was the development loop. Today, I'm increasingly moving beyond simple AI-assisted coding towards: → Agent loops for iterative implementation, testing and validation → Spec-driven development, where agents work from well-defined requirements and acceptance criteria → Autonomous agentic workflows that can plan, implement, test and refine with minimal intervention → Agentic teams where multiple specialized agents collaborate across different stages of development → Automating workflows from (idea → specification → implementation → testing → review → delivery) → Using agents for codebase exploration, debugging, refactoring and evaluating implementation alternatives The interesting shift isn't simply: “AI writes code faster.” It's becoming: “How much of the software development lifecycle can be turned into a reliable agent loop?” And that changes the role of the engineer. Architecture, context, constraints, validation and judgment still matter - arguably more than ever. For me, that's what AI-native development is starting to look like: not replacing software engineering, but redesigning the way we build software. I'm curious to see how far these agentic workflows can evolve over the next year. #AI #AIAgents #AIEngineering #AgenticAI #SoftwareEngineering #GenerativeAI #DeveloperTools #SpecDrivenDevelopment
-
Annyce Davis liked thisAnnyce Davis liked thisMy #Leon moment at Infosys Confluence 2026! Sanjay S. and Rakesh Babu Great sessions with one of our partners.
-
Annyce Davis liked thisAnnyce Davis liked thisExcited to be attending my first NBMBAA conference and representing Ford. See you there! #weareFord #NBMBAA #Pivot
-
Annyce Davis reacted on thisAnnyce Davis reacted on thisMy coach pulled up my LinkedIn earlier this week and got quiet for a second. Then she said, wait, your last post was over a year ago? I laughed, but she was right. A year. I didn't plan it that way. I was just heads down, testing, breaking things, fixing things, showing up for the actual job. Somewhere in there I decided the work would speak for itself. Turns out it doesn't, not on its own. People can't see what they can't see. So I'm easing back in. Slowly, and probably a little rusty at this part. If you've gone quiet for a stretch too, was it on purpose, or did a year just happen?
Experience & Education
Recommendations received
12 people have recommended Annyce
Join now to viewOther similar profiles
Explore more posts
-
Kay Werner
👩💻 Are Zoox and Waymo Automotive Companies or Tech Companies? Five years ago, I made a significant shift in my career: moving from supporting some of the world’s most innovative high-tech customers to working in the automotive industry. It wasn’t just a change of industries— it was stepping into a space where hardware meets AI, where vehicle safety meets software reliability, and where two massive industries are colliding to redefine mobility. As I immersed myself in this new world, one question kept coming up — both for the companies leading the charge and for professionals like me: 🤔 Are companies like Zoox and Waymo automotive companies, tech companies, or something entirely new? Zoox, acquired by Amazon in 2020, is building a fully autonomous vehicle from the ground up — not retrofitting existing models. This places it firmly in the automotive realm for engineering, safety, and manufacturing. But its true edge is its software stack: perception, localization, motion planning, and fleet orchestration — capabilities traditionally owned by robotics and AI firms. Waymo, born from Google’s self-driving project, took a different approach. By partnering with OEMs like Jaguar and Chrysler, it integrates its autonomy platform into existing vehicles. This positions Waymo less as a manufacturer and more as a mobility technology platform, akin to how Android powers various smartphone brands. 🤔 Why Does this matter you might ask? This distinction influences how these companies operate: 👉 Capital Structure: Automotive requires heavy investment in factories and regulatory approval; tech prioritizes software, cloud, and data infrastructure. 👉 Business Models: Automakers sell vehicles; tech companies license platforms or charge per use. 👉 Regulation: Automotive focuses on crash safety and production standards; tech focuses on cybersecurity, AI ethics, and data compliance. 👉 Talent: Automotive attracts mechanical and operational expertise; tech attracts AI, software, and cloud talent. Zoox integrates both worlds — building vehicle + software. Waymo focuses on scaling autonomy software across partners. 🤔 The real answer may not be “automotive” or “tech.” Both companies are moving toward Mobility-as-a-Service — deploying autonomous fleets that could reshape urban transport. Ownership gives way to orchestration: fleets, logistics, and city-scale mobility infrastructure. The automotive and technology industries are no longer separate lanes — they’re converging into a new mobility ecosystem. Zoox and Waymo sit at the center of this transformation, challenging legacy categories. ✅ The question of automotive or tech? is certainly outdated. The answer might be: both — and something more. #AutonomousVehicles #MobilityInnovation #AutomotiveIndustry #MobilityTech #SoftwareDefinedVehicles #FutureOfTransportation #MobilityAsAService #InnovationStrategy
-
Esco Obong
I’ve been running a non profit to support black software engineers in interview prep and career growth for the last 6 yrs. Today we launch a publication where members of our 20k community contribute articles sharing deep technical insights. The first article is by Aza Walker, Jr. about how he built a Game Boy Color Emulator with Rust. Check it out and subscribe if you want to see more! The community will be releasing 1 new article every week. The next article will teach us how the Attention mechanism in Large Language Models works. Building A Game Boy Color Emulator in Rust: https://lnkd.in/eGRDCfwe
4 Comments
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top content