20 year industry vet here. Yeah, no thank you. In the age of AI, developer productivity and job security will involve your proprietary workflow. It no longer makes sense to share your knowledge with the world.
Two years ago, I'd consider this attitude as ungrateful. Today, this attitude is 100% correct and I slowly start to be like that.
People might think I'm a dick, I don't care, my tools, my knowledge, my job security. I actually recently thought of nuking the entire IaC setup and go back to shell scripts on random virtual machines. Too bad that Claude can figure things like that out pretty easily. Well, the world sucks now.
I can appreciate why you'd come to this conclusion, but may I offer one idea that I think you've potentially overlooked?
Unless you are a solo founder running your own company by yourself (in which case ignore the rest of this comment!), then your fundamental job security is likely to be predicated on the survival of your company as well as the survival of your own individual job itself.
From the company-survival POV, all companies are engaged in competition (unless they have a total monopoly).
Therefore I ask you to consider the competitive scenario, of whether a competitor to your company who adopts a more collaborative culture, might be more likely to outcompete your company (assuming everyone you work with in your own company adopts a similarly "dick"-ish stance, to use your own words), and therefore you lose your job due to being out-competed, rather than due to internal politics or due to a failure to guard your personal expertise?
Maybe you say -- I don't care if my company is out-competed, I'll just get another job. Ok fair enough, but might it not be possible that, in a future job interview, they may ask you for examples of collaboration? And if you commit to a monk-like devotion to solitude and privacy, then maybe you are undercutting your own future hireability?
There are no free lunches [1]. By optimizing for one thing (what you view as protecting yourself), you might be sabotaging another dimension (your company's overall competitiveness, or your future hireability).
Anyway, nobody knows shit about shit. I certainly don't pretend to be an authority, but I would caution you to avoid coming to a hasty conclusion, especially since it seems emotions are involved and possibly clouding your judgement. You may also consider whether this decision to protect yourself in this way, is in itself a premature (micro?) optimization of a sort, and if whether you might be failing to optimize on a more macro level.
hackmack10 · · focus · HN ↗
I'd highly advise people don't do this.
mystifyingpoi · · focus · HN ↗
People might think I'm a dick, I don't care, my tools, my knowledge, my job security. I actually recently thought of nuking the entire IaC setup and go back to shell scripts on random virtual machines. Too bad that Claude can figure things like that out pretty easily. Well, the world sucks now.
strgcmc · · focus · HN ↗
Unless you are a solo founder running your own company by yourself (in which case ignore the rest of this comment!), then your fundamental job security is likely to be predicated on the survival of your company as well as the survival of your own individual job itself.
From the company-survival POV, all companies are engaged in competition (unless they have a total monopoly).
Therefore I ask you to consider the competitive scenario, of whether a competitor to your company who adopts a more collaborative culture, might be more likely to outcompete your company (assuming everyone you work with in your own company adopts a similarly "dick"-ish stance, to use your own words), and therefore you lose your job due to being out-competed, rather than due to internal politics or due to a failure to guard your personal expertise?
Maybe you say -- I don't care if my company is out-competed, I'll just get another job. Ok fair enough, but might it not be possible that, in a future job interview, they may ask you for examples of collaboration? And if you commit to a monk-like devotion to solitude and privacy, then maybe you are undercutting your own future hireability?
There are no free lunches [1]. By optimizing for one thing (what you view as protecting yourself), you might be sabotaging another dimension (your company's overall competitiveness, or your future hireability).
Anyway, nobody knows shit about shit. I certainly don't pretend to be an authority, but I would caution you to avoid coming to a hasty conclusion, especially since it seems emotions are involved and possibly clouding your judgement. You may also consider whether this decision to protect yourself in this way, is in itself a premature (micro?) optimization of a sort, and if whether you might be failing to optimize on a more macro level.
[1] <a href="https://en.wikipedia.org/wiki/No_such_thing_as_a_free_lunch" rel="nofollow">https://en.wikipedia.org/wiki/No_such_thing_as_a_free_lunch
Godsend69 · · focus · HN ↗
[dead]