Ask HN: Programmer satisfaction by field
Have you ever wondered if it's true that that devs in field X in general are miserable, while the people in field are having a great time? Me too, and I've decided to make a survey about it! Let's gather data on this!
Please take 30 seconds to answer this one question survey:
https://www.surveymonkey.com/r/3LSJMB7
The results are publicly available at any time:
https://www.surveymonkey.com/results/SM-GVHWDLNR/
18 comments
[ 24.5 ms ] story [ 668 ms ] threadThe bars are ordered 5-1 from top to bottom.
https://www.surveymonkey.com/results/SM-VT2RQJNR/
For what it's worth, I think it's a great part of the programming world to be in. :)
I hope I didn't screw up the metrics. :/
I grew up learning programming on a Commodore 64, where getting anything done meant twiddling bits and writing to registers of various hardware devices. Writing device drivers today can provide the same sort of thrill, since the work is quite similar. A lot of my time in high school and college in the 90's was spent learning all about UNIX and Linux, so it feels very natural today when I develop user-space tools that bring value to the user. Outside of nostalgia, there's plenty of bleeding-edge work to keep things interesting -- audio/video processing, extending platforms such as Android, security, etc.
Shouldn't there be 2 separate questions? "What field are you in?" and "Disregarding salary, how happy are you with your field?" Would prevent confusion.
How did you come up with this list of fields? Where does academia fit in? Why are systems programming and desktop apps in the same category?
There is no academia (as in academic career track) - I am only asking about programmers, not researchers. If you work in academia as a programmer (say implement stuff at CERN), you can answer according to the nature of your job - ex. if you help scientists write simulations, you select "scientific/numeric", if you mainly work on massive data pipelines, you select "big data" etc.
As for coming up with a list - I compiled it myself, trying to bundle together work that seems close enough in nature. For me, desktop programming looks similar to systems programming - i.e. it's mostly C++/C/other compiled languages, working against OS APIs, no garbage collection, expectation of reasonably low latency.
https://www.surveymonkey.com/results/SM-VT2RQJNR/
(Sorry, the original post is too old and I cannot edit it anymore).
http://stackoverflow.com/research/developer-survey-2016