News for hackers. Stuff that matters.
Re:Exercises to craft an employer brand that makes engineers... by toomuchtodo on Tuesday May 14, 2019 @01:37PM (#19911689)
You feel you're paying X for 40 hours a week, when a lot of engineers are of the opinion you should only be getting 30 hours for X. Some companies will offer you X for 30 hours, and the rest of companies will have to compete against that (for now) or deal with it when regulation enforces it through labor law (eventually), similar to how unions brought us the weekend [1].

[1] https://www.politifact.com/truth-o-meter/statements/2015/sep...

Re:Exercises to craft an employer brand that makes engineers... by JohnFen on Tuesday May 14, 2019 @02:09PM (#19912137)
I have never been paid by the hour. I get paid for producing acceptable code by the deadline.
Re:Exercises to craft an employer brand that makes engineers... by sgift on Tuesday May 14, 2019 @02:30PM (#19912390)
So, when you produce the acceptable code faster you can go home earlier? No more work in a week? If not, you are paid by the hour, you just wish you would be paid for producing acceptable code by the deadline (me too btw).
Re:Exercises to craft an employer brand that makes engineers... by JohnFen on Tuesday May 14, 2019 @02:43PM (#19912541)
Yes, technically I could. But in reality, I have more than one task on my plate and a well-managed company will have figured out how to set the deadlines to maximize the amount of work they get for their money.

However, this is one of the things I ask about when I'm interviewing for a position -- if the company keeps track of hours rather than paying for work product, then it's not likely to be a good fit for me. So, my experience is not random chance and may not be representative of the industry as a whole.