- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
When you call the humans who keep production safe “the bottleneck” you’re painting a very specific picture. The reviewer as the obstacle. The gate as friction. Something to route around. Cue in the Balrog scene from Lord of the Rings. That picture determines what you build. The tools to remove reviewers look different from tools to support them.
writing lines has never been the bottleneck, that’s only something a junior would say. The bottleneck is always requirements: changing, understanding them, making sure you don’t miss test cases before writing any code.
No, the bottleneck is not always requirements. Understanding requirements is a prerequisite to writing correct code, but it takes a fraction of the time.
Obviously different domains have different complexities of requirements and code which changes the ratio
Yeah, e.g. writing UI code takes a lot of time, while it tends to be pretty simple overall and that’s why we have so many UI toolkits, to reduce the amount of writing required for UI.
Writing the requirements is what takes time.
Instead of spending 4 weeks writing requirements and 1 week implementing them, have you tried spending a day guessing at requirements, half a week writing a prototype, and then asking the customer if it works for them?
Have you ever worked on a tools team where your customers are internal and your developers are also customers and so know the requirements inside-out?
Hehe! I have.
And what took the longest was for me to get used to the dual versioning of QML modules and fixing the UI code that was partially using stuff from both versions.
Business logic was pretty small for me but that was because other engineers had already written most of it in Maths.