Development velocity slowdowns from inner development loop friction
6/10 MediumDespite improvements in tooling and culture, many teams experience bottlenecks in everyday development work, particularly in the inner development loop where code changes and testing cycles introduce slowdowns.
Sources
Collection History
The whole cycle of having to push CI code, wait 10 minutes while praying for it to work, still getting an error, trying to figure the mistake, fixing one subtle syntax error, then pushing the code again in the hope that that works is just a terrible workflow. Massive waste of time.
So not just the final sight speed but the dev experience right That plus unexpected bugs being introduced and some uh limitations cropping up around server client interactions
Slowdowns in the 'inner development loop'... friction still exists, especially around planning and execution.