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.
🧼 Got legacy code? Refactor it safely with Approval Tests!
Join Jan Van Ryswyck’s hands-on workshop at #DevOpsDaysAMS.
Multi-language support & real-world practice.
🎟️ https://tickets.devopsdays.org/devopsdays-amsterdam/2025/
#LegacyCode #Refactoring #speakers
#Development #Guides
The prompt engineering playbook · How to make AI coding assistants more reliable https://ilo.im/164791
_____
#Programming #Coding #Debugging #Refactoring #Prompts #AI #AiAssistant #WebDev #Frontend #Backend
DRY Don't Repeat Yourself Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.
— Dave Thomas, Andy Hunt
I really liked watching this talk: "Code Mending in the AI age - Ray Myers | Craft Conference 2024"
Last month, GitClear published an analysis of 211 million lines of code in its AI Copilot Code Quality report. One of the key findings is that #refactoring signals are crashing while #code duplication and churn is increasing.
https://thenewstack.io/whats-missing-with-ai-generated-code-refactoring/
🚀 Wow, who knew that #coding while chugging Red Bull and vibing to Spotify could be so groundbreaking? 🎶 But surprise, surprise—turns out the real magic trick is "vibe #refactoring," AKA fixing your 💩 code so you can actually get paid. 💸 Apparently, the real "jazz" happens in the #cleanup crew. 🧹
https://dawidmakowski.com/en/2025/04/vibe-coding-is-fun-but-vibe-refactoring-pays-the-bills/ #vibes #vibe #creativity #HackerNews #ngated
Why I’m Not Ready to Abandon JavaScript for “Faster” Languages, by (not found on Mastodon or Bluesky):
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.)
Medior PHP https://leanpub.com/b/mediorphp by Joseph Kanyo is the featured bundle of ebooks 📚 on the Leanpub homepage! https://leanpub.com #Php #Databases #Mysql #ComputerProgramming #Laravel #Symfony #Html #Refactoring #Apis #ApiDesign #books #ebooks
What is refactoring, why is it important and how can you get really good at it? In this Making Tech Better podcast episode, I spoke to @emilybache about enhancing the skills and culture of your teams, to make your code easier to understand and cheaper to modify.
You can listen here (subtitles on screen): https://youtu.be/ZcEz8cA017M?si=tYhdCbp851oiyLSz
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.