|
|
|
|
|
by _heimdall
506 days ago
|
|
I draw the line at doing work that I can be proud of. That doesn't mean going out of my way and overworking myself, but it does mean being a good person to work with and writing quality code. I tend to stick to the scope of work asked of me (though not always) for the reasons in the article, but I don't just phone it in. I put effort into writing good code, tests, and PR reviews. In my experience, when it comes to getting the next job the only thing that really matters either way are references. If you were a too co-worker and did at least put in the effort to do good work within bounds of the scope asked for, you shouldn't have a problem. |
|
That's important. I spend more awake time working/thinking about work than really else. I don't know that it's healthy, but at least I want to be proud of the outputs if I am going to spend this much time on something. I just can't really show up and mail it in, I'm just not wired that way, and suspect that a lot if us aren't.