|
|
|
|
|
by firefoxd
1 day ago
|
|
A month ago, I fell back into reading patio11's "don't call yourself a programmer" and I found it fitting. The core of the message wasn't about the title we assign to ourselves but the "other career advice". I felt compelled to write "don't call yourself a Software engineer" [0], because we are still falling into the same trap of thinking we are hired only for our technical skills. If we are just looking at a skills and these are assessed by parsing through a resume, then OP is right. We are all at a disadvantage. But the job search starts way before you are looking for a job. It's all about the connections you make along the way. [0]: https://idiallo.com/blog/you-are-an-ai-enabled-engineer-now |
|
Your customers are companies looking for someone to slot into a box called "software engineer" and so you sell yourself as such. Nothing wrong with that.
We should also note who Patrick was at the time. He was an SEO consultant and in general a business development expert. It just also happened that he was able to code. And he was very very early to the field. An SEO expert was barely a thing.
So if your only skill is software development, then of course you would call yourself that. And if your main skill is SEO or some other marketing channel, then you call yourself that.
I think the real takeaway from the advice "don't call yourself a programmer" is to search the market for higher paid opportunities, where you can still leverage coding. And you can call yourself a programmer while doing so.