Building stuff as a Software Engineer Clean Code / Testing / Architecture
Joined October 2019
- Tweets7.6K
- Following376
- Followers982
- Likes4.8K
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 @_rodrigomd } from @hashnode blog.rodrigomd.dev/increment…
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
I truly admire tech leaders back then without AI
So many things to write an summarize, emails to compose, proposals, diagrams… ugh
Rodrigo retweeted
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.
Rodrigo retweeted
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.
Rodrigo retweeted
⭐ 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.
Rodrigo retweeted
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.
Rodrigo retweeted
"...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.
Rodrigo retweeted
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 ^
Don’t miss this!!!
🚀 ANNOUNCEMENT 🚀
Everything about Test-Driven Development this time on the space! 😈 🔥
🎀 What is TDD
🎀 Why do TDD
🎀 Arguments against TDD
🎀 TDD when writing E2E Tests
🎀 Is TDD a silver bullet
Link to the space, set a reminder NOW -> xitter.cf/i/spaces/1zqKVPoVPjLJB
ALT TDD
Rodrigo retweeted
⚛️ 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
ALT function Component() { // ❌ Do not fetch in render! const data = use(fetch(/* ... */)) // ✅ Fetch early and read from cache // ⏳ Data might not be resolved yet const data = use(read(/* ... */)) // ... }
Remember this idea?
Well, now it's out as v1.0.1. Check it out!
github.com/rodrigo-md/envche…
