3 ms·
It's interesting that front-end developers rate so high. Having been in FED for a while, I can say it totally varies from company to company. I've worked at de
by at-fates-hands 11y ago
It's interesting that front-end developers rate so high. Having been in FED for a while, I can say it totally varies from company to company.
I've worked at dev shops that were virtual sweat shops and had insane goals for each month. This caused you to work 11-13 hour days to hit your goals, less you get put on a PIP (performance improvement plan).
Others shops went to great lengths to give developers what I thought to be far too much reign to do what they pleased. Come in at noon and work till 10pm? Sure. Take two hour lunches? No problem. Sure the work got done eventually but the atmosphere was super lax with little or no oversight.
- bsilvereagle 11y ago> Sure the work got done eventually but the atmosphere was super lax with little or no oversight. What's the problem with this? If the work is getting done, and meets quality standards, do all employees need oversight? Does a lax work environment immediately imply that the work done there is poor?
- at-fates-hands 11y agoNot necessarily, but if your developers and QA and PM's are all on different schedules, it can lead to some major headaches. I worked at a place where devs would regularly come in around noon or later. Code wouldn't get checked in and then the QA people were complaining they couldn't test code and the PM's couldn't tell the "business" stuff was ready to look at. Likewise, if the QA people are coming in late and the dev is waiting for stuff to be checked off so he can tell the PM to send the app for review, it can screw delivery up. Is the work done poorly? No, but there were headaches when everybody was on their own schedules.
- wcummings 11y agoNoon to 8 covers most of the core working hours, I've never seen this cause problems.