3 ms·
"Minimizing hours worked" is a great positive sign. You hire a programmer to solve problems (or better yet, identify and solve problems), not to sit on their bu
by itamarst 7y ago
"Minimizing hours worked" is a great positive sign. You hire a programmer to solve problems (or better yet, identify and solve problems), not to sit on their butt for the maximum number of hours.
There's always a limited amount of resources (time, money, etc), regardless of how many hours are worked. So someone whose goal is minimizing hours worked will tend to come up with much better solutions than someone whose only solution is to work longer hours. Because instead of saying "I'll just work longer!" they'll actively try to come up with a fundamentally more efficient solution.
(Long version: https://codewithoutrules.com/2018/02/11/working-long-hours/ https://codewithoutrules.com/2018/02/11/working-long-hours/)
- SketchySeaBeast 7y ago> "Minimizing hours worked" is a great positive sign. You hire a programmer to solve problems (or better yet, identify and solve problems), not to sit on their butt for the maximum number of hours. That assumes the client is paying by the problem and not by the other. Sadly, while there is project work, every place I've worked has also had a huge emphasis on billable hours.
- itamarst 7y agoYeah, billable hours is bad (for everyone). Jonathan Stark talks about this a lot: https://jonathanstark.com/ https://jonathanstark.com/ Lots of programming jobs aren't tied to that, though.