6 ms·

There are a lot of questionable ideas in this piece. > Nobody cares about which programming language you are using, nobody cares about which frameworks your te

There are a lot of questionable ideas in this piece. > Nobody cares about which programming language you are using, nobody cares about which frameworks your team has chosen, nobody cares about how elegant your data structures are and nobody cares about how good is your code. The only thing that somebody cares about is how much does your software cost and how much revenue it generates I agree with this to a point. The business cares about code quality so far as it effects the ability to deliver new features and maintenance, which in reality means they care quite a lot. They don't understand, and they can't express it, but they do. I work on a legacy app now that is so brittle the team takes months to deliver features, and they're buggy and error prone. This team is competent for the most part too. > JS Fatigue happens when people use tools they don't need to solve problems they don't have. I think the concept the author is going for is best elucidated by Fred Brooks in "No Silver Bullet"[1] when talks about accidental and essential complexity. The idea that there's the complexity of the domain/problem and the complexity we introduce as part of the solution, such as build systems, cross compilers, mvc frameworks etc... > The JavaScript ecosystem nowadays is responsible for the global revolution the same way steam engines were responsible for the first industrial revolution I really can't imagine a scenario where this is true. I'd prefer to see some clarification what revolution the author is referring to exactly. [1] http://www.itu.dk/people/hesj/BSUP/artikler/no-silver-bullit.pdf http://www.itu.dk/people/hesj/BSUP/artikler/no-silver-bullit...

lucasfcosta 9y ago
Hi le-mark, Thanks for the feedback. I realize you're right about your last point about the industrial revolution. That was totally my fault, I didn't intend for people to take that literally but I wrote it in a way that made it sound literal. Since that was only an introductory statement I decided on removing that based on the facts shown here later in other to avoid deviating from the post's main subject. Thank you very much for sharing your thoughts!
- le-mark 9y ago
  Ah ok, hyperbole can be an effective oratorical device, I use it myself from time to time. It's tricky though.
  - exelius 9y ago
    Side note - this type of exchange is why I love HN. It's like Reddit for mature adults.
    - na85 9y ago
      >It's like Reddit for mature adults. The immaturity has simply been replaced with smugness and elitism.
bigger_cheese 9y ago
> Nobody cares about which programming language you are using, nobody cares about which frameworks your team has chosen, nobody cares about how elegant your data structures are and nobody cares about how good is your code. The only thing that somebody cares about is how much does your software cost and how much revenue it generates This completely elides one of the biggest issues (at least in my job) -Who is going to maintain the code and how much is that support going to cost. Maintenance can include troubleshooting and bug fixes/enhancements and sometimes it's just pure support (i.e who does the user contact if their app is crashing). I don't know about the web which is what I usually associate Javascript with but for in house business applications delivering a well supported application is critical. I've found (as someone who occasionally has to commission contract work) that unless I am upfront (and dare I say confrontational) about support and maintenance expectations during the design phase I will end up with a complete mess at the end and support costs will end up ballooning out.

lucasfcosta 9y ago

Hi le-mark, Thanks for the feedback. I realize you're right about your last point about the industrial revolution. That was totally my fault, I didn't intend for people to take that literally but I wrote it in a way that made it sound literal. Since that was only an introductory statement I decided on removing that based on the facts shown here later in other to avoid deviating from the post's main subject. Thank you very much for sharing your thoughts!

le-mark 9y ago
Ah ok, hyperbole can be an effective oratorical device, I use it myself from time to time. It's tricky though.
- exelius 9y ago
  Side note - this type of exchange is why I love HN. It's like Reddit for mature adults.
  - na85 9y ago
    >It's like Reddit for mature adults. The immaturity has simply been replaced with smugness and elitism.

bigger_cheese 9y ago

> Nobody cares about which programming language you are using, nobody cares about which frameworks your team has chosen, nobody cares about how elegant your data structures are and nobody cares about how good is your code. The only thing that somebody cares about is how much does your software cost and how much revenue it generates This completely elides one of the biggest issues (at least in my job) -Who is going to maintain the code and how much is that support going to cost. Maintenance can include troubleshooting and bug fixes/enhancements and sometimes it's just pure support (i.e who does the user contact if their app is crashing). I don't know about the web which is what I usually associate Javascript with but for in house business applications delivering a well supported application is critical. I've found (as someone who occasionally has to commission contract work) that unless I am upfront (and dare I say confrontational) about support and maintenance expectations during the design phase I will end up with a complete mess at the end and support costs will end up ballooning out.