100 tips to write clean code:

👇 Clean Namings:

1. Use intention-revealing namings
2. Capture business knowledge
3. Avoid encoding and technical details
4. Use pronounceable names
5. Use searchable names
6. Avoid noise and redundant words
7. Use strong words
8. Don't use abbreviations

It has been 10 years since I wrote my first line of code. Time flies!

Here is a list of 10 honest takes on the job and the industry.

🧵👇 1️⃣ Years of experience is a poor proxy for skill level.

It is not about how many years you spend as a developer.

It is about how much knowledge and experience you fit into those years.

Writing good Git commit messages matters!

A thread about how to write clean commit messages:

🧵 👇 1️⃣ Make your commit messages meaningful, explaining the reason for the change. The more explicit the message is, the more helpful it will be.

Examples:

❌Don't:
- fixed
- done
- added 2 class

✅Do:
- add missing validation to login form
- fix bug for calculating cart price

You always wanted to use Test Driven Development (TDD) but you don't know where to start?

Here is a thread for you about TDD in practice.

🧵 👇 1️⃣ Familiarize yourself with the three laws of TDD

These rules are the fundamentals of using TDD in practice. They constrain us to change only one thing at a time. They force us to apply babysteps!

Memorize and strictly follow these rules in order to use TDD efficiently!