If developers are worried about their jobs with the way the market currently is, they should treat their personal workflows as trade secrets. My example was not specific to AI, but it applies just as much to AI workflows. In a worker's market, it was sometimes fun to share that kind of knowledge with an organization. In an employer's market, they can pay me if they want access to my personal choices.
But when I've been stuck for a while in a dysfunctional team, I've definitely seen the flip side where other people will find ways to take a lot of credit for minor iterations on my work, where management will reward my productivity with high expectations and high pressure to continue the trajectory they perceive in a single idea, and when the tool becomes a support burden because too many people think it should solve all of their other problems too and I'm now perceived as being the owner of this thing they depend on.
If your only goal is to maintain a performance lead on your peers, you either need to gain and keep an advantage or find ways to actively make your coworkers disadvantaged (or both). And if you're already doing 1) then 2) isn't a far stretch.
> would you like to work on a team full of people like you?
If their team is already like this, what choice do they have? It's a prisoners dilemma where everyone else is defecting and I'm the sole cooperator.
IMO the onus for solving this is on the business owner, either through establishing a knowledge sharing culture or more comprehensive performance evaluation that rewards these innovations.
Nice passive aggressive dig!
So while it might be nice to say I won't share, boss-man can certainly make it so I must share.
Boss-man actually has a very difficult time turning legal theoretic right into actual deliverables.
I mean, according to your employment agreement, that code is owned by your employer, since you wrote it as an employee for use at work. They could easily demand that you share it, if they knew it existed.
This just illustrates that smart people figure out their own productivity/time-saving shortcuts at work, and little scripts and tools like this are part of it. Happens all the time. Other employees don't, and just plod through whatever manual process they were trained to do.
You have to get used to acting within the grey area and playing politics. Your counterparty (your employer) certainly does. Every businessperson is good at it, or they wouldn't be successful.
In any transactional relationship - which employment is - when you want to do something, don't think: I can't do this because they wouldn't like it. Instead think: what are the likely consequences of doing this? Are they positive or negative for me, on net?
That sounds like a toxic environment. Sharing those types of things is how I got the recognition to get ahead in my career and I have never once regretted it.
If your employer is expecting that you selflessly share your time for free, you’re getting fucked. Most people are paid to do their job. They are, of course, then expected to work for their employers while on the clock.
What I find strange about this is that in 2020 nobody would be this openly cynical and selfish about, say, good Python idioms, a useful emacs configuration, git shortcuts, etc. This attitude of "your job is to deliver value for the customer, anything else is a distraction, and if you share your hard-earned value-delivery techniques with others then you are a sucker" - this is new, and very disconcerting.
I understand there's not much we can do to stop the cyberpunk dystopia, but do we have to leap in head-first?
I definitely saw people have concerns about vimrc files and their personal library of shell scripts well before 2020, and I've seen people early in their career get burned by sharing it too. They had a tool that made them productive, it got out of their hands, and suddenly they're getting negative feedback from someone who tried using it and it didn't meet their expectations, or it got checked into the repository and now the script they used at their last job too has their current job's copyright notice and license on it, and they're perceived as being petty for trying to claw back their own intellectual property because they didn't go to the trouble of slapping legalese all over their personal tools.
If your employer is extremely spiteful, they might burn a pile of cash to hurt you. But that's not normal.
>it got checked into the repository and now the script they used at their last job too has their current job's copyright notice and license on it, and they're perceived as being petty for trying to claw back their own intellectual property
Where someone is causing a fuss trying to claim ownership of something they never actually owned and thinking the other people are the ones being unreasonable.
This mindset has always existed in the area we're talking about, and not because it's sharing something to speed up with. It's because we don't want to get stuck doing a second job supporting the tool.
I've built all sorts of random tools for myself over the years and haven't shared a single thing, but share the tips and tricks like your examples all the time.
If they gave immediate raises or bonuses for stuff like this, then things would change.
And I'm not a "at work we're a family!" guy, but I wish we could just be excellent at our jobs and share it with each other without worrying if I'm digging my own grave.
None of it is actually that crazy that everyone else could think up.
What I've noticed in my own experience here is that even when I do share my own prompts/skills few people use them (or alternatively they were so basic that everyone already had their own version).
e.g. If someone doesn't care about xyz before AI, they probably won't after AI even if I serve them it on a silver platter.
Does that person rationally go find more work to take on with that reclaimed time? Probably not unless it's their company or exceptional motivating circumstances exist.
yet I don't see anyone question whether management will be just as excited to see that less work is needed and that it'd just result in layoffs
Contrast to remote work where the benefit was extended to all regardless of performance, thus becoming a large target for management to cut.
I think the talk about management & capital demanding ROI will be the inflection point to watch, as a downstream effect could be AI haves & have-nots, depending on open weight models' competitiveness and local capability relative to the SOTA models.
My company set up a “prompt of the week” award and brown-bag sessions to help spread adoption. We also have teams meant to develop these workflows. Clearly, they set these events up to play it off as their own productivity. Without a real (read “monetary”) incentive or job security, the risk and cost of spreading the knowledge falls squarely on the developer.