Ted M. Young's Confident Coding Blog

All the code I’m working on in my live coding stream is available at https://github.com/jitterted/jitterticket-event-sourced.

All the code I’m working on in my live coding stream is available at https://github.com/jitterted/jitterticket-event-sourced.

All the code I’m working on in my live coding stream is available at https://github.com/jitterted/jitterticket-event-sourced.

All the code I’m working on in my live coding stream is available at https://github.com/jitterted/jitterticket-event-sourced.

All the code I’m working on in my live coding stream is available at https://github.com/jitterted/jitterticket-event-sourced.

All the code I’m working on in my live coding stream is available at https://github.com/jitterted/jitterticket-event-sourced.

All the code I’m working on in my live coding stream is available at https://github.com/jitterted/jitterticket-event-sourced.

All the code I’m working on in my live coding stream is available at https://github.com/jitterted/jitterticket-event-sourced.

All the code I’m working on in my live coding stream is available at https://github.com/jitterted/jitterticket-event-sourced.

All the code I’m working on in my live coding stream is available at https://github.com/jitterted/jitterticket-event-sourced.

All the code I’m working on in my live coding stream is available at https://github.com/jitterted/jitterticket-event-sourced.

All the code I’m working on in my live coding stream is available at https://github.com/jitterted/jitterticket-event-sourced.

All the code I’m working on in my live coding stream is available at https://github.com/jitterted/jitterticket-event-sourced.

All the code I’m working on in my live coding stream is available at https://github.com/jitterted/jitterticket-event-sourced.

All the code I’m working on in my live coding stream is available at https://github.com/jitterted/jitterticket-event-sourced.

All the code I’m working on in my live coding stream is available at https://github.com/jitterted/jitterticket-event-sourced.

All the code I’m working on in my live coding stream is available at https://github.com/jitterted/jitterticket-event-sourced.

Notes from Today’s Live Coding Session I’m back from vacation and resumed my live coding streams where I’m working on “JitterTicket”, an example Event Sourcing application in the Concert Ticketing domain.

Improving Your Skills Just about every week on my live-coding stream, I get asked “how do I learn Java/Spring Boot/etc.”?

Playing the Game The Video On the Agile Lunch & Learn channel, I gave a talk about “Predictive” Test-Driven Development as an introduction to JitterTed’s TDD Game.

Slide from the Primitive Obsession presentation The Video Recently at the Seattle Software Crafters meetup (remote), I gave a new version of my talk on Primitive Obsession.

Does 'No' sound good to you?

Slide from the presentation The Video Recently at PhillyXP (remote), I gave an updated version of my talk on how Hexagonal Architecture—primarily its separation of concerns—helps make code more testable.

Introduction On my live coding stream, the question often comes up: “what books would you recommend?”

Hexagonal Architecture: The Hexagon Q.

On my Discord, @Oye recently asked about removing a feature from a codebase using Test-Driven Development (TDD).

Why Ensembler is Slow I’ve been trying to figure out how to make Ensembler, my scheduling application for group programming sessions (aka MobReg), more responsive.

Really Squeeze 'Em Specifying, or Over-specifying?

For the GoF Builder, use the KDL language as the “director” and then implementations that can create an HTML document, a PDF, or even JSON.

Welcome to The New TED.DEV If you’ve stopped by here before, you may have noticed that the domain TED.dev no longer redirects to tedmyoung.com, which is my old (and non-responsive, yucky) website.

Implementing the Feature Continuing from last time, we’re now ready to write code!

2023-10-09: Added “Spectator” role information, added Retrospective details 2023-03-27: Added some Driver etiquette around not blocking information, closing unneeded windows, etc. 2022-06-09: This article was originally published on Dev.to, but it’s time…

In Part 2 of my “Predictive Test-Driven Development” series, I talked about how predicting the failure of a test is not always enough.

Way back in March 2021, I started explaining my Predictive Test-Driven Development process.

One of my Twitch viewers was confused about the “Fake” and “In-Memory” Repositories I use, and wanted to know more about them.

As you may know, I code live on Twitch whenever I can.

This article comes from a question asked in my Discord.

2023-02-21: Added the Custom Postfix Templates plugin. 2023-02-02: This article was originally published on Dev.to, but it’s time to bring it here, as well as bring it up to date.

Change Behavior with Predictive TDD In my last post, I talked about the two main activities of Test-Driven Development[1]: Change Behavior: adding capabilities and features to a system, or, perhaps, fixing bugs.

When it comes to Test-Driven Development, we often see it as a cycle consisting of three parts: RED, GREEN, and REFACTOR.

I was recently reminded (thanks to Jon Reid @qcoding) of a tweet I wrote back in July 2020: When doing #TDD and writing unit tests, I try to write my expectations in the language of the domain (Ubiquitous Language from DDD) instead of primitives and colle…

Back in October 2018, I gave my 3rd iteration of my talk: “Human Learning: How We Learn & Why It Matters” at the Silicon Valley Code Camp.