Re:Study monitors programmers' stress levels to predict the ...
by NathanKP on Wednesday May 25, 2016 @05:46PM
(#11773394)
99% of the time when I'm stressed out about code I'm working on its because the product spec is overly complicated, not because the code is bad quality. Interesting study, but I don't think it matches up with real world scenarios that well.
[ Parent
| on HN ]
Re:Study monitors programmers' stress levels to predict the ...
by appstateguy on Wednesday May 25, 2016 @05:52PM
(#11773431)
If by "overly complicated" you really mean, "ambitious but nebulous and we need it now" then I 100% agree. Nothing is more stressful than basically being put into the position where you've been given nothing more than a couple slides worth of b.s. "architecture" and "design" and they want a working prototype in a month. Feels like you're being put in an impossible situation.
Re:Study monitors programmers' stress levels to predict the ...
by fleitz on Wednesday May 25, 2016 @09:06PM
(#11774475)
This is a jr programmer mistake, sr programmers know that a couple slides is usually enough to contain the essence of the problem, and yet not enough to paint them into a corner, make something that solves the crux of the problem, and rename a couple of your classes to items on the boxes drawn on the classes, and a couple of the methods have the same names as drawn on the lines between the boxes.
If anyone questions it, show Sr Mgmt that the class and method names match, say it works, and that everyone else is just a bunch of whiners. (The most important thing is that it works enough for a sales guy to convince the customer that it does everything they wanted)
Everyone wants a Lexus but if they're stranded on the side of the road a Lada will do quite nicely. Arriving with a Lada always make you the hero. You can go for beers with mgmt after and negotiate a raise while laughing about how you're surprised the wheels didn't fall off.