The question that matters isn't where to use AI.
It's how work should function now that AI exists.
That changes everything, how you evaluate performance, map skills, allocate people, design roles.
This is what I think about every single day building Kipon
Last week someone told me their biggest challenge was getting AI adoption right across teams.
They'd installed Copilot. Tested ChatGPT. Put it in the board deck.
Still running annual reviews. Same learning system. Same org structure from 2019.
The problem isn't whether to adopt AI.
It's that no one has rethought what work means now that AI exists. If AI changes what a dev ships in a sprint, the baseline for good changed. If AI can do 70% of a process the team running that process needs to change.
Ghostty 1.3 is now out! Scrollback search, native scrollbars, click-to-move cursor, rich clipboard copy, AppleScript, split drag/drop, Unicode 17 and international text improvements, massive performance improvements, and hundreds more changes. https://t.co/IMk3i6528t
@JulienBek Looking at the chart, I would add another axis to this conversation, which would be โphysicalities.โ Physicality is still on the human side, for now and there is no theoretical AI coverage, we still need advances in robotics for that to happen.
Weโve identified industrial-scale distillation attacks on our models by DeepSeek, Moonshot AI, and MiniMax.
These labs created over 24,000 fraudulent accounts and generated over 16 million exchanges with Claude, extracting its capabilities to train and improve their own models.
At Stripe we have a tool called "minions" -- it lets us kick off async agents built right in our dev environment to one-shot bugs, features, and more e2e.
I have team, project, and personal channels dedicated just to working with minions.
I like to think of it as a new type of pair programming -- "pair prompting."
Read more --> https://t.co/0A6vDEOEjL
@gokulr@OpenAI I would say it can be a good move to connect with various systems of record to deal with the legacy, but I would say itโs not the most efficient path. The shift to graphs has to be from the ground up, because the relationship of generated data is at completely higher levels.