Stack Overflow Developer Survey Results 2017

Re:Stack Overflow Developer Survey Results 2017 by Baeocystin on Wednesday March 22, 2017 @09:58AM (#13930907)

Heh. Two of my clients are still using VB Apps I wrote for them in VB6. I'm not ashamed. They work, and they've worked well for 12+ years, with only the most minor of updates. Not every business follows the 'innovate fast and break things' mold. Thankfully.

[ Parent | on HN ]

Re:Stack Overflow Developer Survey Results 2017 by sremani on Wednesday March 22, 2017 @10:57AM (#13931423)

Exactly, we should be proud of creating Software that works and works great. Not the languages we develop in. The one main lesson if there is I learnt from 13 years of development is, keep the dev stack boring!

[ Parent | on HN ]

Re:Stack Overflow Developer Survey Results 2017 by pjmlp on Wednesday March 22, 2017 @11:14AM (#13931568)

Whenever a kid comes around with the cool idea lets rewrite this in X, they need to explain me the business value of the proposal, like in, how will that change the monetary outcome of a project.

[ Parent | on HN ]

Re:Stack Overflow Developer Survey Results 2017 by notduncansmith on Wednesday March 22, 2017 @02:03PM (#13933199)

Isn't the implicit argument for any refactor/rewrite essentially increased velocity?

"This change will allow us to do X in Y days when normally it would take some multiple of Y."

It sounds like what you want is a more salient list of pain points in the current development environment and exactly how the proposed new thing would address them. Additionally, you'd want to hear the new set of pain points that the new thing will impose (cue the quote about some devs knowing the value of everything and the cost of nothing).

You may also, for their benefit, direct the next kid with the cool idea towards a link that's commonly thrown around here: https://en.wikipedia.org/wiki/Wikipedia:Chesterton%27s_fence

I'm going to pull the more direct section "What this means on Wikipedia":

> If you're considering nominating something for deletion, or changing a policy, because it doesn't appear to have any use or purpose, research its history first.

> You may find out why it was created, and perhaps understand that it still serves a purpose.

> Or if you do feel the issue it addressed is no longer valid, frame your argument for deletion in a way that acknowledges that.

[ Parent | on HN ]

Re:Stack Overflow Developer Survey Results 2017 by Baeocystin on Wednesday March 22, 2017 @09:21PM (#13936726)

It's the implicit rationalization. New software engineers in particular suffer from "Ohh Shiny" when choosing their toolset more than just about any other group I've worked with. To the detriment of the profession, IMO.

(Nice link. I was unaware of the name for that heuristic.)

[ Parent | on HN ]