⚛️ React tip: you should almost never fetch inside render. Start fetching as early as possible, e.g. on route change or when an event occurs (click, submit, etc.). Mental model should be: ✅ Read from fetched data in render NOT: ❌ Start fetching in render

Code reviews can be very beneficial, but they're conducted once the code is done or almost done To increase productivity and reduce risks and failures, you've to aim to receive feedback much earlier

Don’t miss this!!!

Sarah Drasner Developers have 3 ways to communicate with one another in a codebase: -Naming -Punctuation -Indentation/Formatting Can only do so much with the latter two. Best believe the naming should be good! I heard this recently on some YouTube video ^

"...consider the case of the developer who claims ten years of experience, but in reality it was one year of experience repeated nine times. That doesn’t count as experience." What you do during your years of experience is what matters, not the number of years.

Fernando First, make it work. Then make it right. And finally, make it fast.

Avoid logic in your test code! - if-else statements - for/while loops - switch cases They can easily lead to bugs in tests. Once you feel the need for these, it's a smell that you test more than one thing. Get rid of them by splitting up your test into multiple test cases.

PRs were created to protect the code from contributions from people outside the team of maintainers If your team is the project owner and can fix any error ASAP, then why delay the code from being delivered, especially when it's published to dev env first?

If you prefer debugging over testing is because you didn't invest time in testing in the earlier stages of the project Now you've thousands of lines of code without coverage, and to test anything you've to mock a ton of services Do yourself a favor and add tests from the start

⭐ avg. software engineer when encountering a problem -> how to solve the problem. ⭐⭐ good software engineer -> analyze the root cause and prevents the problem from happening again. ⭐⭐⭐⭐ great software engineer -> how to avoid the problem in the first place, not solve it.

The biggest irony is that agile actually contributed to the degradation of software quality. We are supposed to experiment, get quick feedback and refactor. The experiments go straight to production, we never look for that feedback, and we never have time to refactor.

Measuring a Software Engineer's productivity by counting lines of code instead of value created, it's like measuring the delivery guy by tracking kilometers instead of deliveries. Anyone can hack such vanity metrics, causing damage for both the company and the employee.

I just came back to Twit… now X only to congrats Maxi Contieri for his new book “Clean Code Cookbook”🎉🎉 I’ll get a copy as soon as I finish my current reading list 😅

I truly admire tech leaders back then without AI So many things to write an summarize, emails to compose, proposals, diagrams… ugh

One thing I miss after the AI trend is to work with Juniors They had always a fresh point of view, were very informed regarding new topics and had a ton of energy; and they were always eager to learn new things it was always a win win situation to work with them

It’s very easy to be busy but much difficult to be productive I prefer focus work

Come and learn how to migrate to another testing library without leaving your project unprotected. I’ll be working on the second part this week. Incremental Testing Library Migration: A Step-by-Step Guide: Part 1 { by Rodrigo } from Hashnode blog.rodrigomd.dev/incremental-te…