Hermit Programmers Are Dead
21–30 of 133 posts
Re: Hermit Programmers Are Dead
#22was this written by GPT-3?
Re: Hermit Programmers Are Dead
#23The text seems to imply that people on the "technical track" (only programming) are doing so because of some flaw in their personality. That is absolutely not the case! This is not a good way to launch "hermit programmer" as a new term. The term is not defined and mentioned only three times in the entire text (once in the title). I suppose most readers have different assumptions on its meaning. I know a few "hermits"…
* they don’t plan how they're going to finish a task
* they don’t document
* they don’t test
* they don’t refactor
* they don’t know anything about production infrastructure
* they don’t have good communication skills
* they don’t try to diversify their skills
I'd agree with the article that this kind of programmer is "dead".... but as far as I know they've been dead for a very long time already.Re: Hermit Programmers Are Dead
#24As they don’t plan, you never know when (or if) they are going to finish a task. As they don’t document, their code is not reusable because nobody knows how it works. As they don’t test, chances are the code they write is full of bugs. As they don’t refactor, the software cannot evolve. As they don’t handle infrastructure, their code has only been executed on their machine, and only God knows what will happen when the code runs in production. As they don’t have good communication skills, they do not know how to sell what they do to the market, which is why they are always behind the competence. As they don’t diversify their skills, powerful AI will take over their workplaces.
I think in the end the author took the attributes of "Bad" programmers and applied them to "Hermit" programmers.
So yeah I agree Bad Programmers are going to have a Bad time in future.
Re: Hermit Programmers Are Dead
#25They've been saying this since the 80s. The magical world where prolog/pascal/java/NPM solves all your problems is eternally 3 years away.
Re: Hermit Programmers Are Dead
#26The text seems to imply that people on the "technical track" (only programming) are doing so because of some flaw in their personality. That is absolutely not the case! This is not a good way to launch "hermit programmer" as a new term. The term is not defined and mentioned only three times in the entire text (once in the title). I suppose most readers have different assumptions on its meaning. I know a few "hermits"…
There's a part of the article at the bottom that defines a Hermit programmer more precisely: * they don’t plan how they're going to finish a task * they don’t document * they don’t test * they don’t refactor * they don’t know anything about production infrastructure * they don’t have good communication skills * they don’t try to diversify their skills I'd agree with the article that this kind of programmer is "dead".…
Re: Hermit Programmers Are Dead
#27The text seems to imply that people on the "technical track" (only programming) are doing so because of some flaw in their personality. That is absolutely not the case! This is not a good way to launch "hermit programmer" as a new term. The term is not defined and mentioned only three times in the entire text (once in the title). I suppose most readers have different assumptions on its meaning. I know a few "hermits"…
There's a part of the article at the bottom that defines a Hermit programmer more precisely: * they don’t plan how they're going to finish a task * they don’t document * they don’t test * they don’t refactor * they don’t know anything about production infrastructure * they don’t have good communication skills * they don’t try to diversify their skills I'd agree with the article that this kind of programmer is "dead".…
I think they are quite alive.
Re: Hermit Programmers Are Dead
#28I feel bad saying it but I’m just not willing to read something this long until eventually it comes to the point.
Yeah I wish I hadn't read it either.
Re: Hermit Programmers Are Dead
#29It was a much simpler way of doing things because the number of users was known, and you didn't need to scale past that.
Also, your users were known, and thus you really didn't have to worry about security, for the most part.
Programming was a matter of finding the right libraries, and doing plumbing, back then, as it is now. Nothing has really changed in that aspect.
What has changed is that productivity has plummeted as a result of having to fragment systems across servers, networks, and client platforms, with many additional leaky layers of abstraction added to attempt to compensate.
I watched as the office network I was hired to support in 1997 became so reliable that by 2013 there was almost nothing for me to do. The tools that can produce code to run in that environment from 1997 only fail because we've switched from 32 to 64 bit environments.
All those layers of plumbing need to be managed, and it's programmers, not some AI that is going to do the job.
Re: Hermit Programmers Are Dead
#30The text seems to imply that people on the "technical track" (only programming) are doing so because of some flaw in their personality. That is absolutely not the case! This is not a good way to launch "hermit programmer" as a new term. The term is not defined and mentioned only three times in the entire text (once in the title). I suppose most readers have different assumptions on its meaning. I know a few "hermits"…
Or you know just want to make a good job, and not have to "live" in a artificial and complete dishonest "family", like the googles of the world try to portrait them self's.