@joaoqalves Might be due to the constant pressure to consume content in social networks about every new library and language. Overall, doing is probably a better method. On the other side, when jumping into an unfamiliar language, a high quality tutorial/book can save a lot of time.
Bugs still happen. It's often so easy to put them under the rug and never come back until we find a bug in production, which leads to hundreds if now thousands of warnings appearing in our test output.
Learn to avoid this situation with @victorandcode: https://t.co/EZG2AMzYCr
One powerful technique to debug weird issues is to create a small project from scratch that reproduces the issue
Debugging on a production app has many layers of noise that can make it harder to find the culprit
Since now I'm "at the office" most days of the week with remote work, I find I need to improve how to take breaks. Here's a good start:
https://t.co/9Vo8eLjRLu
@b0rk When debugging I always follow this format
- Write hypothesis
- Write how to validate each hypothesis is wrong
- Document everything I find
- Verbalize current train of thought to keep me focused
Hope it's useful!
Amazon is well known for prizing clear writing.
One well written design doc can save you *thousands* of wasted dev hours. And when you've shipped, you can better advocate for your team by writing up your achievements.
Writing is a career superpower. Here's a guide.
I'm turning 35 today! 🎉
As I grow older, I'm realizing the value of principles to make decisions and guide behavior. What are yours?
Here's 35 of mine:
I recently started reading "Staff Engineer: Leadership beyond the management track" from @Lethain and the first chapters are already providing a lot of value to me.
Clear, specific advice based grounded on real experience.