davefarley77.bsky.social
Software Engineer, Consultant & Author.
The Modern Software Engineering Channel: https://www.youtube.com/@ModernSoftwareEngineeringYT
Support Me On Patreon: https://bit.ly/ContinuousDeliveryPatreon
165 posts
2,288 followers
23 following
Prolific Poster
Conversation Starter
comment in response to
post
😂
comment in response to
post
Subscribe & hit the notification bell so you don't miss an upload ➡️ youtube.com/@ModernSoftw...
comment in response to
post
If you want to learn more about the fundamentals, there's a free course on my online training site. Find out more and get your free course here ➡️ courses.cd.training/courses/cd-f...
comment in response to
post
😂
comment in response to
post
Go for it! I recommend you define the DSL test by test, create only enough to make your first test work, then add more. Don’t think too far ahead. I have a playlist on Acceptance testing with several videos that show examples of my DSLs on my YT channel 😎
comment in response to
post
Most devs write tests that are brittle, misunderstood, or added too late.
ATDD fixes that by turning user stories into clear, executable specs.
Included in the course:
• Write better tests
• Design better systems
• Communicate better with your team
comment in response to
post
Subscribe to the Modern Software Engineering channel!
youtube.com/@ModernSoftw...
comment in response to
post
that’s important for all software. All good software evolves over time to better adapt to its usage in the real world. My team “play-tested” a Finacial exchange we built every Friday afternoon for 6 months before we released it.
comment in response to
post
That’s true of all software, not just games. SW dev is an exercise in continuous learning.
comment in response to
post
All of these groupings are “roles” so depend on the skills, experience and mindset of the individual, but also the company, team and project context. I don’t think you ever get better results from coders than engineers, so it is a poor choice, but it is, sadly, a common organisational mistake
comment in response to
post
Sure, favouring testability forces you in this direction, to make your code more deterministic and so more testable. This has always been a definite positive in the systems that I have worked on, resulting in MUCH higher quality designs and systems. So faking RNG is a small price to pay
comment in response to
post
If you can't tell if your software is releasable after every small change that you make to it, at least once per day, then I don't think you count as a "software engineer".
These are rather niche opinions, but they are what I think.
3/3
comment in response to
post
If you have ever said 'It's not my fault, <someone else> didn't get the requirements right' Then you are a "coder" not a "software developer"
2/3
comment in response to
post
I think that there are a very small number of "engineers" vs "coders", fewer "software developers" than "coders", and fewer "engineers" than software developers"
1/3
comment in response to
post
The UI needs a different kind of testing. I treat visually rich UIs as a rendering problem, now you can test the rendering with controlled, repeatable tests and you can test the logic independently of the rendering. It is more difficult than some kinds of code, but it still works!
2/2
comment in response to
post
I think that you may be making the mistake of thinking of TDD as testing rather than as designing. If it is more about designing, then it is how you go about design, more than the type of programs you write. The challenge with testing games is the ui, the rest is no different to any other code.
1/2
comment in response to
post
If you're curious about how ATDD fits into an AI-assisted workflow, we’ve just added a new lesson to the Mastering ATDD & BDD course — focused entirely on ATDD + AI.
Practical, structured, and ready to apply. Check it out here ➡️ courses.cd.training/courses/atdd...