How to write clean code units (functions and methods)

Code units at the edges of your application should be small, independent and only do one thing…. » DEV Community | dev.to

30 de abril de 2021 · 1 min · 22 palabras · Nacho Cano

My Top 4 Patterns for Writing Simple Code

When it comes to writing code, I aim to write simple code. What Bob Martin calls clean code. What oth… » DEV Community | dev.to

3 de agosto de 2020 · 1 min · 25 palabras · Nacho Cano

You dont believe in clean code

What has clean code ever done for us? » DEV Community | dev.to

6 de julio de 2020 · 1 min · 13 palabras · Nacho Cano

10 practices for readable code

I’ve been writing code for 20 years. During that time I’ve worked with 17 teams coding different languages to build hundreds of projects. These include everything from a simple blog site, to APIs supporting 3,000 requests/second, to top selling apps. From these experiences, combined with the books I’ve read, it’s become apparent to me what matters most in code: readability. » Jason McCreary | jason.pureconcepts.net

19 de septiembre de 2018 · 1 min · 65 palabras · Nacho Cano

The Exceptional Beauty of Doom 3’s Source Code

What would ”nice looking”—or ”beautiful”, for that matter—actually mean when referring to source code? I asked some programmer friends what they thought that meant. Their answers were obvious, but still worth stating: Code should be locally coherent and single-functioned: One function should do exactly one thing. It should be clear about what it’s doing. Local code should explain, or at least hint at the overall system design. Code should be self-documenting. Comments should be avoided whenever possible. Comments duplicate work when both writing and reading code. If you need to comment something to make it understandable it should probably be rewritten. » Shawn McGrath | kotaku.com

8 de febrero de 2015 · 1 min · 106 palabras · Nacho Cano