| A few observations: - Being reasonably kind to your future self without over engineering or over architecting is the real skill of a talented developer/engineer in my eyes. - All software is like hardware, no matter how it's built, it has it's limits that will likely have to be revisited. - Customers not caring about which language/framework something is made in doesn't mean the code is automatically unkept or made carelessly. - Most languages and frameworks are pretty capable. All have their tradeoffs of what they uniquely provide vs give away. Very few projects will critically fail or succeed solely from the selection of a particular framework or language. - I'm not sure if you're connecting customers who don't care what language their system is built in, causing 3 AM bugs. If so: a) 3 AM bugs are not a cause of any particular language of framework or language, or the customer not caring about which one, but rather, the developer. b) Bugs are a reality on all platforms, and are best insulated against by a combination of process, policy and strategy that can be reasonably implemented in any stack. Ultimately, it's about how the user feels and the value that provided to them in solving a pain. Customer value is NOT the same value the developer provides themselves to make the developer's own life easier and somehow believing that all the build tools in the world will solve the customer's problem any better, or make a difference for the end user. It's not as often as it seems. Most languages and frameworks are capable of delivering delight if the developer spends time focussing on the user's pain and not just their own pains in their stack. Looking at how much value HN provides, it's not a function of it's language, framework, or coding. Maybe like inter-faith, i'm an inter-platform kind of guy as a polyglot and see the good everyone can be doing instead of dividing among syntactical philosophy that is indistinguishable to the users in the end. |