Most software engineers are facing an identity crisis bordering on depression.
As CTOs aggressively evangelize tokenmaxxing, a class divide ensues.
The lazy. The lazy push code. They don't write it. They don't manually test it. They don't even read it. They're on autopilot. See Jira ticket, prompt for task, submit code. Many of them are barely on their computer the whole day. A comment on the PR asking why they did this? The lazy ask AI. A Slack message? The lazy ask AI. Need to prepare for standup? The lazy ask AI. As long as it sounds enough like them and isn't detected. Some of the lazy are even overemployed, and work multiple jobs. The lazy smart ones get away with this, and even rewarded. After all, software engineering for the lazy is just a dance to convince your colleagues you're smart and hard working.
The craftsmen. The craftsmen are tired. Very tired. 15 PRs in queue. Slack blowing up. The entire burden of review falls on the craftsman. The burden of understanding. They try. They work their way through the code, thoughtfully commenting to improve what ships. The response? A lazy: "That's a clever idea! You're absolutely right." with an incorrect change. It's fine, the craftsman says. I can fix them. They write a doc urging his colleagues to be better. The next day? 20,000 line PR to review. Day after day, their workload grows. Bugs seep into production. No one seems to care. Another round of AI is thrown at it. Their animosity to their colleagues rises. Eventually, they give up. It's just not what it used to be. The craft they loved is dead. They eventually wake up, a lazy.
This isn't all companies. Many companies are genuinely more productive, adopt the right set of principles and practices around AI development and have highly talented teams that trust each other. It tends to happen in bigger companies that are 10+yrs old with a higher talent variance. But it happens. A lot.
Cloudflare has acquired Vite / VoidZero
Void is vite's fullstack Intertia-like framework.
This gives Cloudflare control over the entire stack. They have all the primitives from frontend/backend framework, linting, testing, formatting, JS runtime, db, kv, inference, blob storage, access, etc...
smart move. A tidy package they can hand to an LLM to make a site.
okay folks, new module out of the oven 🍞
kyo-ui 🧩
write a UI once, run it on the client or the server:
▸ Swap the runner: the same UI mounts in the browser on Scala.js, streams from a server over SSE, or renders to static HTML for SSR and tests.
▸ Reactivity without the machinery: a Signal is a plain value you pass wherever the API takes one, with no wrapper type, binding operator, or hooks.
▸ Type-safe down to the markup: containers accept only valid children, attributes are enums instead of strings, and setters exist only where they apply.
▸ Surgical updates: no virtual DOM and no re-rendering, only the nodes a changed signal touches get patched.
JVM, JS, and Native. Of course 😎
No one could have known that telling programmers "spend as much money as possible on this new agent technology; whoever spends the most money wins!" would result in companies spending too much money on this new technology.
More developers should learn about property-based and model-based testing
Unit, integration, E2E tests are fine for "this should work" but are usually not good enough to test "this should never happen"
Has anyone coined a term for filling up Jira description with AI Slop ?!
AI is really good to populate plausible wall of text which is mostly overlooked during planning but the struggle begins during implementation.
#VibeCoding#VibeProducting
2004 was a good year, but your Gmail address doesn't need to be stuck in it.
To say goodbye to [email protected] or [email protected] (or whatever you were into at the time), go to your Google Account settings and choose any name available. You'll keep your old username and you can sign in with both.
‼️Do not npm install or deploy anything right now
Supply chain attack on axios 1.14.1 - even if you don’t use axios it may be a nested dep.
Pin versions or wait until this is resolved