First I felt cheated. Then I realized that something else was more important here. I missed it. And @unclebobmartin has always stood for this: Invest time in tests. Not only unit, but all kinds of tests. And in monitoring.
And still, at this point in history, read the code ;).
I was raised on Uncle Bob's words that our code can affect someone's life and that our responsibility is to keep it to the highest standards. Now Bob says the tests are sufficient to prove the code quality. Yeah, but meh. I use agents to write code. I still read the code.
I was raised on Uncle Bob's words that our code can affect someone's life and that our responsibility is to keep it to the highest standards. Now Bob says the tests are sufficient to prove the code quality. Yeah, but meh. I use agents to write code. I still read the code.
I’m significantly older than you. I started coding in the late 60s. My current strategy is to not read any of the code written by my agents. That’s the only way I can take advantage of their productivity. What I do instead is to surround the agents with extreme constraints. Unit tests, gherkin tests, QA procedures, quality metrics, mutation testing, test coverage, and a plethora of others. In the end, I have very high confidence in the code they produce because they’ve had to run the gauntlet of all of my constraints and tests.
@cursor_ai looks really good after the latest update. The Agent-UI finally feels more structured; The agents are taking center stage, while the editor still remains code-oriented with a really nice diff view. I was skeptical at first, but it does the job. Nice!
Beginning July 20, Claude Fable 5 will be included in all Max and Team Premium plans, at 50% of limits.
Pro and Team Standard users will continue to have access to Fable via usage credits, and will receive a one-time $100 credit.
Demand for Fable has been challenging to predict, which is why we rolled it out to subscription plans in stages, extending access several times as we secured additional capacity.
‼️ BREAKING: AWS users are in shock as the company shows them wildly inflated cost estimates running into billions of dollars per account. AWS has confirmed a global billing console bug as the cause.
In some reported cases the estimates run as high as $1 trillion.
AWS blames a unit pricing error in its estimation subsystem and stresses that the phantom numbers do not reflect actual usage or charges.
Absolutely beautiful rant about AI in Linux Kernel from Linus yesterday:
I realize that some people really dislike AI, but this is an area
where I'm willing to absolutely put my foot down as the top-level
maintainer.
Linux is not one of those anti-AI projects, and if somebody has issues
with that, they can do the open-source thing and fork it.
Or just walk away.
AI is a tool, just like other tools we use. And it's clearly a useful one.
It may not have been that "clearly" even just a year ago, but it's no
longer in question today.
There are other questions around AI (like what the economy of it will
actually look like in the end), but "is it useful" is no longer one of
those questions. Anybody who doubts that clearly hasn't actually used
it.
Yes, it can also be a somewhat painful tool, both for maintainer
workloads and just from a "it keeps finding embarrassing bugs"
standpoint.
But the solution is not to put your head in the sand and sing "La La
La, I can't hear you" at the top of your voice like some people seem
to do.
The solution is to make sure those LLM tools _help_ maintainers
instead of just causing them pain. There's no question on that side.
We're not forcing anybody to use it, but I will very loudly ignore
people who try to argue against other people from using it.
And no, AI isn't perfect. But Christ, anybody who points to the
problems at AI had better be looking in the mirror and pointing at
themselves at the same time.
Because it's not like natural intelligence is always all that great either.
The kernel project has been and will continue to be about the technology.
Sure, the social angle of working on open source is important and
often a very motivating part of the project, but in the end that's a
side benefit, not the _point_ of the project.
This is *NOT* some kind of "social warrior" project, never has been,
and never will be.
In the kernel community we do open source because it results in better
technology, not because of religious reasons.
And so we make decisions primarily based on technical merit. Not fear
of new tools.
Linus
@ceeoreo_ Walter Isaacson's The Innovators is a great read. I also like UNIX: A History and a Memoir.
IMO, gaming is also an important part of the history of computing, so these are worth checking: Sid Meier's Memoir!; Masters of Doom; and Blood, Sweat and Pixels
Happy reading! :)
Ownership, domain knowledge and standing by our own decisions. This is the new SWE. But is it that different from what we did until today? The layer changed, but the job remains the same.
Great speech by @tom_enden here: https://t.co/TGTwO6Jd7u
If AI can write the code, where do engineers create ✨ value?
That's the question @tom_enden tackles in this thought-provoking talk.
He explores how the role is evolving, which skills are becoming more important, and what may separate the engineers who thrive in the AI era from those who struggle to adapt.
Along the way, Tom connects ideas from influential voices such as @unclebobmartin, @karpathy, @paulg, @abeanstalker, and others to explore what engineering may look like in a world where AI writes the code.
If you're trying to understand where software engineering is headed - this talk is worth watching:
If AI can write the code, where do engineers create ✨ value?
That's the question @tom_enden tackles in this thought-provoking talk.
He explores how the role is evolving, which skills are becoming more important, and what may separate the engineers who thrive in the AI era from those who struggle to adapt.
Along the way, Tom connects ideas from influential voices such as @unclebobmartin, @karpathy, @paulg, @abeanstalker, and others to explore what engineering may look like in a world where AI writes the code.
If you're trying to understand where software engineering is headed - this talk is worth watching:
@mattpocockuk i've already checked 5ire and HyperChat, because I wanted to work with open models (in my case it was incept5/llama3.1-claude:latest); both were fine; I found them on the mcp awesome list: https://t.co/ZA3mg29liY
Dzisiaj skorzystamy z wiedzy o symbolach i przeanalizujemy operator `using`, który od niedawna gości w specyfikacji TypeScript.
Jak się okazuje (szok!), przydaje się on nie tylko do reactowych heheszków z `useUsing()` 😉.
Zapraszam do piątkowej lektury! Link w wątku. :)