I'm Not a Programmer
A woman on Tinder asked me if I was a programmer.
I said:
“No.”
This was apparently misleading.
Later, in the same general interaction, we were discussing:
- React;
- Angular;
- Prototype;
- Scriptaculous;
- WinGet manifests;
- Chocolatey;
- SideQuest Easy Installer;
- public package manifests;
- and whatever other technical archaeology fell out of my head that evening.
At one point I was literally submitting a WinGet manifest while talking to her.
So from her side there was probably a reasonable question:
“What exactly does this man think a programmer is?”
Easy.
A programmer is somebody who identifies as a programmer.
I don't.
I am a guy who programs.
That is not the same sentence.
Activities Are Not Identities
I write code.
I also configure networks.
I fix computers.
I build infrastructure.
I work on CI pipelines.
I mess with Linux.
I mess with Windows.
I have built game-engine infrastructure, deployment tooling, automation, web applications, installers, services, and things that probably should not have existed but now do.
I have also repaired vehicles.
I have fixed electrical cables.
I have worked at a gas station.
I have cooked food.
I have driven motorcycles across countries.
None of this requires me to say:
“This is what I am.”
It is what I do.
Sometimes.
There is a difference.
The Identity Compression Problem
People love labels because labels compress information.
“What do you do?”
“Programmer.”
Done.
One word.
Very efficient.
Except the compression is lossy.
Ask me whether I program and the answer is obviously yes.
Ask me whether I am a programmer and now you are asking an identity question.
That is where I stop cooperating.
Because once the label lands, people begin attaching the rest of the package.
Programmer.
Therefore:
- probably sits at a desk all day;
- probably likes a certain kind of conversation;
- probably has a certain personality;
- probably has a certain career path;
- probably thinks about himself through technology.
No.
I write software because I know how to write software.
Sometimes because I am paid.
Sometimes because I need something.
Sometimes because something annoys me.
Sometimes because I looked at a problem and thought:
“Fuck it. I can build that.”
That is not an identity.
That is a capability.
Same With IT
I am also not an “IT guy.”
I do IT.
Sometimes absurd amounts of it.
I have had evenings where a television could not reach Plex and somehow, several hours later, I was deep inside DNS, Pi-hole, dnscrypt-proxy, VPN routing, network behavior, and undocumented Windows nonsense.
That does not mean I wake up every morning and think:
“Ah yes. I am IT Man.”
I am just a guy who knows enough about these things to be dangerous.
Occasionally useful.
Frequently annoyed.
The Tinder Problem
This is why the Tinder exchange was funny.
She asked:
“Are you a programmer?”
I answered honestly:
“No.”
Then later:
“I’ve submitted a dozen manifests to the public repo.”
Then:
“I was on the Chocolatey dev team once upon a time.”
Then:
“I built one of those for a job interview.”
At no point did the original answer become false.
It merely became inconvenient.
The category she selected was too small.
The Resume Is Not the Person
This probably creates problems.
Employers want a title.
Dating apps want categories.
Forms want a profession.
LinkedIn wants an identity stack.
Software Engineer.
Architect.
Technical Lead.
Staff Engineer.
Principal Engineer.
Head of Engineering.
Fine.
Use whatever label is operationally useful.
But internally?
No.
I am not the title.
I am not the stack.
I am not the activity.
I am not a programmer.
I am a guy who programs.
I am not an IT guy.
I am a guy who does IT.
Sometimes I am a guy who writes a blog post because one sentence on Tinder accidentally turned into a philosophical argument about identity.
Apparently I am also that.
For now.