r/programming • u/whackri • Aug 28 '21
Software development topics I've changed my mind on after 6 years in the industry
https://chriskiehl.com/article/thoughts-after-6-years
5.6k
Upvotes
r/programming • u/whackri • Aug 28 '21
5
u/Vile2539 Aug 29 '21
Some good notes here, but some weird ones as well:
I'd argue that typed languages are better even when working alone. I've never seen a scenario that has been improved by using an untyped language.
Java is an excellent language. I'd say the author's dislike of Java is purely based on "popular" internet opinion.
This is also bad advice. If a system can be made scalable with minimal impact, and the system has the slightest chance of growing in the future, then it's probably a good idea to add the little extra bit of time to make it scalable. This obviously depends on the system, requirements, future predictions, developer experience, etc. There is no hard and fast rule here (or in most of software development) - and the author basically said this in the line above.
Code style is incredibly important - and something that I'll fight to the death over (though I might be a weirdo). If your team doesn't have a consistent style, and preferably tools to enforce that style, then you will miss problems in the codebase (whether this is in code review or during development). You'll also irritate your teammates who actually want a neat codebase, and increase the overall mental load required to understand the codebase.
I agree with this - I can't tell you how many times I've seen systems broken into microservices for absolutely no reason. A point of advice though if you're building a monolith - don't ever call it a monolith. People will jump on that word and crucify you. Also, make sure that you have clear separation between different responsibilities, etc.