Top 3: technical debt is evil?, the code review pyramid and codebases with clean code

Hello my friends.

Here's what I picked this week, enjoy!

1. Technical Debt – Good or Evil?​

TL;DR: What technical debt really is and why it’s neither good nor evil.

My notes:

• Technical debt is neither bad nor good, it’s a tool to achieve certain goals: reduce time to market, development costs, and save resources.
• Badly written code or a poorly chosen library is not a technical debt, it's the wrong solution to a problem.
• The technical debt must be taken meaningful with a clear plan of its repayment.
• If you don’t pay the technical debt the opposite of what you took it for will happen - the time to reach the market will increase, development costs and the amount of resources needed (time and money) will increase.

2. The Code Review Pyramid​

TL;DR: An interesting mental model in the form of a pyramid on how to code review.

​

Too complicated to put into practice, but you can learn something from it.

3. Ask HN: Codebases with great, easy to read code?​

TL;DR: A list of repositories with clean code to raise your coding skills.

🦚 Tweet of the week

When you created a thing that everyone doesn't use the way it was originally intended.

Steven Pemberton @stevenpemberton CSS co-designer here. !important was added for one reason only: laws in the US that require certain text to be in a given font-size. !important stops the cascade from changing it. Anything else is probably misuse, and a sign you may not understand the cascade properly. March 21st 2022 707 Retweets 3,451 Likes

That's all for this week, take care and have a great one!

– Nick

If you're enjoying the newsletter, share it with a friend or two. Here's one quick way you can do it in 5 seconds:

​Share with Twitter, WhatsApp, Facebook, LinkedIn or copy & paste this link: https://nickbull.me/top-3​