What happens when you go all-in on velocity

Manager.dev

A startup CEO shares how his 6-person engineering team achieves velocity comparable to 50-person organizations through direct customer-engineer communication, AI-assisted code reviews with sub-hour PR merges, and continuous bottleneck elimination. The approach prioritizes learning rate over accumulated knowledge, includes hiring interns for fresh perspectives, and requires leadership to remain hands-on in code to identify real friction points.

What a 10X TEAM looks like

Why I’m obsessed with Engineering velocity

Experiment #3: testing & quality: the next frontier

Building the Right Team (and hiring interns)

<a href="https://app.daily.dev/antonzaides" data-mention-id="pPJxvEccyBNkDUh4jQy6I" data-mention-username="antonzaides" translate="no">@antonzaides</a> this is true gem! I love how bullish this team is on AI. Are some of their tools open source or maybe there’s more to read?

Awesome write up <a href="https://app.daily.dev/antonzaides" data-mention-id="pPJxvEccyBNkDUh4jQy6I" data-mention-username="antonzaides" translate="no">@antonzaides</a>
Would love to dive deeper into the test cases, it’s something we try to apply, big coverage should give more safety/confidence.
But at the same rate if those are AI generated you often get hit with a expect(true).toBeTruthy tests.
Did you get any insights from Sumanyu on how they do quality control on the tests to make sense from product level? (Maybe this is big part where their QA comes in now)