@george @blacklight back then, software engineers were actually engineers, as opposed to the IDE google-jockeys we have now. Software cobblers?
Top-level
@george @blacklight back then, software engineers were actually engineers, as opposed to the IDE google-jockeys we have now. Software cobblers? 8 comments
Software dev team A has an expert chiefly responsible for its main program. That genius routinely codes amazing optimizations incomprehensible to anyone else. Team B distributes responsibility and authorship. Readability is consciously priorized over performance. Coding standards are obeyed. Which team can implement a brilliant new idea? Has fewer bugs? Fixes them faster? Will exist in 5 years? Would I prefer to work in? B. B. B. B. B. @dj3ei @uastronomer @george @blacklight I was meaning more about the discipline and rigorous methodology, rather than pasting from StackOverflow until error messages are resolved. I'm completely with you that methodical thinking and a certain amount of knowing what it is one is doing are essential. I was mostly reacting to @uastronomer's "Story of Mel". That Mel hero from back then, when IT knew little about how to do software projects, would need to learn a thing or two today. Worse: By today's standard, the project management is unacceptable: Non-agile, truck number 1, team resorts to passive-aggressive behavior for ethical reasons. I'm obviously with you on your main conclusion. 🤔 But to pick a minor nit: Who was finally securing Greek victory in the Trojan war (according to the classical account)? On that one, I'm betting the horse on team Odysseus, rather than team Achilles. @dj3ei @dnorman @george @blacklight i concede without argument as i last read the Iliad 30 years ago ☺️ |
@dnorman @george @blacklight
I guess it's time to bring out The Story of Mel again:
https://web.archive.org/web/20170309215507/http://www.pbm.com/~lindahl/mel.html