4 ms·
I would be willing to bet that a lot of the code produced at large companies is not very good either, honestly. Almost every company I've ever been at, code qu
by bluefirebrand 4y ago
I would be willing to bet that a lot of the code produced at large companies is not very good either, honestly.
Almost every company I've ever been at, code quality is a far down the list concerns for the business and that winds up infecting the dev team as well who is constantly scrambling to hit deadlines and produce business value.
Some of these companies have been in business making money on these shoddy codebases for decades.
- atomicnumber3 4y agoYeah, I can second this. I worked at a big company popular on this board and while all the devs there were obviously absurdly talented, the general level of code quality was... not good. And it's specifically because management prioritized shipping features over literally anything else, so any time you spent on designing or refactoring was a negative mark on your perf sheet (since that's then a gap where you weren't shipping anything). Maybe the secret sauce is that if you hire good devs and make them write bad code, the code is still workable and is just a huge PITA to figure dev work instead of being totally intractable?
- bluefirebrand 4y agoI think this is basically exactly it. Everyone needs to hire the best, 10x, rockstar ninja programmers that they can find. They find the people who, given time, could build absolutely amazing high quality systems. They have to try and find those people because they can still produce working, somewhat maintainable systems in less time. And all companies just want to give less time to build things.
- Existenceblinks 4y agoAt some point clean code doesn't really exist. I mean, after eliminate this two big cases; a too big function and too deep(inheritance)/wide(composition) indirection. Is pipe only function clean? I don't know, I think it's sometimes.