Earlier quoted context omitted.
What I get a bit annoyed is companies forcing AI tools, getting usage metrics and actively hunting the engineers that don't use the tool "enough", I've never seen anything like it for a technically optional tool. Even in the past, aside from technical limitaions, you were not required to use enough of a tool. It just sounds like a giant scheme to burn through tokens and give money to the AI corps, and tech directors…
The only thing I've mandated for engineers is that folks give it a try occasionally, as models, best practices, and tooling improves. I'm currently tracking exactly two numeric metrics: total MAUs (to track the aforementioned), and total DAUs (to gauge adoption and rightsize seat-licensed contracts.)
I'm OK being left behind, thanks
331–340 of 800 posts
Re: I'm OK being left behind, thanks
#332Earlier quoted context omitted.
But it's so easy to try something like Claude Code. It's not like you need to get up to speed. There is no learning curve*, that's the nature of AI. Just start using it and you'll see why it has attracted so much hype. *I should qualify that "using" CC in the strict sense has no learning curve, but really getting the most out of it may take some time as you see its limitations. But it's not learning tech in the tradi…
I've been playing with it on weekends for the last few months. 9 out of 10 projects, it's failed. Projects as simple as "set up a tmux/vim binding so I can write prompts in one pane and run claude in the other". Fails. I've been coding for over 20 years. If there is no learning curve, why doesn't it work for me? You can't say I'm not using it right, because if that was true, then all I need to do is climb the learnin…
That's what's being asked of me in my last two jobs. Vibe code it, if it's bad just throw it away and regenerate it because it's "cheap". The only thing that matters is that you can quickly generate visible changes and ship it to market.
Out of frustration I asked upper management (in my current job), if you want me to use AI like that then I'll do it. But when it inevitably fails, who is responsible? If there's no risk to me, I will AI generate everything starting today, but if I have to take on the risk I won't be able to do this.
Their response was that AI generates the code, I'm responsible for reviewing it and making sure it's risk free. I can see that they're already looking for contractors (with no skin in the game) that are more than willing to run the AI agents and ship vibe code, so I'm at a loss on what to do.
Re: I'm OK being left behind, thanks
#333> If this tech is as amazing as you say it is, I'll be able to pick it up and become productive on a timescale of my choosing not yours. Broadly speaking, I think this is a wise assessment. There are opportunities for productivity gains right now, but it I don't think it's a knockout for anyone using the tech, and I think that onboarding might be challenging for some people in the tech's current state. It is safe to…
It also seems like skills with particular tech (prompt engineering, harnesses, mixture of experts set ups) doesn't always necessarily pay off when there's a sea change. Hard to predict what you'll want in a few years anyway, right?
Prompt engineering as a specific skill got blown out of proportion on LinkedIn and podcasts. The core idea that you need to write decent prompts if you want decent output is true, but the idea that it was an expert-level skill that only some people could master was always a lie. Most of it is common sense about having to put your content into the prompt and not expecting the LLM to read your mind.
Harnesses isn’t really a skill you learn. It’s how you get th LLM to interact with something. It’s also not as hard as the LinkedIn posts imply.
Mixture of Experts isn’t a skill you learn at all. It’s a model architecture, not something you do. At most it’s worth understanding if you’re picking models to run on your own hardware but for everything else you don’t even need to think about this phrase.
I think all of this influencer and podcast hype is giving the wrong impression about how hard and complicated LLMs are. The people doing the best with them aren’t studying all of these “skills”, they’re just using the tools and learning what they’re capable of.
Re: I'm OK being left behind, thanks
#334> If this tech is as amazing as you say it is, I'll be able to pick it up and become productive on a timescale of my choosing not yours. Broadly speaking, I think this is a wise assessment. There are opportunities for productivity gains right now, but it I don't think it's a knockout for anyone using the tech, and I think that onboarding might be challenging for some people in the tech's current state. It is safe to…
But it's so easy to try something like Claude Code. It's not like you need to get up to speed. There is no learning curve*, that's the nature of AI. Just start using it and you'll see why it has attracted so much hype. *I should qualify that "using" CC in the strict sense has no learning curve, but really getting the most out of it may take some time as you see its limitations. But it's not learning tech in the tradi…
If you have try teaching someone something from the absolute ground up, you will quickly realize that a huge number of things you now believe are "standard assumptions" or "obvious" or "intuitive" are actually the result of a lot of learning you forgot you did.
Re: I'm OK being left behind, thanks
#335Earlier quoted context omitted.
But it's so easy to try something like Claude Code. It's not like you need to get up to speed. There is no learning curve*, that's the nature of AI. Just start using it and you'll see why it has attracted so much hype. *I should qualify that "using" CC in the strict sense has no learning curve, but really getting the most out of it may take some time as you see its limitations. But it's not learning tech in the tradi…
> There is no learning curve*, that's the nature of AI. There isn't? Then why is it that whenever devs have tried it and not achieved useful results, they're told that they just haven't learned how to use it right?
Re: I'm OK being left behind, thanks
#336There's value in being early - in the right thing. - If you'd invested in Bitcoin in 2016, you'd have made a 200x return - If you'd specialized in neural networks before the transformer paper, you'd be one of the most sought-after specialists right now - If you'd started making mobile games when the iPhone was released, you could have built the first Candy Crush Of course, you could just as well have - become an Acti…
I was ahead of the game with my intimidate expertise in ActionaScript and Silverlight! I made 3D engines in browsers well before WebGL was a spec.
It was quite profitable for a few years, then poof. Dead end lol
Re: I'm OK being left behind, thanks
#337> If this tech is as amazing as you say it is, I'll be able to pick it up and become productive on a timescale of my choosing not yours. Broadly speaking, I think this is a wise assessment. There are opportunities for productivity gains right now, but it I don't think it's a knockout for anyone using the tech, and I think that onboarding might be challenging for some people in the tech's current state. It is safe to…
What I get a bit annoyed is companies forcing AI tools, getting usage metrics and actively hunting the engineers that don't use the tool "enough", I've never seen anything like it for a technically optional tool. Even in the past, aside from technical limitaions, you were not required to use enough of a tool. It just sounds like a giant scheme to burn through tokens and give money to the AI corps, and tech directors…
This is exactly what's happening. The top 5 or 6 companies in the s&p 500 are running a very sophisticated marketing/pressure campaign to convince every c-suite down stream that they need to force AI on their entire organization or die. It's working great. CEOs don't get fired for following the herd.
Re: I'm OK being left behind, thanks
#338Re: I'm OK being left behind, thanks
#339>I didn't use Git when it first came out. This really hinges on what you mean by "didn't use git". If you were using bzr or svn, that's one thing. If you were saving multiple copies of files ("foo.old.didntwork" and the like), then I'd submit that you're making the point for the AI supporters. I consulted with a couple developers at the local university as recently as a couple years ago who were still doing the copy…
Was "when it first came out" a confusing limiter, there? I guess it seems like the article was making the point that jumping on git the day it came out could've just meant learning the betamax of repos, and that it was better to wait a bit to see what mature tech looked like, rather than waiting until 202X to realize that saving multiple file versions was suboptimal. I don't understand how this, at all, makes "the po…
Or have bet on Mercurial. Which is also close to dead. Or darcs, which has been big in certain environments and now practically extinct.
Re: I'm OK being left behind, thanks
#340Earlier quoted context omitted.
Yeah, maybe empathise was the wrong word. I certainly empathise with the feelings, I just struggle to see how people cannot use it to get more done. I'm also daydreaming about other careers instead of doing something useful.
> I just struggle to see how people cannot use it to get more done. To be blunt about it, there's a decent chance I'll be quitting this job later this year, largely because of the AI push. I just hate these tools and I do not want to work this way. Losing an employee is a pretty big cost to the company. I guess the AI stuff is probably worth it to them, but there's a downside to it, too.