• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Dion Almaer

Software, Development, Products

  • @dalmaer
  • LinkedIn
  • Medium
  • RSS
  • Show Search
Hide Search

Developer Productivity

Keeping your A-Team together with developer AI

September 30, 2024

When I look back at my career, the most fun and fulfilling times I have had has been tied to impactful projects with a team that is clicking. This has often happened at a startup, but it has also happened in some magical moments where the team is able to move fast and with agency within a larger company.

How often have you heard, or thought, the following?:

Remember when we were small? We moved so fast back then.

What if you could stay small and nimble, but get so much more done?

One core philosophy that DHH has often discussed as a key part of The Rails Way, is how it scales from a single developer. From Hello World to IPO. The way to do that is to be able to do more with less, and keep as much of the system in your head as possible. Allow room for the important pieces, and keep complexity from taking up valuable space.

When we come up with new infrastructure that compresses the complexity, we see amazing scale such as what the WhatsApp team was able to build with a small team.

I believe AI native tools can help here in a slightly different way. For example, you can somewhat outsource some of the complexity to the system. The brain budget can be augmented, and some of it can be swapped in, in real time.

This is an area of AI that I am particularly excited about, and I am seeing it occur in practice every day with customers at Augment.

When talking to one customer that is startup sized, they said:

We are growing like a weed, and I was nervous that we would have to grow the team… which scared me. I love our tight-knit crew and how we have trust and minimal coordination issues. But since using Augment and other AI tools we are finding that our work isn’t scaling linearly… we are so productive that we don’t have to grow to meet feature demand. I hope this lasts as long as possible!

This resonates a lot! I have seen the coordination headwinds first hand, and anything that you can do to minimize them will result in HUGE productivity gains… and will also give you more joyful moments.

How are AI tools helping?

I think that the following properties are compounding:

More than “faster typing”

It’s easy to think about features such as code completions as a way to speed up typing. Speeding up typing is just the start. The next step is taking care of raw toil and tedium, but where savings really kick in are when the suggestion brings you something that you maybe didn’t necessarily know what to write. I love it when this happens, especially when it teaches me something new about the codebase or another way to do something.

No more “Reading the docs”

The LLMs have read the docs for you, and much beyond. They have read your code, and that of all of your dependencies. They may have consumed knowledge from other sources (Linear tickets? Slack channels? PRs with comments?).

Instead of hunting down documentation, you can use features such as Chat to ask questions that map to your exact task at hand. You can personalize responses (maybe you want a terse reply, or the opposite?). And having help that maps to your context means you aren’t translating between the examples that happen to be in the docs.

Saving time not just for myself, but for my team

I hate interrupting my coworkers when I am stuck. Now the first line of defense allows me to stay unblocked by working with Augment. This can save a ton of “clock time” when my coworkers are busy… or on the other side of the world!

This doesn’t mean I don’t want time with my colleagues, but it can be focused on working together on more novel and creative problems.

Confidence working across unfamiliar codebases

Maybe you aren’t as experience in Rust and have been nervous to touch that part of the codebase. You don’t have to worry as much about the idioms of the language, and you can use these tools to help you learn as you use autocomplete functionality and chat to act more declaratively.

This flexibility is being noticed, and “full stack” is morphing into the rise of the “product engineer”:

Many argue that front-end engineering is fading due to AI tools, but I see a convergence of roles.

Front-end devs can now generate schemas with tools like @supabase’s https://t.co/ZWMGf6cVj5, while back-end devs can scaffold UIs with @vercel’s @v0.

This is the rise of the…

— Kenneth Auchenberg 🛠 (@auchenberg) September 18, 2024

This also works when your team has to interact with another team at a larger company. You may not have to wait for the work to be done by them, and instead can dive in and collaborate to get something done!

From code completion to task completion

Code completions are still a favorite feature. I feel like I am dancing with my AI partner and quickly iterate and steer. But we are now seeing the ability to share your intent at a higher level, and have new UX that will quickly help you get a full task done. I’m very excited to share what Augment has been doing here.

Think you can keep your A-Team?

Now, I may be biased… but I think the best way to keep the A-Team together is to have a developer AI platform that has the deep codebase and external context awareness to act like you are working with the experience of your entire team vs. a knowledgable engineer that knows the basics. The difference is night and day, and I get very happy thinking about smaller teams with super powers. I hope you do too!

And maybe you will have the type of outsized impact that 13 employees did at Instagram, or 55 at WhatsApp, or 50 at Mojang (Minecraft), or if you are truly lucky… Donald Knuth with TeX?

(I was thinking about TeX and Professor Knuth again when Matt Holden recently shipped TexSandbox, a tool I wish I had in my Math courses at Uni!)

Building AI Dance Partners (and your role as a good lead!)

December 31, 2023

tl;dr LLMs give computers new abilities to be better partners for us humans, and if we build the right systems we can transform how we work together. I have learned some lessons on the building side, but also on how to do more as an augmented human to get the most out of this new world!


A dream stirred me from my sleep. I found myself on the set of ‘Dancing with the Stars,’ but with a twist: my partner was not human, but a robot. As I lay there, half-awake at 3am, I pondered the meaning of this mechanical ballroom dance. Then it clicked… it was a metaphor for the work I’ve been deeply immersed in at the close of 2023: creating computer systems that augment human capabilities, giving developers and their teams superpowers in software delivery.

The Dance

I’ve always believed in the power of combining the best of both worlds: human creativity and computer precision. The best user experiences have always weaved brain and tool, these days including those that are digital.

LLMs have changed the game in that precision has a brand new capability: a new layer of intuition that we can tie to. A way to combine my Systems 1 and 2 brain with a mesh of combined thought. Back in the dream, my subconscious was painting a picture of the ideal partnership where the human mostly leads, and the machine follows in a tightly choreographed back-and-forth. Just like picking up a tool such as PhotoShop, it can still take time to master the steps, and the dance changes as the capabilities change. How can we best use the strengths and weaknesses of each partner so that they work as one?

Crafting the Perfect Partner

I’m currently iterating on a dancer that developers can shape into the best partner possible. Speed and skill are crucial. A slow computer is like a dance partner with two left feet, disrupting the flow and making collaboration frustrating. Skill, on the other hand, is about quality and finesse—leading without stepping on each other’s toes, sharing knowledge to maintain the rhythm.

The Car and the Engine

I was excited to join a Sutter Hill Ventures startup for many reasons, and my expectations have been very much exceeded. Not only do we have a solid financial backing that allows us to really focus on building a game changing product and business, but the support that the Sutter Hill team has is special. I get to work with my favorite UX person there is. The enterprise sales playbook is ready to run. And on and on.

The team itself (founders, CEO, and everyone else!) is not only world class, but there is a strategic bet that I strongly believe in for building the absolutely best product. The heart of the team has AI researches who deeply understand every part of the stack.

It’s one thing to build a car using someone else’s engine; it’s another to be able to fully tinker with that engine or even build your own.

In 2023 we have learned so much as a community. First we had the transformational moment when developers got to poke at what could be done with OpenAI APIs (and then so many more). There was the prompt engineering, RAG’ing, and pushing the boundaries of what’s possible.

Embracing Constant Change

The model tier is just the beginning, and going from demo to a production system requires a world of work to be done around it.

New models and research are popping up on a daily basis, so how do you filter out what could be helpful? How do you determine its utility for your specific needs? How do you ensure your data is accurate and current? Are your evaluations truly reflective of quality, or are you just fitting the last piece of a puzzle?

Metrics

Measuring what matters here is hard. For example, with coding tools, I often see discussion around the amount of codethat is created, or the Completion Acceptance Rate, but when you watch this play out in practice with your users you realize…. wait a minute…

Do we want to always be creating code if it’s adding entropy into the system? If that code is iffy, and if the human can’t tell, then maybe we are adding problems. And, wouldn’t it be nice if we maybe could… delete code and simplify?

For completion acceptance, I can get very different results by changing the system to vary the amount of code that comes back, or the latency, and many of the habits that you build with the developers. The habits have been really fun to watch. Seeing cohorts that start by waiting for the system to do things vs. communicating more and moving quickly.

And when I do side by side comparisons, I see the huge difference where one system can have a hire acceptance rate that ends up with code that doesn’t run. Don’t I really want to be tracking time to running code that is high quality?

Here’s to 2024

We are somewhere in the journey that is akin to constant improvements that we can see with other tools such as Midjourney.

I’m grateful for my team’s collective ability to build everything needed for the ultimate coding dance partner. We are building the platform that enables the building of this partner, to iterate on it, to take in the innovation from open source and our own research, and man I’m having a great time doing it.

I can’t wait to share it with more of you. If you’re a developer who spends most of your day coding, enjoys giving feedback the moulds a product, and are interested in getting early access, I’d love to hear from you.

Happy New Year, and may this become true!

Prediction: 2024 will feel like a breakthrough year in terms of AI capability, safety, and general positivity about its potential impact. In the longer term, it'll look like just one more year on an exponential that can make everyone's lives better than anyone's today.

— Greg Brockman (@gdb) December 31, 2023

NOTE: Of course, this article was written by both Dion Almaer and the dancer within Type.

Developer Productivity Matters

November 8, 2021

I have been fighting for investment and focus on developer productivity for a large part of my career. Platforms often focus on the user side more, and think that the focus should be on solely economic opportunity. Understandably, if you can’t persuade a business that their effort will result in profit, you won’t get resources applied.

I can’t tell you how often I have heard a version of the following:

“Hell. Developers rushed to learn Objective-C to build iOS apps!”

— Bizness Guy

The gold rush was real on getting apps available for the exploding usage on the iPhone, but while Objective-C looks weird to many from the {curly brace generation} it is actually an elegant language (sure, it has quirks, but don’t we all!). This flippant repost also ignores the quality in the UIKit foundations, and the quality of tooling.

i know it's popular to hate on "dev experience" as a cop-out these days but i'd argue that "dev experience" is actually "developer economics" and should be guiding most (but not all) technical decisions we make.

— Pete Hunt 🚁 (@floydophone) May 25, 2021
Pete’s right!

Economics of a platform are important, and are an input into how many developers can be hired, but there are clear reasons that it is important to focus on developer productivity if you work on a platform. I contend that the vast majority of platforms are under invested in their support of developers, and haven’t reached the point of limited returns. Why?

Time is precious

A developer has a set time budget that is fixed. There are priorities coming at them from all sides. The “business” wants features, features, features. The platform is forcing deprecations, and requirements for performance, accessibility, and security.

Time well spent

If we can take away any time that is wasteful, we can optimize the time well spent of a developer. This allows for more productive output per time slot.

Another important characteristic of time well spent is that we aren’t JUST talking about pure optimization of effort. Developers want to do a good job, and are quite willing to spend time that results in higher quality experiences. We want to do a good job, and have experienced getting into the flow state to build something great. The notion that “developers are lazy” is often misinterpreted. We just don’t want to waste time, just like humans hate any form of bureaucracy that feels wasteful.

Frustration is the productivity killer

If you are frustrated, time gets exponentially eaten up. Developers are engaging in a creative pursuit, and paper cuts slow down your flow, and get you in a frame of mind that is destructive. When you are enjoying yourself, your energy levels won’t deplete in the same way as if frustrated. This is why it is vital that you track developer needs and frustrations and actively get rid of them.

If the platform is hard to use, and the tooling isn’t delightful, and the documentation sucks, well then the effect on time isn’t a set amount, but is rather a multiplier. You have the power to influence a multiplier. This is a big deal. Also, if you are particularly bad, that multiplier can go as low as zero, where the developer flips the table and does something else 🙂

Developers don’t scale linearly

While the economics of a platform may allow for hiring more developers, we all know that this doesn’t scale cleanly. As a team grows, you get increased communication costs, and it takes a very special team to be able to scale. Cut out the need and allow teams to be as small as possible, and to allow a team to be able to work in parallel as best as they can.

Don’t cop out on productivity

Don’t fall for it. Don’t think that you can get away without focusing on developers and doing everything you can to keep them productive. I remember someone who told me “The business doesn’t care about developer smiles” as though I was a hippy solely looking to care about our developers (which isn’t a bad thing!). Building trust is important. Having developers who love working on your platform is valuable. But beyond that, you want the flywheel from developers to be going as fast as possible. You want them putting their effort into quality new features. You want them fresh enough to want to put effort into areas that you care about in the commons of your ecosystem (performance, privacy, security, etc).

You should be doing everything you can to maximize time well spent, and taking on as many hard problems as you can, so your ecosystem doesn’t have to.

So, yes, developer productivity matters.

Primary Sidebar

Twitter

My Tweets

Recent Posts

  • Stitching with the new Jules API
  • Pools of Extraction: How I Hack on Software Projects with LLMs
  • Stitch Design Variants: A Picture Really Is Worth a Thousand Words?
  • Stitch Prompt: A CLI for Design Variety
  • Stitch: A Tasteful Idea

Follow

  • LinkedIn
  • Medium
  • RSS
  • Twitter

Tags

3d Touch 2016 Active Recall Adaptive Design Agile AI Native Dev AI Software Design AI Software Development Amazon Echo Android Android Development Apple Application Apps Artificial Intelligence Autocorrect blog Bots Brain Calendar Career Advice Cloud Computing Coding Cognitive Bias Commerce Communication Companies Conference Consciousness Cooking Cricket Cross Platform Deadline Delivery Design Design Systems Desktop Developer Advocacy Developer Experience Developer Platform Developer Productivity Developer Relations Developers Developer Tools Development Distributed Teams Documentation DX Ecosystem Education Energy Engineering Engineering Mangement Entrepreneurship Exercise Eyes Family Fitness Football Founders Future GenAI Gender Equality Google Google Developer Google IO Google Labs Habits Health Hill Climbing HR Integrations JavaScript Jobs Jquery Jules Kids Stories Kotlin Language LASIK Leadership Learning LLMs Lottery Machine Learning Management Messaging Metrics Micro Learning Microservices Microsoft Mobile Mobile App Development Mobile Apps Mobile Web Moving On NPM Open Source Organization Organization Design Pair Programming Paren Parenting Path Performance Platform Platform Thinking Politics Product Design Product Development Productivity Product Management Product Metrics Programming Progress Progressive Enhancement Progressive Web App Project Management Psychology Push Notifications pwa QA Rails React Reactive Remix Remote Working Resilience Ruby on Rails Screentime Self Improvement Service Worker Sharing Economy Shipping Shopify Short Story Silicon Valley Slack Soccer Software Software Development Spaced Repetition Speaking Startup Steve Jobs Stitch Study Teaching Team Building Tech Tech Ecosystems Technical Writing Technology Tools Transportation TV Series Twitter Typescript Uber UI Unknown User Experience User Testing UX vitals Voice Walmart Web Web Components Web Development Web Extensions Web Frameworks Web Performance Web Platform WWDC Yarn

Subscribe via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Archives

  • October 2025
  • September 2025
  • August 2025
  • January 2025
  • December 2024
  • November 2024
  • September 2024
  • May 2024
  • April 2024
  • December 2023
  • October 2023
  • August 2023
  • June 2023
  • May 2023
  • March 2023
  • February 2023
  • January 2023
  • September 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • November 2021
  • August 2021
  • July 2021
  • February 2021
  • January 2021
  • May 2020
  • April 2020
  • October 2019
  • August 2019
  • July 2019
  • June 2019
  • April 2019
  • March 2019
  • January 2019
  • October 2018
  • August 2018
  • July 2018
  • May 2018
  • February 2018
  • December 2017
  • November 2017
  • September 2017
  • August 2017
  • July 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • September 2016
  • August 2016
  • July 2016
  • June 2016
  • May 2016
  • April 2016
  • March 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • July 2015
  • June 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • December 2014
  • November 2014
  • October 2014
  • September 2014
  • August 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • December 2013
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • December 2012
  • November 2012
  • October 2012
  • September 2012
  • August 2012

Search

Subscribe

RSS feed RSS - Posts

The right thing to do, is the right thing to do.

The right thing to do, is the right thing to do.

Dion Almaer

Copyright © 2026 · Log in

 

Loading Comments...