schmonz.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
Here's how I started test-driving a SwiftUI counter app… https://qualitycoding.org/tdd-where-do-you-even-begin/ #TDD
Join me in just about half an hour, when I'll be live-coding (note: live, not vibe, coding!) a new feature in my open-source project.
A long-term client contract is ending in September, so I'll have some time in the last three months of the year. I want to spend a lot of it slowing down, learning, experimenting, ... and I'll write about it here.
I also have some capacity for training and technical coaching (Test-Driven Development, Agile Engineering, Domain Driven Design). Contact me to discuss more details if you are interested: DM here or business@davidtanzer.net
#TDD #DDD #agile
In software development, we have many ways to speed up the time until we get good feedback (in this video, I talk about test-driven development or #TDD).
So, if we are in an environment where we get feedback slowly, we are choosing slow feedback - deliberately or by neglect.
Why are so many choosing slow feedback? https://videos.devteams.at/w/x5Hkwz6ey1GeNF5sZRKAcP
If you prefer youtube, watch here: https://youtu.be/NIP13D9cEgc
Video 4 of #TDD with #SwiftUI: Did you know that Xcode behaviors can help change _your_ behaviors as a developer? https://www.youtube.com/watch?v=uEpBDR_f3tc
@jlink that's because "developer productivity" is hard to define and even harder to measure. All in all my key metric is shortening the feedback cycle(s). #TDD does a great deal in that. But you also have to do (real) continuous delivery. Even #AI can help with that (cycle time) when it comes to rapid prototyping and quickly explore an idea or technology.
If you really really want to increase your developers productivity, teach them proper #TDD and give them time to refactor.
so good I wrote #playwright tests yesterday, I knew the complexity was beyond me comprehending the validity of the code.
That's when I start applying tests and #TDD lately.
Why do I start testing so late?
Well I passed the line of the code being for throw away, since I am coming back and actively being interested in it keeping to work.
curious to see the tests? https://codeberg.org/wolframkriesing/spaish/src/branch/main/tests/details.spec.js
for this project: https://picossg.dev/tools/spaish/
#OpenToWork Hi y'all.
I'm now properly looking for a new job, available from early September for a senior software role. Ideally, in #Kotlin or Java-to-Kotlin conversion. I think I can tick just about all the important boxes for backend development and some more. (especially XP, #DevOps, #TDD, trunk-based development, pairing, fast feedback cycles). Ideally, #remote or flexible #HybridWorking in #London (the one in the #UK).
Would it be possible to transfer the test-driven development paradigm over to writing fiction? Test-driven novel writing? I think so!
Here’s my pecha kucha talk on the topic from @Oop Munich: https://youtu.be/s9rPI1lPWfc
Leanpub book LAUNCH 🚀 The Software Developers’ Guidebook: A Collection of Modern Engineering Practices by Dave Farley https://youtu.be/C0OL14tVx2c #books #ebooks #newreleases #booklaunch #programming #softwareengineering #DevOps #Agile #Lean #softwaretesting #TDD
Don't miss out on the technical content at Agile 2025!
Join me in Denver in for my talk, “Test-Driven Development: Exploring the Spaces in Between”. I'll expose the hidden thinking behind the actions.
Get tickets: https://agilealliance.org/agile2025/
#Agile2025 @AgileAlliance
Leanpub book LAUNCH 🚀 The Software Developers’ Guidebook: A Collection of Modern Engineering Practices by Dave Farley https://youtu.be/C0OL14tVx2c #books #ebooks #newreleases #booklaunch #programming #softwareengineering #DevOps #Agile #Lean #softwaretesting #TDD
What is Test Driven Development (TDD) and how can it speed up your software development? In this Making Tech Better podcast episode, I spoke to @GeePawHill about why he loves TDD so much and how he has spread that love to software teams all over the world.
You can listen here: https://www.youtube.com/watch?v=jJauO_q5dq8
Leanpub book LAUNCH 🚀 The Software Developers’ Guidebook: A Collection of Modern Engineering Practices by Dave Farley https://youtu.be/C0OL14tVx2c #books #ebooks #newreleases #booklaunch #programming #softwareengineering #DevOps #Agile #Lean #softwaretesting #TDD
My live-coding #TDD with #SwiftUI will be back next Sunday. Follow me at twitch.tv/qcoding to get the go-live notification.
The last session was so good, I spent time adding chapter timestamps. If you can't join live, subscribe to my YouTube channel for my next video. https://www.youtube.com/watch?v=pAd8AEJIVyw
I find that the issue Kent Beck talks about here:
https://tidyfirst.substack.com/p/why-tdd-doesnt-lead-to-dumb-code
... is very fundamental to TDD and centers around a couple of commonly missed aspects of it (even though they are spelled out in Test Driven Development by Example)
1- When passing the test, there is a Fake It approach you can take if you don't see the Obvious Implementation right away before you move on to Triangulation and add more tests.
2- When you are using Fake It, the Refactoring step is not primarily about making the code "nicer", but generalizing by removing the duplication between the test and the production code. This is only refactoring in the sense that you are staying green. That's why the step is not optional and getting to green using the simplest, naive implementation is a core part of the process.
I think not using Fake It is one of the two main reasons people fail with TDD (the other is not making writing more testable code a design goal.)
_Event-Sourcing Live Coding_
I've been live coding an example #EventSourcing app in #Java (via #TDD) w/o an ES library.
This week I'll continue to code the "Time-Traveling Event Viewer" to view the state at any point in time.
Join me Mon-Thur 18:00 UTC https://jitterted.stream
One danger of a too transparent box used for TDD is that tests get too coupled to a specific implementation and thus hinder refactoring and evolution. ie, taking the soft out of software.
Sure you are aware of that, but novices easily fall into that trap, when they not have learned enough about refactoring towards simpler code.