Today, I received the comment below from a "software engineer". For once, I was left speechless. The title is in quotes because, frankly, I don't think this person has earned the title they use.

"I don't dislike people but I dislike interacting with them. I didn't get into computers so I could spend time interacting with people. With programming, I don't really need a team. I'm sufficient to get the job done."


Had this discussion occurred during an interview, I would have thanked the candidate for their time and let them know the process ends here.

Few things are brighter red flags than boldly stating how you *don't want* to interact with people.

I'm sure these people are only hired because they pass a series of algorithmic puzzles without anyone checking their cultural fit.

Individuals and interactions are what our industry is all about.

We interact with clients, stakeholders, users, and other developers daily — the more often, the better.

The sad thing is how this enforces the stereotype of a lone coder cowboy who spends their days in isolation crunching Jira tickets to get the job done.

· · Web · 1 · 1 · 3

Unfortunately, the more we see creative software engineering as monotonous ticket crunching instead of learning and experimentation, the more we compare producing software to building houses.

With that analogy, you can only go wrong.

@nikoheikkila Luckily the perfect Jira ticket fall mysteriously from sky onto your table, right next to your LED keyboard. Nice. You just have to write some lines of code, throw them in the build pipeline and collect the check. /s

Sign in to participate in the conversation
Mastodon for Tech Folks is shutting down by the end of 2022. Please migrate your data immediately. This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!