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

The thing for me isn't that you'll necessarily climb the ranks as a result of this - but that any job you can automate away is a bloody boring job to do. Even if you don't automatically take on new responsibilities as a result, your job now has less boring bits in, so it's still a win.


It's also a refreshing way to think about jobs and keep t6hem new.Personally when I take a new job I like to think about how long it will take for me to get the organisation in a position that they won't need me any more. It gives me a degree of control I enjoy, it leaves me with a grateful employer and some achievements on my CV that the next employer will like. "Why did you leave?" I had done my job.

I'm desparately trying to remember who it was who wrote the article about how - when employing someone new - you should explicitly work with them on the assumption that they won't be around for ever - so what do they want to achieve while they are there and what do you want them to achieve. It muight have been Joel, but I can't find it. Anyone?




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

Search: