Earlier quoted context omitted.
I mean get onboard or fall behind, that's the situation we're all in. It can also be exciting. If you think it's still just slop and errors when managed by experienced devs, you're already behind.
The obvious pulling ahead from early AI adopters/forcers will happen any moment now... any moment
AI-First Company Memos
71–80 of 216 posts
Re: AI-First Company Memos
#72Earlier quoted context omitted.
Then, you might even tinker with some AI stuff on your own terms, you never know. :) Or install a landline (over 5G because that's how you do it nowadays) and call it a day. :-)
> Then, you might even tinker with some AI stuff on your own terms, you never know Indeed! I'm not like dead set against them. I just find they're kind of a bad tool for most jobs I've used them for and I'm just so goddamn tired of hearing about how revolutionary this kinda-bad tool is.
I was a huge AI skeptic but since Jan 2025, I have been watching AI take my job away from me, so I adapted and am using AI now to accelerate my productivity. I'm in my 50s and have been programming for 30 years so I've seen both sides and there is nothing that is going to stop it.
Re: AI-First Company Memos
#73I work for a large tech company, and our CTO has just released a memo with a new rubric for SDEs that includes "AI Fluency". We also have a dashboard with AI Adoption per developer, that is being used to surveil the teams lagging on the topic. All very depressing. A friend of mine is an engineer of a large pre-IPO startup, and their VP of AI just demanded every single employee needs to create an agent using Claude. T…
This is absolutely the norm across corporate America right now. Chief AI Czars enforcing AI usage metrics with mandatory AI training for anyone that isn't complying. People with roles nowhere near software/tech/data are being asked about their AI usage in their self-assessment/annual review process, etc. It's deeply fascinating psychologically and I'm not sure where this ends. I've never seen any tech theme pushed to…
Re: AI-First Company Memos
#74Earlier quoted context omitted.
4. They heard from their golf buddy who heard from his racquetball buddy that this other CTO at this other shop is saving lots of money with AI
I know you're speaking half in jest but the C-suite of my area actually used a tweet by an OpenAI executive as the agenda for an AI brainstorm meeting.
Re: AI-First Company Memos
#75Earlier quoted context omitted.
This feels like a construction company demanding that everyone, from drywaller to admin assistant, go out and buy a drill.
Some companies swear by this. CP Rail is notorious for training everyone to drive a train.
Re: AI-First Company Memos
#76Whatever happened to "show, don't tell"? Other productivity boosters certainly didn't need such memos; they were naturally adopted because the benefits were unambiguous. There were no "IDE-first company memos" or "software framework-first company memos"; devs organically picked these up because the productivity gains were immediately self-evident.
All the tools that improved productivity for software devs (Docker, K8S/ECS/autoscaling, Telemetry providers) took very long for management to realize they bring value, and in some places with a lot of resistance. Some places where I worked, asking for an IntelliJ license would make your manager look at you like you were asking "hey can I bang your wife?".
Re: AI-First Company Memos
#77Earlier quoted context omitted.
> Then, you might even tinker with some AI stuff on your own terms, you never know Indeed! I'm not like dead set against them. I just find they're kind of a bad tool for most jobs I've used them for and I'm just so goddamn tired of hearing about how revolutionary this kinda-bad tool is.
If you're finding their a bad tool for most jobs you're using them for, you're probably being closed minded and using it wrong. The trick with AI these days is to ask it to do something that you think is impossible and it will usually do a pretty decent job at it, or at least close enough for you to pick up or to guide it further. I was a huge AI skeptic but since Jan 2025, I have been watching AI take my job away fr…
Re: AI-First Company Memos
#78Earlier quoted context omitted.
I try these things a couple times a month. They're always underwhelming. Earlier this week I had the thing work tells me to use (claude code sonnet 4? something like that) generate some unit tests for a new function I wrote. I had a number of objections about the utility of the test cases it chose to write, but the largest problem was that it assigned the expected value to a test case struct field and then... didn't…
Try Opus?
Re: AI-First Company Memos
#79I work for a large tech company, and our CTO has just released a memo with a new rubric for SDEs that includes "AI Fluency". We also have a dashboard with AI Adoption per developer, that is being used to surveil the teams lagging on the topic. All very depressing. A friend of mine is an engineer of a large pre-IPO startup, and their VP of AI just demanded every single employee needs to create an agent using Claude. T…
I mean get onboard or fall behind, that's the situation we're all in. It can also be exciting. If you think it's still just slop and errors when managed by experienced devs, you're already behind.
I am aware of a large company that everyone in the US has heard of, planning on laying off 30% of their devs shortly because they expect a 30% improvement in "productivity" from the remaining dev team.
Exciting indeed. Imagine all the divorces that will fall out of this! Hopefully the kids will be ok, daddy just had an accident, he won't be coming home.
If you think anything that is happening with the amount of money and bullshit enveloping this LLM disaster, you should put the keyboard down for a while.
Re: AI-First Company Memos
#80Earlier quoted context omitted.
People will voluntarily adopt modest productivity boosters that don't threaten their job security. They will rebel against extraordinary productivity boosters that may make some of their skills obsolete or threaten their career.
That’s simply not true. Developers hand-writing assembly readily adopted compilers, accountants readily adopted spreadsheets, and farmers readily adopted tractors and powered mills.