Wanted James Shore's testing advice but he's fully booked. Built a whole RAG pipeline to query his articles. Then found notebooklm-mcp-cli - load, point Claude at it, done. Zero DIY. github.com/jacob-bd/not...
Audible TDD is a game changer. 🔈
I refactored my Loomium watch script to play sounds:
✨ Glass "ping" = Pass
🐸 Frog croak = Lint error
🎸 Grumbly bass = Test failFeedback in <1s without leaving the editor. No more "checking" the build. I just listen for the win.
Every feature branch starts the same way, so I put it in a script: pull, optional version bump, branch name from story title, spec file scaffold, pnpm checks.
Less decision fatigue. Every branch starts versioned, documented, and verified.
(Why not Java? Unsure.)
I see a lot of advantages : no JS-glue anymore, better performance, open the door for first-class client-side or fullstack #Rust, #Kotlin, #Go, #Swift or #Java support, consistency with upcoming WASI 1.0 on server/desktop side. It can unlock very interesting use cases.
Any reason? I don’t really know what the differences are between any of them or even why they exist, except for graalvm.
Ah, I notice that you're using Java 25 Oracle now instead of temurin?
Did you use an OpenRewrite stuff? What stream was that on?
How do you test AI agents when output is non-deterministic? 🧪
This guide on Embabel agents covers:
* Fast IO-free tests with Fakes
* Real-world LLM integration tests
* Optimizing for speed, cost, & reliability
@poutsma.bsky.social
The main thing it does differently than things like Claude Code is to give you control over exactly what goes into the context, which is good if you know your code base well.
“LLM said it’s right”
Oh, cool! Curious if you’ve tried Brokk?
Just discovered James Shore's incredible work on testing without mocks and it's been a game-changer for my Next.js development.
When I first started working professionally on a Next.js codebase, I brought the TDD practices I'd developed over a couple of year of Java/Spring Boot/Vaadin work. But wit
Console Whisperer v1 is live. A desktop app that lets you set up your mixing console using natural language through Mixing Station. Channel names, colors & routing to main. $37 one-time, BYOK. Works offline with Ollama. consolewhisperer.com
I asked Elis to test Console Whisperer for me so she made everything purple and added animal names.
"Java offers a fully modern, end-to-end alternative — desktop, web, terminal, and even mobile apps — all powered by a single language. With one cohesive Java stack, teams and AI tools can reason, build, and iterate more efficiently than ever." #java #ui robintegg.com/2026/02/08/j...
When I read your articles I think, “hmmm, I like this. I could probably write articles this short if I stopped using LLMs so much.” 😆
Do you write these right after the stream? Or from the interns journal?
I finally finished the Next.js App Router Fundamentals course that I started in Devember and I think the missing certificate image pretty well mirrors my complicated feeling about NextJS as "production-grade tooling". ¯\_(ツ)_/¯
@vaadin.com vaadin.com/docs/latest/ is returning a 503
Hasn’t shown up in my player or in your website yet, far as I can tell.
experienced engineers: one change, test, one change, test
junior engineers: batch everything because they're in a hurry
this is exactly backwards
the person least capable of batching is the one most likely to batch
Fiverr Workspace (formerly And.Co) is officially closing shop. 🫠 I’ve been using them since the early days—it wasn’t perfect, but it did the job. Now that I’m back on the hunt for a new invoicing home, I’m curious what everyone is using these days?
SketchUp + Flex users: stop manually typing equipment lists into Pull Sheets.
Square Wave's new Equipment List Import feature turns your SketchUp CSV into a Flex Pull Sheet in seconds.
Upload → Enter element number → Done.
Build your own sound laser.
Next.js tutorial: "An alternative to client-side validation is server-side validation."
No. Server-side isn't an *alternative*—it's mandatory. Client-side is the optional UX layer.
Anyone can delete `required` in DevTools. Only server-side actually protects your system.
A test should be a complete story you can read from top to bottom without scrolling. By handling test setup directly inside the test method, you eliminate the "yo-yo effect" of jumping around the file to understand the setup.
You aren't stuck with <T>!
Using <DATA> or <RESULT> makes your generics so much more readable.
First I’ve heard of them. Looks helpful.
