Looking forward to it! 🤓
05.03.2026 09:58
👍 1
🔁 0
💬 0
📌 0
Looking forward to it! 🤓
So excited to do some vibe coding in a familiar environment, Java! :D
Regardless of the outcome: There will be something to learn from this. 🤓
If you're still vibe coding in 2026, you're leaving productivity on the table 😉
Watch the full session:
youtube.com/live/vopBYXp...
We also covered:
- Prompt injection risks
- Real guided coding projects
- Research workflows
- Live coding example
This is probably the most practical session I've been to on AI coding.
My favorite section was feedback loops:
- Automated tests
- Linters
- Benchmarks
Instead of guessing if AI code works, you prove it works.
The most practical part was AGENTS.md
A single file that tells AI agents:
-How the project works
-What matters
-Coding rules
-Constraints
It massively reduces hallucinations.
Key idea:
Vibe coding = hoping the AI gets it right
Guided coding = making the AI predictable
The difference is huge.
Guided coding uses:
- Clear plans
- Structured context
- Feedback loops
- Repeatable workflows
Many people are still doing vibe coding.
After a 2+ hour session with Kenny Pflug, I realized there's a better way: guided coding.
Less chaos.
More results.
Better AI collaboration.
Here’s the full session 👇
youtube.com/live/vopBYXp...
If you care about serious Java engineering, AI agents in real workflows, and maintainable code instead of quick hacks, this is for you.
AI and Java folks, join us live and bring your toughest questions.
Kenny will walk me through his Guided Coding framework:
• Plan first
• Constrain the AI
• Review aggressively
• Refactor deliberately
Using GitHub Copilot in Visual Studio Code with a real Java example.
Live session: Guided Coding in Java with Kenny Pflug.
Not vibe coding. Not blind prompting.
We explore a structured way to collaborate with AI while keeping architectural control and code quality high.
youtube.com/live/vopBYXp...
To be honest: Never heard of it ^^
But after reading up on it, it does sound interesting, especially in the java environment. The tools i use usually have a single file, where they try to describe the structure of the codebase, but it seems like @buildwithbrokk.bsky.social does more here.
java.evolved – Every old Java pattern next to its modern replacement, side by side.
javaevolved.github.io
If you care about serious Java workflows, agent based development, and reproducible AI evaluation, this will be interesting.
Join live.
Give hints.
Challenge assumptions.
Or just watch what actually happens.
👉 youtube.com/live/XNtd3hJ...
#Java #SpringBoot #AIAgents #Copilot #Claude #IntelliJIDEA
We will measure:
• Time to working build
• Number of iterations
• What extra context the agent requests
• Whether tests pass
• Code quality and architectural discipline
If the model is identical, will the agents still behave differently?
The task is simple and strict.
Fix the failing tests.
Make the build green.
Make the application behave correctly.
That is it.
Three agents.
@github.com Copilot. @anthropic.com Claude Code. @jetbrains.com Junie.
Same project state.
Same prompt.
Same model: Claude Opus 4.6.
No architectural redesign. No shortcuts. No manual rescue unless clearly stated.
This is a full stack chat application with authentication, persistence, frontend integration, Docker, and failing integration tests.
Existing architecture. Existing tests. Real constraints.
AI coding agents claim they can handle real production Java projects.
Let’s test that. Live.
I am running a controlled comparison inside a real world Java codebase.
Watch here:
👉 youtube.com/live/XNtd3hJ...
So looking forward to this! 😅
Is... is that comic sans? 😧
I will be live coding, no slides, no script.
Testing where AI in @intellijidea.com actually helps and where human judgment still wins.
Join if you are curious and judge for yourself.
youtube.com/live/OAfmalI...
This makes it the most honest place to test AI.
No new workflow to learn. No shiny distractions.
Just my normal Java development with AI added on top.
Now I am doing something that feels like a back to the roots vacation.
IntelliJ.
My long time Java IDE. Familiar. Opinionated. No novelty factor.
I have tried AI in many forms so far.
CLI tools, web UIs, different editors, different models.
Sometimes it helps a lot. Sometimes it gets in the way. Both are worth learning from.
Over the last year I discovered that experimenting with coding assistants is genuinely fun.
Not because they solve everything, but because they change how I explore ideas, refactor code, and think while coding.
AI feels fast, but feelings are not measurements.
Studies claim 20 to 50 percent productivity gains, especially for debugging and issue analysis. Is that real or just perception?
Let’s examine this live today at 20:00 CET
youtube.com/live/SVJC4Du...
AI adoption often stops the moment GDPR enters the conversation.
Local models, client approval, and limited code access make real world usage messy.
I will talk about what actually works and what does not in a live session (with @brunoborges.bsky.social).
#GDPR #DataProtection #Java
Wow...that doesn't sound right. How many hours did that cost you? 🫠
