Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think it depends on the kind of person you are. I’ve met some pretty reliable folks for whom their day job was just a job and it didn’t matter if they were being paid to program web applications for processing tax returns or batch processing reports. They were much more passionate about collecting accordions or attending their kids’ hockey games.

They did not give one f for, “the company,” but they were steady and reliable co-workers.

I’ve also worked with passionate “try hards,” that will get upset if they’re not using the latest-and-greatest languages and tools. They’d throw tantrums over architectural decisions. And if they didn’t settle down they’d move on to the next job in a year. Hope they found what they were looking for.



In a single comment you mixed:

* Professional reliability

* People who don't care about what type of job they do

* Hobbies

* Parenting

* People who don't care about the company, but cared about their job

* Tryhards

* People chasing the latest fad

* People that have opinions about software architecture

* Job hoppers

My initial comment was about people caring about THEIR work, not the company or anything else. It was about people not doing something they dreaded for >8h straight and thinking that's what life has for them.


> My initial comment was about people caring about THEIR work, not the company or anything else.

For me, when I say I care about my work, it implies caring about the company at least to some degree. The mix of caring for other things easily emerges. If I review a peer's code, I care about them, about the code quality, about customer satisfaction, and hence about the reputation of the company I work for. This can be selfish in a way as well, since that mix has some reflection towards how I am perceived and how I am judged as a person.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: