Favour composition over inheritance. Instead of deep class hierarchies, build objects by combining smaller, focused components. Easier to test, modify, and reason about. #DesignPatterns #CleanCode
Favour composition over inheritance. Instead of deep class hierarchies, build objects by combining smaller, focused components. Easier to test, modify, and reason about. #DesignPatterns #CleanCode
A code review full of sarcasm and vague critiques is like giving someone a broken compass and saying “you’ll figure it out.”
Clarity > cleverness.
If you want better code, offer better feedback. Precision, kindness, and context go further than snark ever will.
New Release: API-Doc-Crafter just got sharper. Cleaner. Meaner.
Giving my little OpenAPI merging monster some upgrades.
It all started with a simple idea: merge OpenAPI specs from multiple repos.
Now? It transforms outdated Swagger specs to OpenAPI 3+, generates HTML pages with full navigation, and allows customization via config or env.
SecurityRequirement deduplication - because why merge APIs if you can't also merge logic?
Custom metadata enrichment - inject your info, license, contact, and docs straight from config. No more excuses.
Better parser fallback - now tries more ways to read broken specs than your average intern in panic mode.
Variable substitution in outputs - ${variables} be gone. Use env or config, stay DRY, stay sane.
Tests expanded. HTML, JSON, YAML outputs covered like a nuclear bunker.
Powered by GraalVM, no reflection, blazing fast.
Native Docker builds.
Reflection config surgically trimmed. Less bloat. More edge.
Project: https://github.com/YunaBraska/api-doc-crafter
Happy crafting. And remember: if your docs aren't automated, they're probably lies.
Sometimes you need to clean up your code and turn repetitive tasks into helper functions. Watch our quick tip to learn how to create a simple plugin for your helpers. #cleancode https://www.youtube.com/watch?v=PajT4qyE55c
I have found the most annoying type of source code comment: Questions. Like this:
// What does this code do? Does it even work?
if (someCondition) {
do_stuff();
}
Hey, don't ask me pal, I am just trying to find that out myself...
And I am really starting to think that the "The code is the documentation" people might have a point. That is honestly worrying...
Oh right, my survey on the book "Clean Code" ended. Seven people have participated, six haven't read the book. This is far from being representative but I urge every dev who hasn't read this book to give it a shot. We are drowning in badly made software and one reason is because devs do not care enough about code quality. It's high time we do something about that and if we are honest about it we need to start with our own habits and practices because they produce bad code.
Time to blow off some steam! What practice has caused you most headaches? Abuse of a theoretically sound idea also counts.
What best practices do you believe are sine qua non?
Of those which are espoused at your work place?
Which do you espouse on your hobby projects?
Me:
1. #tdd, #refactoring, #cleancode, #solid(ish), #agile
2. #agile(ish), #ddd (starting), #cleancode
3. #tdd, #refactoring, #solid(ish), #agile(in the sense of fast iteration)
I am too new in DDD to apply it in 'personal' projects, clean-code, I kinda try
This week I have started on some exciting new plans for coaching and facilitations in the new year. I also got to enjoy some quality coding time. I go into a bit more depth on "Code Scout Rules" on my blog in #WeekNotes #CleanCode #LittleAndOften #blog
http://tessbarnes.uk/blog/code/scout-rules-still-apply/
#Introduction post is in order?
I am a software engineer from Czech republic, so I like to talk about #cleancode, #agile and other things #programming.
And because the best way to learn coding is to make games, I also sometimes do little #gamedev or #pixelart projects.
And currently I am working on a set of handy plugins for pixel art workflow in Gimp!
Moin and Tach, ich bin quasi #neuhier.
Ich komme aus #greifswald, plane #it-Projekte und helfe Wissenschaftler:innen, setzte mich für #datenschutz, #cleanCode, #privacyByDesign und #floss ein und versuche mein Wissen zu streuen. Außerdem #singe ich, mache #musik und #notensatz, nutze #inkscape, #ardour. #linux muss sein, ich respektiere die #hackerEthik, höre #podcasts und #frickel und #löte gern an Dingen rum.
Ich hoffe hier auf regen Austausch und freue mich auf die Community :)