🎤 Just gave my first public keynote at #DevDaysEurope: "Readable Code: The Secret to Clean, Productive Software"!
Covered what readability really means, why it matters, metrics, AI’s impact, and practical ways to improve codebases.
Watch here: https://www.youtube.com/watch?v=lQBYQvyGPLE
#ReadableCode #SoftwareEngineering #DeveloperExperience
Why @Annotations Will Eventually Burn You.
Preach annotation voodoo or embrace explicit method calls? Too many still cling to @PreAuthorize, entrusting their fate to framework black magic. But such blind faith is brittle. One innocent Spring Boot update, and suddenly your security vanishes unless you summon an obscure @Enable... incantation.
Prefer the custom preauthorize() method: it’s concrete, predictable, and the compiler screams when something breaks as it should. Just like how constructor injection finally defeated the field-injection cult, it’s time to retire annotation worship elsewhere too.
Consider @JsonProperty("fieldName"): sure, the object mapper might infer names correctly without it, until one day it doesn’t, because the naming strategy changes behind your back. It’s happened. It will happen again. That’s the price of depending on invisible magic. Unreadable, unpredictable, unmaintainable. Same applies to reflection.
Frameworks and their “best practices” are relics of the monolith age. Java has evolved: threads, HTTP services, logging,… all can now be built functionally, fluently, and natively. It’s not Java vs Kotlin or some trendy syntax candy. Languages, especially those that compile, already give you more than enough. The bottleneck isn’t the tool, it’s the one holding it.
#Java #SpringBoot #CleanCode #SoftwareEngineering #CodeQuality #Programming #ModernJava #DeveloperExperience #DevMindset #NoMoreMagic #ReadableCode #ExplicitOverImplicit #SayNoToAnnotations #SeparationOfConcerns #FunctionalProgramming
Code is read more than it is written.
You’ll write it once —
But your team will read it again and again.
✅ Optimize for clarity, not cleverness
✅ Follow consistent coding styles
✅ Use meaningful structure and naming
✅ Write with the reader in mind
Readable code saves hours.
Confusing code costs days.
———
♻ Share to help others level up their software engineering career.
➕ Join My WhatsApp Channel: https://lnkd.in/g62_G8Gr
———
Jeremy Clark presents 'Code is for Humans' July 24th at Nebraska.Code().
https://nebraskacode.amegala.com/
#Pluralsight #QuestSoftware #code #ReadableCode #devconf #practicaltechniques #clevercode #techconference #Nebraska #NebraskaTechCollaborative #GreaterDesMoinesPartnership #computerscience #computercoding #coding #programming
Code readability is important because it improves maintainability, promotes collaboration, reduces errors, and leads to robust, long-lasting codebases. Well-written code should strive to be self-explanatory through clear naming, structure, and idiomatic practices, with comments used sparingly to increase understanding (i.e. adding context that is not immediately obvious from the code itself), rather than to compensate for poor design.
I equate readability of code with beautiful code which can be efficient or optimized or both.
#BeautifulCode #ReadableCode #Programming #Code #Haskell #Python
Code is communication — not just instructions.
You’re not just writing for machines.
You’re writing for the next developer.
(Maybe future you.)
✅ Use clear, meaningful names
✅ Write small, focused functions
✅ Leave helpful comments when needed
✅ Make the intent obvious
Readable code saves time.
Maintainable code saves teams.
♻ Repost to help others level up their engineering career.
➕ Join My WhatsApp Channel: https://lnkd.in/g62_G8Gr
"Programs must be written for people to read, and only incidentally for machines to execute." – Harold Abelson
#ReadableCode #ProgrammingWisdom
Actually sidestepping the "comments bad" debate, if you can't read your code two weeks later, you have bigger problems. #readablecode
QT: https://social.cybre.town/@DeveloperMemes/107190603989169170
https://qiitadon.com/web/statuses/103518840698550311
https://qiitadon.com/web/statuses/103518844041756160
Kindle No.774/6035
Encoding Other Important Attributes
> For this, you might want to use variable names like untrustedUrl or unsafeMessageBody. After calling functions that cleanse the unsafe input, the resulting variables might be trustedUrl or safeMessageBody.
近い?
HACK: Admittedly inelegant solution to a problem
// HACK: よりパフォーマンスが良い実装
comment > FIXME: / HACK: > FIXMEの実例
https://qiita.com/7of9/items/c7920e8b1539f01b4b84
@ The Art of Readable Code
No. 1756 / 6036
日本語の本では
p61
