Live data from Hacker News

Hermit Programmers Are Dead

cesarsotovalero.net

121–130 of 133 posts

Re: Hermit Programmers Are Dead

#121
post #120
post #105

Earlier quoted context omitted.

From that light, I think the article's point is that rules of the environment have changed so much that the archetype of the lone-programmer is becoming obsolete in the workforce. I've always worked at agencies so I get exposure to a great deal of projects, and I do partly see what they are saying. More and more parts of orgs are becoming intertwined with software, and they're becoming better at software, requiring y…

Climate is getting warmer so we need humans that can stand higher temperatures.

Hahahaha

Re: Hermit Programmers Are Dead

#122

Earlier quoted context omitted.

I'm guessing the article refers to a form of "cowboy coding" or similar things promoted along with the myth of the 10x programmer, where there are attempts to apply that practice (of siloing developers and having them only write code to satisfy their needs) into the organizational environment. And I'd agree with the article there, in my experience that's awful and leads to everyone being upset. The hermit programmer…

It all depends on what your perspective is. This article seems to speak to web devs, and I agree with their premise for the most part. But it doesn't work for single indie game developers. Hermit programming is very effective in that space (insert Stardew Valley reference here). So I come back to... why bother even writing this? It's no secret that poor "team players" are a nightmare to work with.

I'd be careful with that, I don't see why game development would be any different. You still have to focus on customer satisfaction. Single indie game developers succeeding without doing that seems to be an exception, not the rule. For every Stardew Valley, it feels like I've read a dozen postmortems from people who went off developing something for years only to find out that nobody wanted it and there was no audience for it.

Re: Hermit Programmers Are Dead

#123
Honestly, I thought the term was "cowboy coder," but maybe my vernacular is archaic.

Not to pile-on, but I don't understand the bizarre disparagement of computer science. There are far too many programmers, hermit or otherwise, who don't know what big-O notation is, which data structure(s) to choose in a particular scenario based on requirements, algorithm design, or the Church–Turing conjecture. I would also add variations of software engineering methodologies are obligatory knowledge of a professional programmer for situations like using strict, formalized waterfall development in life-safety systems. Credentialed Professional Engineers supervising and/or implementing critically-important code are also Good Things in such situations too.

Re: Hermit Programmers Are Dead

#124
post #105

This is such a strange thing to choose to write a derogatory article about. If you are a singular developer that is only writing code to satisfy your needs, then you can do whatever the hell you want. If you have to work in a collaborative environment, then you will likely need to play by the rules of that environment. There's not much else to say about it. The stuff about automation doesn't even seem to fit in this…

From that light, I think the article's point is that rules of the environment have changed so much that the archetype of the lone-programmer is becoming obsolete in the workforce. I've always worked at agencies so I get exposure to a great deal of projects, and I do partly see what they are saying. More and more parts of orgs are becoming intertwined with software, and they're becoming better at software, requiring y…

No longer program for a living but even 20 years ago that kind of stuff was 80% of my daily job as a LAMP web programmer. I wrote as little code as possible, and only to glue stuff together. The challenge was to understand the pieces to fit together and even just remember how to access all the accounts required. In that light, I'm not seeing much has changed in the past few decades.

Re: Hermit Programmers Are Dead

#125

I've been working both as 1-person team for years but also in larger teams for the same amount of time. In my experience the hermit programmer is some sort of a myth. It's true that sometimes tech staff is more separated from more non-tech staff but that is always a management decision because they think it makes people more efficient. In fact as a 1-person team it's usually necessary to interface much more often wit…

I'm a 1-person remote team, and I virtually never deal with non-technical people. So I'd say hermits most certainly do exist.

Re: Hermit Programmers Are Dead

#126
People have been prophesying the dawn of no-code since before I was even born, and yet we're yet to see the demise of programmers.

Also:

> if you want more SSD storage or CPU processors, you just need to add them to the basket

I used to say "CPUs are cheaper than developers", until the day I discovered that's not always true, and had to spend several months refactoring the product we were building so that it could actually scale properly. Funnily enough, Terraform doesn't magically solve P=NP.

Re: Hermit Programmers Are Dead

#127

This is such a strange thing to choose to write a derogatory article about. If you are a singular developer that is only writing code to satisfy your needs, then you can do whatever the hell you want. If you have to work in a collaborative environment, then you will likely need to play by the rules of that environment. There's not much else to say about it. The stuff about automation doesn't even seem to fit in this…

It all ties in perfectly. A.I. is coming for Johnny Weekend's lunch. It will build an evil version of every conceivable widget and market it to your other hobbyist friends better than you could, humiliating your entire existence further. Do you want that? then you had better sign up to my productivity cult blog spam to have a chance at beating it.

Re: Hermit Programmers Are Dead

#128
post #43

This is just wrong. Imaginary computing (based on language models) and blockchain or other source of truth is the future. As hermit programmers we can rely on AI to make a prediction as to when a task will be done, generate documentation for us, generate tests https://mullikine.github.io/posts/imaginary-reflection/ , generate, etc. Any deployment system that doesn't use language models will be fragile as the time to…

There is only one place for Blockchain - in the center of the Bullshit-Bingo tile matrix.

Firstly, what I'm saying does not rest on blockchain being the source of truth. It could, for example, be another language model from a corporation that you trust. Secondly, if you can't see the value of a blockchain or decentralised cryptography as a way to deal with the issues of consensus, then that's not my problem.

Re: Hermit Programmers Are Dead

#129
Sounds like this person is swallowing and licking up whatever corporate gives them. But as many have or will find out, companies don't love you like that. Lifetime employment at the same company is just about dead too.

When that pay raise doesn't happen, when cuts to the staff come down, when that other or junior person get's chosen or promoted over you, when your job get's outsourced, etc... It's about their profits, not you.

Somehow this person has got themselves so twisted up in the corporate game, they don't know the difference between "hermit programmer" and "bad programmer".

Below is a list of traits of bad programmers. Saying that only an independent or hermit will do one or more is to be blind to reality:

1) they don’t plan 2) never know if they are going to finish a task 3) they don’t document 4) their code is not reusable 5) they don’t test 6) code they write is full of bugs 7) they don’t refactor 8) the software cannot evolve 9) they don’t have good communication skills 10) they don’t diversify their skills 11) powerful AI will take over their workplaces

As for AI, corporate is more likely to use such to eliminate jobs internally, to save themselves a few bucks. In addition, corporate environments and teams don't produce bug-free code and management can lead a project "off a cliff" to where it fails. Just because a team of people think they are doing the right things, doesn't mean they actually are nor is there any guarantee of success. Doing things by committee can also be a source of vicious arguments, resentment, and project stagnation. Every team isn't effective or efficient, so can depend on the situation.

Bad programmers can exist in corporate environments and teams too, because they are able to abuse the power of their position or fool management for a while or prior to them jumping ship unexpectedly to another company.

Re: Hermit Programmers Are Dead

#130
post #105

Earlier quoted context omitted.

From that light, I think the article's point is that rules of the environment have changed so much that the archetype of the lone-programmer is becoming obsolete in the workforce. I've always worked at agencies so I get exposure to a great deal of projects, and I do partly see what they are saying. More and more parts of orgs are becoming intertwined with software, and they're becoming better at software, requiring y…

> From that light, I think the article's point is that rules of the environment have changed so much that the archetype of the lone-programmer is becoming obsolete in the workforce. Tell that to millions of small-medium businesses, if their needs can't be met by squarespace (and anything other than a brochure really can't) They reach out in their network for what could be looked at as a 'computer/internet handyman'.…

Right, there are definitely lots of very normal software projects going on. But it is worth noting that this is a new way that software is being managed and it will be up to some developers to work within it.

I don't agree with the article by the way, I don't see SaaS/cloud computing eating software at all levels.

Post reply on HN