3 ms·

> Technology is not a goal. Nobody cares about which programming language you are using, nobody cares about which frameworks your team has chosen, nobody cares

> Technology is not a goal. 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. Technology doesn't matter, if your code doesn't fulfill a mission.

Xoros 9y ago
And it may brings back a little bit of humility in our field. There's often no need for a hammer, as shiny as it is, to crack an egg open. Sometimes quick and dirty makes clients happy, and sometimes this is all that matters.
- mythrwy 9y ago
  While this is certainly true it's also our responsibility to consider the long term well being of a client rather than just their temporary placation with a bit of sugar. Picking apart what people actually need from what they claim to need is an underrated skill.
  - unclebucknasty 9y ago
    >our responsibility to consider the long term well being of a client True, but I don't think the answer is just "framework" either. A more thorough analysis of many of these scenarios would likely yield a surprising number of cases wherein the answer is not framework, if all tradeoffs were earnestly considered. For instance, a couple of short years ago it would have been seen as responsible to build on Angular 1.x. Today, those clients are stuck with an obsolete, underperforming stack that has been deprecated with no reasonable upgrade path. In some ways, knowing what we do about the ever-changing framework landscape, a reasonable argument could be made that it's almost irresponsible to recommend dependency on these ever-heavier, more intrusive, monolithic behemoths.
celim307 9y ago
One of the biggest lessons I learned early in my career.

Xoros 9y ago

And it may brings back a little bit of humility in our field. There's often no need for a hammer, as shiny as it is, to crack an egg open. Sometimes quick and dirty makes clients happy, and sometimes this is all that matters.

mythrwy 9y ago
While this is certainly true it's also our responsibility to consider the long term well being of a client rather than just their temporary placation with a bit of sugar. Picking apart what people actually need from what they claim to need is an underrated skill.
- unclebucknasty 9y ago
  >our responsibility to consider the long term well being of a client True, but I don't think the answer is just "framework" either. A more thorough analysis of many of these scenarios would likely yield a surprising number of cases wherein the answer is not framework, if all tradeoffs were earnestly considered. For instance, a couple of short years ago it would have been seen as responsible to build on Angular 1.x. Today, those clients are stuck with an obsolete, underperforming stack that has been deprecated with no reasonable upgrade path. In some ways, knowing what we do about the ever-changing framework landscape, a reasonable argument could be made that it's almost irresponsible to recommend dependency on these ever-heavier, more intrusive, monolithic behemoths.

celim307 9y ago

One of the biggest lessons I learned early in my career.