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
Post a Comment