Comment

Comment by cletus

So there are two issues with this:

1. If I were looking to hire someone and read this, I would immediately be turned off. Why? Because part of being an engineer (or any employee really) is doing a bunch of stuff people don't enjoy doing. This includes:

- Writing documentation

- Writing tests

- Fixing bugs

- Talking to partners about a change/launch

- Talking to lawyers

- etc

So I would be wondering: if you're signaling you don't want to do those things, that means someone else will need to do all that for your code, which is not great for them and tends to be much worse.

Like you're basically saying you want to cherrypick the parts you enjoy and not give a damn about anything else. You might say you're only costing $1/hour but the risk of a bad engineer can mean you're still expensive or a loss.

2. You don't factor in the time cost of me or my team in onboarding you, dealing with you, dealing with your code and so on. That's a big part of the filtering in hiring. People are deciding if they can justify that time investment and the opportunity cost involved.

parent cletus 5 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton