Hacker News new | past | comments | ask | show | jobs | submit login

> They want every codemonkey to be easily replaceable.

Most folk/bosses who are risk averse actually want their codemonkeys to be easily replaceable (although admittedly, they might not realise it!). Nobody likes/wants a system with a single-point of failure.

If I'm working for a client, and get hit by a bus tomorrow, it is rather reassuring for the client if they know the work they've paid for so far can be fairly easily picked up and completed/maintained by another hire.

I deliberately make it part of my strategy to bring a client's attention to this kinda stuff, in an ongoing fashion. It means I can happily spend time on e.g. documentation and/or other technical debt, because my client understands the values of these things.

My actions to make myself (more) replaceable lowers my client's risks. (A good client understands this, and might acknowledge and support such efforts with fatter pay checks: someone who helps lower their risks can be a particularly valuable asset)

I guess it depends on one's attitude and understanding towards 'being replaceable', and how one pitches that understanding.




> Most folk/bosses who are risk averse actually want their codemonkeys to be easily replaceable

Absolutely, everything else wouldn't be very smart. Maybe my comment came off a bit more negative than I intended to.

I don't blame google if this mindset is reflected in their tools but I wouldn't like to have to work with that.




Join us for AI Startup School this June 16-17 in San Francisco!

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

Search: