Blog

Hello World — Starting with Clean Code

Welcome to the Kendine Coder blog! In this first post we talk about clean code principles and the 'Kendine Coder' philosophy.

Hello! 👋

This blog is the journal of a developer who loves writing clean code, wants to keep his technical independence and believes in constant improvement.

Why Clean Code?

Clean code isn't just code that "looks nice". Clean code is:

  • Readable: Another developer (or you, six months from now) can understand it easily.
  • Testable: Every function does one thing, and dependencies are clear.
  • Maintainable: Making changes and adding new features is easy.
💡

As Robert C. Martin put it: "Clean code always looks like it was written by someone who cares."

An Example: Naming

Bad naming:

const d = new Date();
const x = d.getTime();

Clean naming:

const currentDate = new Date();
const timestampMs = currentDate.getTime();

The difference looks small, but in large projects readability is everything.

Next Steps

On this blog I'll regularly write about:

  1. Refactoring techniques — How do we modernize legacy code?
  2. API design patterns — RESTful, clean endpoint design
  3. Real-world experience — Lessons from SaaS projects like EmlakBase

Stay tuned! 🚀

0

Comments

Be the first to comment

Share Your Thoughts

No comments yet. Be the first using the form above!
ME

Muhammed Emin Özdemir

Senior full-stack developer at VakıfBank. Focused on enterprise systems, clean code and LLM-based tools.

More about me →