The Single Responsibility Principle isn't just about classes - apply it to functions, modules, and even variables. Each should have one clear reason to change. Makes debugging and testing much easier. #CleanCode
The Single Responsibility Principle isn't just about classes - apply it to functions, modules, and even variables. Each should have one clear reason to change. Makes debugging and testing much easier. #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.
Was fällt euch auf? Ist das wirklich sinnvoll so?
Diskutiert mal!
Bitte denkt selbst nach und fragt nicht einfach eine KI – eure eigenen Ideen interessieren mich viel mehr!
Migrating to Temma v2?
Here’s what’s new:
Updated method naming
Native dependency injection
Cleaner SQL handling
A solid upgrade for your PHP projects.
Full documentation: https://www.temma.net/en/documentation/migration
Preprocessor directives can do a lot more for your C# projects — especially when you want to conditionally compile code for different environments, platforms, or configurations.
Have you used preprocessor directives in a clever way? Drop your favourite use case below
Test coverage is compound interest.
Every edge case you catch now is one less bug, one less support ticket, one more confident release.
Invest early. The payoff is peace of mind.#SoftwareEngineering #SaaSDev #CleanCode #TestDrivenDevelopment #DevLife #saasini
DDD for PHP, the silent revolution.
Entities > Arrays
Domain services > Spaghetti code
Shared language = fewer bugs
Could business-aligned code be your next power move?
Tightened up our database this week on CityCatalyst project at OEF.
This means stronger validation, fewer orphaned records, and better model alignment across all our services.
Clean schema, clean mind.
It’s the little things that keep big systems stable.
Are you still using new to create dependencies in your C# apps? It’s time to level up your code with Dependency Injection!
Constants or Enums in PHP?
Constants = silent bugs
Enums = strong typing, cleaner code
Your future self will thank you.Full article: https://medium.com/@sfmok/10-benefits-of-using-enums-instead-of-constants-in-php-7fc87465edf3
Write LINQ like a pro:
Chain with intent
Use Where() early
Keep it readable — break long chains
Avoid side effects in selectors
Profile when querying large datasets
Clean LINQ = happy code.
Write tests not because you don’t trust your code — but because you do.
Testing isn’t a chore.
It’s a sign of care and confidence.
Catch bugs before users do
Document expected behavior
Refactor without fear
Build with peace of mind
Good tests make great code sustainable.
——— Share to help others level up their software engineering career.
Join My WhatsApp Channel: https://lnkd.in/g62_G8Gr
———
I was writing yet another JsonConverter<T>... until I discovered how .NET handles polymorphic serialization with just two attributes
Here’s how I ditched boilerplate & made my APIs cleaner with [JsonPolymorphic] + [JsonDerivedType]
https://wp.me/p29SK-ZB
#DotNet #CSharp #SystemTextJson #WebAPI #CleanCode
Tack för feedbacken, alla. Nu finns en ny version på https://test.trainfo.eu med "Länder"-meny
fortfarande en del som skall göras, men att jobba med filer och kunna göra sök-ersätt och se skillnader efter ändring underlättar mycket.
Jag använder även en linter (program som kollar att markdown-strukturen är korrekt) vilket förhoppningsvis gör risken mindre att det blir problem. #cleancode
Även användbarhets-problem uppmärksammas och skall fixas.
I'm reading The Devil Never Sleeps (Kayyem). Juliette introduced me to the Normalization of Deviance, which describes how unacceptable practices gradually become acceptable over time and repetition.
She is talking disasters, but I see real lessons for software development. When I have to refactor, and leave the code 'good enough' I normalize the Deviance of quality that is expected because it is "better than it was before."
I need to write a blog post on this. It's a fascinating way to look at a well understood problem.
What if writing simpler code could help save the planet?
In my latest essay, I explore how the Simplicity-First initiative aligns with Green Software principles, less complexity, less energy, and less carbon.
‘Future-proofing' often leads to unnecessary complexity. Learn how to work confidently with incomplete knowledge in our hands-on workshop on code simplification. Join us for group exercises, discussions, and practical insights that will transform your approach to software design: https://buff.ly/3xrKM6z #CleanCode #SoftwareArchitecture
PrettyBlazor v1.3.0 is out!
You can now write switch cases as Blazor components—clean, separate, and beautiful.
Huge thanks to Mabrouk for making PrettyBlazor even prettier!
PHP vs Go, two backend mindsets
PHP = flexible, fast to build
Go = strict, but blazing fast
Which one fits your next project best?https://medium.com/@emprovedev/go-vs-php-practical-outlook-69b814e0f564
Dear Gradle, Why So Stubborn?
Do I do something wrong?
Watching juniors try to set up a project and being greeted by cryptic stack traces like it's some kind of initiation ritual.
`Unsupported class file major version 61`
`invalid CEN header zip64 no access package`, ...
Java can compile code for older versions just fine.
It's literally designed for that.
Oh why, must Gradle behave like a bitter librarian who refuses to hand over a book unless I whisper the exact Dewey Decimal Code?
Every other Language will laugh again at java, seeing this.
Why is Gradle bound to a java version? And if Gradle knows it needs Java 11… why doesn't it just do this for me?
Like using `/usr/libexec/java_home -v 11` in background?
Is there a clean way to force Gradle into submission without adding another tool like SDKMAN or jabba or YunaBraska/gradle-java-fix or whatever the trendy painkiller of the week is?