4 ms·
I'm going to ignore #3. They really don't matter and are crap at best. The problem with #1 is that they refuse to acknowledge the newer tools of analysis and u
by crankylinuxuser 8y ago
I'm going to ignore #3. They really don't matter and are crap at best.
The problem with #1 is that they refuse to acknowledge the newer tools of analysis and understanding. They cling to older "mature" tools and methods, with nary a care of if/how the newer ones work. They won't be the fastest or novelist, but one ting can be said: it will work, and it will work well.
The problem with #2 is "Oh shiny OH SHIT". They go down the path of the next new thing, with little to no understanding that the old fogeys already did that and it didn't work then. But their big advantage is, it might just work now and enable a whole new area.
And it's really hard being in both #1 and #2.
- somethingsimple 8y agoAbout #3s - read this comment I just posted about my wife: https://news.ycombinator.com/item?id=17060366 https://news.ycombinator.com/item?id=17060366 I didn’t mentioned it there but the only reason she got into Software Engineering is because it pays well.
- crankylinuxuser 8y agoAh. I was also attributing "lazy, claim a lot, do little, and copy from stackexchange" type. I certainly wasn't thinking of 10x dev who wants to get away from it when out of work.