4 ms·
No one is talking about running a business. We're talking about code bureaucracy. I don't like front end, still happy to do it though, the issue is mandatory me
by carom 4y ago
No one is talking about running a business. We're talking about code bureaucracy. I don't like front end, still happy to do it though, the issue is mandatory meetings, code reviews, design docs, and tests to make a simple UI change.
Run a business, talk to stakeholders, make sales, but don't make programming so unpalatable that it moves at a glacial pace. Tell me what to do then let me do the thing you pay me to, and that is to puke out high quality code.
All of the code bureaucracy features have their place but I don't think they're needed for every change.
- t43562 4y agoCode reviews should be at least a chance for other team members to learn the code - and take responsibility for it. If there's a bug they should have spotted it and the heat no longer falls entirely on you. Tests similarly are about allowing other people to change things without fearing that they will break the code you wrote. Without them the pace of change becomes very slow or very buggy. It's just working with other people that's more complex than working on your own. The meetings are usually because nobody has enough information or enough authority to get things decided. We can fix that sort of thing up to a point in many ways including the agile idea of having a product owner to prevent stakeholders annoying developers.