Petar Ivanov
@petarivanovv9.bsky.social
Practical React, Node, and Software Architecture Tips 🔥
Author of “The Conscious React” book ⚛️
Author of the "The T-Shaped Dev" newsletter 🧙
Join 17K+ devs → thetshaped.dev
Author of “The Conscious React” book ⚛️
Author of the "The T-Shaped Dev" newsletter 🧙
Join 17K+ devs → thetshaped.dev
Links: react.dev/blog/2025/02...
Sunsetting Create React App – React
The library for web and native user interfaces
react.dev
February 15, 2025 at 10:34 AM
Links: react.dev/blog/2025/02...
After the learning process, you can move to Vite-based frameworks.
This way, you've mastered the basics, and the transition to a framework is easy.
This way, you've mastered the basics, and the transition to a framework is easy.
February 15, 2025 at 10:34 AM
After the learning process, you can move to Vite-based frameworks.
This way, you've mastered the basics, and the transition to a framework is easy.
This way, you've mastered the basics, and the transition to a framework is easy.
The docs recommend starting with a framework.
However, I still think it would be beneficial for anyone who is starting with React to start with plain Vite.
However, I still think it would be beneficial for anyone who is starting with React to start with plain Vite.
February 15, 2025 at 10:34 AM
The docs recommend starting with a framework.
However, I still think it would be beneficial for anyone who is starting with React to start with plain Vite.
However, I still think it would be beneficial for anyone who is starting with React to start with plain Vite.
We must adapt and make AI our ally, not our enemy.
Otherwise, someone who does will take over our job.
Otherwise, someone who does will take over our job.
February 11, 2025 at 3:03 PM
We must adapt and make AI our ally, not our enemy.
Otherwise, someone who does will take over our job.
Otherwise, someone who does will take over our job.
Mistakes are a free classroom.
We learn and grow from them.
Otherwise, we can't progress forward and then move only backward because there's nothing like a permanent state in the universe.
We learn and grow from them.
Otherwise, we can't progress forward and then move only backward because there's nothing like a permanent state in the universe.
February 9, 2025 at 9:42 AM
Mistakes are a free classroom.
We learn and grow from them.
Otherwise, we can't progress forward and then move only backward because there's nothing like a permanent state in the universe.
We learn and grow from them.
Otherwise, we can't progress forward and then move only backward because there's nothing like a permanent state in the universe.
Nothing can beat real-life experience and getting your hands dirty.
February 9, 2025 at 9:41 AM
Nothing can beat real-life experience and getting your hands dirty.
Communication skills are vital for a good Software Engineer and a Leader.
We must express our ideas clearly, listen carefully, understand others, and discuss problems and ideas humanely.
Well said, Josh!
We must express our ideas clearly, listen carefully, understand others, and discuss problems and ideas humanely.
Well said, Josh!
February 6, 2025 at 4:06 PM
Communication skills are vital for a good Software Engineer and a Leader.
We must express our ideas clearly, listen carefully, understand others, and discuss problems and ideas humanely.
Well said, Josh!
We must express our ideas clearly, listen carefully, understand others, and discuss problems and ideas humanely.
Well said, Josh!
Type-driven development is the practice of defining types upfront, making sure of type consistency across the application, and making illegal states unrepresentable.
This approach leads to slower short-term output, but leads to easier, more reliable coding in the long run.
This approach leads to slower short-term output, but leads to easier, more reliable coding in the long run.
February 5, 2025 at 3:20 PM
Type-driven development is the practice of defining types upfront, making sure of type consistency across the application, and making illegal states unrepresentable.
This approach leads to slower short-term output, but leads to easier, more reliable coding in the long run.
This approach leads to slower short-term output, but leads to easier, more reliable coding in the long run.
When I start refactoring code or working on a new feature, I run the `test:watch` command and monitor how the changes impact the tests and vice versa.
February 5, 2025 at 3:09 PM
When I start refactoring code or working on a new feature, I run the `test:watch` command and monitor how the changes impact the tests and vice versa.
It will automatically rerun tests related to the changed files and speed up the feedback loop from your tests.
February 5, 2025 at 3:09 PM
It will automatically rerun tests related to the changed files and speed up the feedback loop from your tests.
Great breakdown, Neo!
February 3, 2025 at 2:50 PM
Great breakdown, Neo!
Benefits of mastering one language:
1. Deep Expertise
2. Becoming the go-to person
3. Easier to learn new technologies
1. Deep Expertise
2. Becoming the go-to person
3. Easier to learn new technologies
February 3, 2025 at 8:59 AM
Benefits of mastering one language:
1. Deep Expertise
2. Becoming the go-to person
3. Easier to learn new technologies
1. Deep Expertise
2. Becoming the go-to person
3. Easier to learn new technologies
💡 My advice: Always start with React’s built-in tools for state management and evolve when necessary.
Don’t add unnecessary complexity. Keep things as simple as possible.
Don’t add unnecessary complexity. Keep things as simple as possible.
February 3, 2025 at 8:58 AM
💡 My advice: Always start with React’s built-in tools for state management and evolve when necessary.
Don’t add unnecessary complexity. Keep things as simple as possible.
Don’t add unnecessary complexity. Keep things as simple as possible.
🟢 When to consider a State Management Library?
• Complex state logic across multiple components.
• Large applications.
• Complex state logic across multiple components.
• Large applications.
February 3, 2025 at 8:58 AM
🟢 When to consider a State Management Library?
• Complex state logic across multiple components.
• Large applications.
• Complex state logic across multiple components.
• Large applications.
🔴 When NOT to consider a State Management Library?
• Small to medium-sized applications.
• Simple UI or state logic.
• Short-term projects or prototypes.
• Small to medium-sized applications.
• Simple UI or state logic.
• Short-term projects or prototypes.
February 3, 2025 at 8:58 AM
🔴 When NOT to consider a State Management Library?
• Small to medium-sized applications.
• Simple UI or state logic.
• Short-term projects or prototypes.
• Small to medium-sized applications.
• Simple UI or state logic.
• Short-term projects or prototypes.