Clean-Code on Karpoke - Just Another Blog

How to Implement the SOLID Principles in Flutter and Dart

Thu, 02 Oct 2025 11:49:30 +0100

How to Implement the SOLID Principles in Flutter and Dart

How to Write Clean Code – Tips for Developers with Examples

Wed, 06 Nov 2024 07:19:31 +0100

Imagine a messy room with clothes, books, and other items scattered everywhere. Finding something in that room would be tough, right? Now, think about writing messy code – it’s just as confusing, if not more! On the other hand, clean code is like an …

» freeCodeCamp.org | freecodecamp.org

Clean Code: Single Responsibility, Open/Closed, Liskov Substitution SOLID Principles in TS [Part 4]

Fri, 10 Nov 2023 10:57:24 +0100

In this article, we will look at the three first SOLID principles: The Single Responsibility Principle, the Open/Closed Principle and the Liskov Principle.

» hackernoon.com | hackernoon.com

PyBites: When to refactor your code?

Sat, 12 Aug 2023 02:21:51 +0100

PyBites: When to refactor your code?

» pybit.es | pybit.es

How to Find the Stinky Parts of Your Code [Part XXXIX]

Tue, 20 Jun 2023 10:59:23 +0100

It smells because there are likely many instances where it could be edited or improved.

» hackernoon.com | hackernoon.com

106 Stories To Learn About Clean Code

Thu, 13 Apr 2023 07:42:32 +0100

Learn everything you need to know about Clean Code via these 106 free HackerNoon stories.

» hackernoon.com | hackernoon.com

How to eliminate if-else chain, for long life software

Tue, 18 Oct 2022 16:54:49 +0100

Motivation All programing principles and paradigms aim to enhance code readability and…

» DEV Community | dev.to

How to Find the Stinky Parts of Your Code [Part XXI]

Sun, 24 Jul 2022 12:15:37 +0100

Code smells are a classic. It smells because there are likely many instances where it could be edited or improved.

» hackernoon.com | hackernoon.com

7 Tips For Clean Code

Sun, 01 Aug 2021 20:18:28 +0100

It’s all about maintaining clean and readable code(which works of course). So, I wanted to share a…

» DEV Community | dev.to

Clean Code Part 2: Functions

Mon, 05 Jul 2021 13:40:57 +0100

This is part 2 of the series of Clean Code By Robert C. Martin. If you haven’t gone through the part…

» DEV Community | dev.to

How to write clean code units (functions and methods)

Fri, 30 Apr 2021 08:45:42 +0100

Code units at the edges of your application should be small, independent and only do one thing….

» DEV Community | dev.to

My Top 4 Patterns for Writing Simple Code

Mon, 03 Aug 2020 16:20:43 +0100

When it comes to writing code, I aim to write simple code. What Bob Martin calls clean code. What oth…

» DEV Community | dev.to

You dont believe in clean code

Mon, 06 Jul 2020 22:55:09 +0100

What has clean code ever done for us?

» DEV Community | dev.to

10 practices for readable code

Wed, 19 Sep 2018 19:59:00 +0100

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

The Exceptional Beauty of Doom 3’s Source Code

Sun, 08 Feb 2015 19:25:00 +0100

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