- 29. Compound.Components and Context
Scheduled for Friday, February 15
The combination of the dot syntax and context can make a component smart while keeping composition intact at the same time.
- 28. Rethinking the component model with Hooks
Compared to classes, hooks expose edge-cases early. This is great for correctness of the application, but annoying to deal with early on.
- 27. Just use children
No, this isn't a post about child labour. It's a post about using children as props. Wait that doesn't sound right either. It's about writing good components, okay?
- 26. Forming habits that stick
Here's everything I learned from reading half of the book Atomic Habits
- 25. Beware of the Apropcalypse!
It's all fun and games when you just one more tiny prop but suddenly you're drowning in props!!
- 24. Order of props matters!
Welcome to the weird world of difficult to debug bugs because of order of props.
- 23. Don't set new year goals
It's that magical time of the year where you contemplate if you wasted the entire year and start making plans for the next one.
- 22. Give names to behaviors not interactions
Naming event handlers is easy, until you put all your components together.
- 21. Don't create conflicting props
When it comes to React components, props are the API that developers consume.
- 20. Obsession treadmill
I struggle with doing things passively. When I want to try something new, I get obsessed with it. It's a problem.
- 19. Let me teach you React Hooks
I teach a beginner's React workshop and this is how it usually goes
- 18. Spacing for reusable components is hard!
When I started working on cosmos, I didn't think spacing was a big deal. Boy, was I wrong!
- 17. Standup Driven Development
If you work for a technology company, there are high chances your team already does
stand-ups... and you probably already hate them.
- 16. Design systems for the rest of us
You probably don't work in a fortune 500 company with dozens of developers and designers
working on a design system. Neither do I.
- 15. On Burnout
Burnout is a mythical creature that sounds like excuses a lazy person would make until
you experience it for yourself.
- 14. Taking one step back and four steps forward
I spent the last week with my team standing in front of whiteboards planning, here's what I realised.
- 13. Should frontend developers learn data structures?
To understand how to do well in an interview, you need to put yourself in the company's shoes.
- 12. Rebuilding my website with Gatsby in 15 minutes
The fomo is real. Finally tried out Gatsby and was way easier than I expected!
- 11. On golden handcuffs
When you don't love your job, but love your salary
- 10. Generating images on the fly using puppeteer
We did a fun twitter sharing thing for stackstickers generating screenshots on the fly, here's how
- 9. Contributing to open source is overrated
I used to think contributing to open source is cool. It's the next step you take as a developer.
- 8. Video games and React state
There is a lot we can learn from video games. Modern games render hi-def graphics based on heavy calculations and still run smoothly.
- 7. Startup or big company, where should you work?
Last year, I was looking for a new job and this question was stuck in my head. Should I join a big famous company or a small startup?
- 6. Five minute guide to React
If you have been hearing about React but didn't find time to get into it, that's perfect. Let me teach React to you. If you already use React, this is still going to be useful for you.
- 5. ️Work doesn't happen at work
My thoughts about the workplace have changed a lot over time. I now believe that work doesn't happen at work.
- 4. ️How do you measure your personal growth?
Oh man, this is a hard one. Dipti asked me a while back and I've been thinking about it again last week.
- 3. How do you start a side project
This week's newsletter is full of practical ideas that you can apply! I'm really happy with how this came out
- 2. The best way to learn something
Learning for the sake of learning can be demotivating. Here's my way of learning that almost always works
- 1. How do you decide what to work on?
Hey from Sid! Remember signing up for this?