El secreto para mejorar en #programación es entender la #abstracción. Sin ella, tu #código será un caos. Aprende a pensar como un #programador de verdad.
Si te interesa la programación, #Linux y la #tecnología, ¡sígueme para más contenido! 
#coding #desarrollosoftware #devlife #python #javascript #software #cleancode #informática #tech #dev
Ayer aprendí algo importante en #cleancode. Los tests deberían seguir las siguientes reglas:
F.I.R.S.T.
F: Fast (Que corran rápido)
I: Independent (Que sean independientes)
R: Repeatable (Deben correr en cualquier entorno)
S: Self-Validating (Salida Booleana, pasa o falla, nada más)
T: Timely (Escribirlos antes que el código de produccion)
Si ya programas hace un rato probablemente te habías dado cuenta de esto ;)
New post:
Sprouting or wrapping?
https://codesai.com/posts/2025/03/sprouting-or-wrapping
"Every great app starts with great code."
Natalie Samhan will lead a session titled "Streamlining Quality Checks by Leveraging Custom Lint Rules" at #FlutteristasConf2025. She will explore how Flutter and Dart developers can use the custom lint package for a straightforward setup or the analyzer package for more advanced customization.
Learn how custom lint rules can help you build cleaner, more maintainable projects. 
RSVP: 
flutteristas.org
I wrote a new post in @codesai blog:
The class is not the unit in the London school style of TDD
https://codesai.com/posts/2025/03/mockist-tdd-unit-not-the-class
Republishing an old Codesai's post on Dev community:
On code smells catalogues and taxonomies
https://dev.to/trikitrok/on-code-smells-catalogues-and-taxonomies-3ba6
Stop bugs before they happen! Pre-Commit automates code checks, ensuring quality and consistency before every commit. Upgrade your workflow today!
Stop bugs before they happen! Pre-Commit automates code checks, ensuring quality and consistency before every commit. Upgrade your workflow today!
So I just learned about _cohesion_ in classes. Never heard of it, but it changes the way I think about OOP completely. I am now playing with the Python `cohesion` tool.
Taming Tech Debt: The Psychological Benefits of a Clean Codebase
As software developers, we often overlook the clutter that accumulates in our codebases, much like the mess on our desks. Daniel Janus explores how dedicating time to clean up tech debt can not only e...
https://news.lavx.hu/article/taming-tech-debt-the-psychological-benefits-of-a-clean-codebase
I am still mystified why #CleanCode became popular despite having terrible advice for #programming production-quality software. 
#APhilosophyOfSoftwareDesign aligns much more closely with the hard-won lessons I have gained over the years. 
John Ousterhout (“A Philosophy Of Software Design”) & Robert ‘Uncle Bob’ Martin (“Clean Code”) debate 
:
https://github.com/johnousterhout/aposd-vs-clean-code/blob/main/README.md
On HN: https://news.ycombinator.com/item?id=43166362
On Lobsters: https://lobste.rs/s/xcqfp7/philosophy_software_design_vs_clean_code
Why I Read Code, Not Just Docs.
Many ask what books I read to know so much. Truth? I read a lot.
The Key is to read Iterative on usage:
I read & test language updates to stay ahead. I read JavaDocs from methods to understand my tools. I dive into source code to see reality.
Marketing slides, old books, outdated websites, foreign benchmarks, YouTube videos, consultants, or sales pitches, code doesn't tell you everything.
That's how I spot:
Frameworks abusing ThreadLocals, reflection, synchronised. "GraalVM-ready" still needing class loading & build on runtime. Cloud SDK packed with 300+ dependencies. Memory leaks, vulnerabilities & hidden bloat.
[...]
AI won't save us, it'll just continue the trend.
‘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/4houjvO #CleanCode #SoftwareArchitecture
When your code is a few KB, but your dependencies rival AAA game installations. Still believe in fairy tales of secure code?
Gigabytes of code you didn't write. Licences you didn't read. Security flaws you didn't anticipate. Yet, you trust them. Adorable.
Not just Node.js. Gradle caches, AWS libs with 400 sub-dependencies + reflection parties. In control? How cute.
I use plain Java with jlink + jpackage. Minimal. Secure. No bloat.
Fewer deps = fewer surprises. Because I care.
But hey, keep stacking that Jenga tower. Watching it fall will be fun.
Ah, the age-old battle between "Clean Code" and "A #Philosophy of Software Design." 
Apparently, scribbling README files on #GitHub counts as a philosophical debate now. 
Who would've thought that toggling navigation menus and playing with #Copilot could lead to such profound enlightenment? 
https://github.com/johnousterhout/aposd-vs-clean-code/blob/main/README.md #CleanCode #SoftwareDesign #HackerNews #ngated
Clean Code vs. A Philosophy Of Software Design — https://github.com/johnousterhout/aposd-vs-clean-code/blob/main/README.md
#HackerNews #CleanCode #SoftwareDesign #Philosophy #Programming #BestPractices #TechTalks
У світі, де AI вже пише код та п'є каву з розробниками, базові принципи SOLID все ще залишаються загадкою для багатьох 
Щойно опублікував детальний гайд про SOLID принципи з практичними прикладами на C#
#programming #developers #dotnet #csharp #solidprinciples #softwareengineering #codinglife #cleancode #solid
Resilience. Reliability. Reusability.
Always wrong investments…
If you think bugs, tech debt & maintenance are “normal,” do the world a favor: resign. You’re part of the problem.
MVP/PoC ≠ Done.
It’s a candle - fragile, short-lived.
Real engineering = the light bulb: robust, lasting.
But devs & managers stop at "it works."
Why? Because real engineering demands more.
More thinking. More iterations. More uncomfortable truths.
Fragile systems = endless maintenance. Seniors wasted on babysitting. Knowledge stagnates.
Product & Tech - Two worlds, but only one is visible.
Mixing them = slower, costlier, dumber.
Resilient systems don’t break. Reliable systems don’t fail. Reusable systems don’t get rewritten.
Start building like you mean it.
