|
|
|
|
|
by arasx
1651 days ago
|
|
Software engineering is one of the easiest jobs out there from an ability to track your output standpoint. I think a lot of the commenters implying "if you have 10 hours to cut down a tree, use the 9 to sharpen your ax" and using that to argue against code-line-output != productivity. Certainly in cases where you need to put a lot of thinking or research to come up with a very elegant solution in a few lines, no one can argue you have been productive. But more often than not, we work on simple CRUD or basic apps that were stretched among hours, flying under radar from one stand up to the next, like you mentioned. It's a common problem so you are not the only one. Especially in large teams, or teams that are run by PM's who are not very savvy to open the hood and understand what had been going on. In most of the opposite cases, it's also awkward for some managers to challenge what you have produced in a day. It starts more on the foot of discovering: is there another mental block with the employee, are they having motivation issues (maybe you fall into this group), is there a training/onboarding issue? And I have seen first hand, most of the time - they give up and mediocre output continues. Laziness/talent/ethics of it is not our place to comment for you - but it sounds like this would be a boring job to continue. Sure you can make good money and live a comfortable life, but I can't fathom if it would be fulfilling in the long run for me. Find what stirs your passion and try to apply to work. You have the luxury to do so. |
|