Scaleups: If we double the amount of engineers, why can't we get the work done in half the time?





However funny Warren Buffett's famous quote ‘๐˜ ๐˜ฐ๐˜ถ ๐˜Š๐˜ข๐˜ฏ’๐˜ต ๐˜—๐˜ณ๐˜ฐ๐˜ฅ๐˜ถ๐˜ค๐˜ฆ ๐˜ข ๐˜‰๐˜ข๐˜ฃ๐˜บ ๐˜ช๐˜ฏ ๐˜–๐˜ฏ๐˜ฆ ๐˜”๐˜ฐ๐˜ฏ๐˜ต๐˜ฉ ๐˜ฃ๐˜บ ๐˜Ž๐˜ฆ๐˜ต๐˜ต๐˜ช๐˜ฏ๐˜จ ๐˜•๐˜ช๐˜ฏ๐˜ฆ ๐˜ž๐˜ฐ๐˜ฎ๐˜ฆ๐˜ฏ ๐˜—๐˜ณ๐˜ฆ๐˜จ๐˜ฏ๐˜ข๐˜ฏ๐˜ต’ is, it doesn't really do any justice to the creative process and the complexities of software engineering.

While ideally, you should see an acceleration after adding new developers, the reality of many scaleups is that there are many inhibiting factors at work that affect productivity, or can even cause big delays when not addressed.

In the article "If adding more engineers doesn’t speed up our development, what does?", I'm describing a few of these situations and best practices that actually help in speeding up software development:

✅ Respect Legacy Code & Treat it Right
✅ Forget Technical Debt (I'll explain)
✅ Own the Code in a Senior Way
✅ Split up the Monolith (in all ways possible)
✅ Address the Documentation Problem — Intelligently
✅ Analyze & Fix the Product Development Process

๐˜“๐˜ช๐˜ฏ๐˜ฌ ๐˜ต๐˜ฐ ๐˜ต๐˜ฉ๐˜ฆ ๐˜ข๐˜ณ๐˜ต๐˜ช๐˜ค๐˜ญ๐˜ฆ ๐˜ช๐˜ฏ ๐˜ต๐˜ฉ๐˜ฆ ๐˜ค๐˜ฐ๐˜ฎ๐˜ฎ๐˜ฆ๐˜ฏ๐˜ต๐˜ด.

๐Ÿ’กInspiration for the article: Maarten Dalmijn's post a few weeks ago (see comments).

#scaleups #techdebt #legacy #softwareengineering #cto #fcto #softwaredevelopment #timetomarket #productdevelopment #lean #agile #modularmonolith #knowledgemanagement




Source: https://www.linkedin.com/posts/mvneerven_scaleups-techdebt-legacy-activity-7031918898685845504--TAz

Comments

Popular Posts