Earlier quoted context omitted.
CEOs want productivity. They don't want employees. Employees are a cost center.
Employees also make for customers. Not sure how AIs and robots will be replacing human consumers once CEOs realize their dream.
AI-First Company Memos
171–180 of 216 posts
Re: AI-First Company Memos
#172Earlier quoted context omitted.
Reminds me of those little gadgets, which move your mouse, so that you show up online on Slack. I’d just add a cron job to burn some tokens.
That sounds like a lot of work - maybe you could burn some tokens asking AI to write a cron to burn some tokens for you?
Sounds like a lot more work tbh.
Re: AI-First Company Memos
#173Earlier quoted context omitted.
Why have you never even _tried_ it? It’s very easy to try and surely you are somewhat curious.
I've never had to try lots of things in order to know that I won't like them.
In my heart I’m a code “artist,” and like all artists that have been more directly attacked, I also feel personally attacked by all of my stolen “art” that is now monetized by big corporations that do not give a single f*ck about beauty in the code, or whatever.
This may be a strange position, idk. Anyways, that’s the reason why.
Re: AI-First Company Memos
#174Earlier quoted context omitted.
Twice now in this same story, different subthreads, I've seen AI dullards declaring that you, specifically, are holding it wrong. It's delightful, really.
I don't really care if other people want to be on or off the AI train (no hate to the gp poster), but if you are on the train and you read the above comment, it's hard not to think that this person might be holding it wrong. Using sonnet 4 or even just not knowing which model they are using is a sign of someone not really taking this tech all that seriously. More or less anyone who is seriously trying to adopt this t…
If "learn to hold it not wrong" is your message, then the AI bubble will be popping very soon.
Re: AI-First Company Memos
#175People have always resisted change especially one that modifies the way they work. They’d rather work on the same thing for life. To get them to adopt new tools you need to do this stuff. And yes, people did resist IDEs (“I’m best with my eMacs” - no you weren’t), people resisted the “sufficiently smart compiler”, and so on. What happened was that they were replaced by the sheer growth in the industry providing new p…
Re: AI-First Company Memos
#176Earlier quoted context omitted.
Unfortunately at this scale, when you are this soft on the message, everyone ignores it and keeps doing what they were doing before. Carrot and stick are both required for performance management at this scale. You can argue whether the bet is worth it or not, but to even take the bet, you need a lot more than some resources and a "please".
If performance was the true goal then we'd just naturally see slow adopters unperform and phase out of that company. If you make good tooling available and it is significantly impactful the results will be extremely obvious - and, just speaking from a point of view of psychology, if the person next to you is able to do their job in half the time because they experimented with new tooling _and sees some personal benef…
Re: AI-First Company Memos
#177Earlier quoted context omitted.
Why have you never even _tried_ it? It’s very easy to try and surely you are somewhat curious.
I've never had to try lots of things in order to know that I won't like them.
Re: AI-First Company Memos
#178Whatever 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.
Tech loves making something a top priority (and forgetting about it several years later); AI is the first one that is applicable to the masses.
.. Well maybe not User-first. But that was even less clear than AI-first.
Re: AI-First Company Memos
#179I 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 just another business fad, but because the execs want to seem to be cool and seem to be doing what their "peers" claim to be doing, well, then by gosh, all of the workers have to do the same fad.
Re: AI-First Company Memos
#180People have always resisted change especially one that modifies the way they work. They’d rather work on the same thing for life. To get them to adopt new tools you need to do this stuff. And yes, people did resist IDEs (“I’m best with my eMacs” - no you weren’t), people resisted the “sufficiently smart compiler”, and so on. What happened was that they were replaced by the sheer growth in the industry providing new p…
It's Emacs. Also Emacs is an IDE.