Steve P.’s Post

Frontend development is a journey, not a shortcut. You don’t start with React. You don’t jump straight into TypeScript. And no framework can save you from weak fundamentals. This image tells a story every frontend developer knows: 🚗 HTML the old engine that still holds everything together 🚙 CSS makes it look good, but only if you understand it 🏎️ JavaScript speed, power, logic (and bugs 😅) 🏁 React productivity, structure, scalability 🛻 TypeScript safety, confidence, long-term maintainability Each layer builds on the previous one. Skip one and the ride gets bumpy. The real difference between a tutorial developer and a professional? Understanding why things work, not just how to make them work. Frameworks evolve. Fundamentals stay. What part of this journey are you currently driving? 👇 HTML, CSS, JS, React or TypeScript? #FrontendDevelopment #WebDevelopment #JavaScript #React #TypeScript #Programming #DevJourney #CleanCode

  • No alternative text description for this image

Currently I am into react and typscript. Sometimes I find myself having to look up fundamentals again. But let’s be honest, Who doesn't have to? The more interesting question is. Which learn method especially for beginners is better? Top down or bottom top?

estas son mamadas, todos esos lenguajes son complementarios

I was lucky enough to start web development in an era when things were simpler. HTML, CSS, and plain JavaScript were the default without many other options. Over the years, the ecosystem evolved and evolved fast and aggresively. Frameworks like React, Vue, and Angular didn’t appear out of thin air. They were created to fill gaps and to compensate for missing standards, inconsistent browser APIs, and the lack of scalable patterns in vanilla HTML and JavaScript at the time. Now we’re at an interesting pivot point. Many of those gaps are closing. Native web standards have matured. Web Components, modern CSS, and browser APIs allow us to build things that previously required heavy frameworks. And yet, frameworks are still the default choice. Not because they’re the best tool, but because they’re familiar and comfortable. The result is that a lot of developers jump straight into frameworks without truly understanding what they’re built on. That works, until it doesn’t. So to answer your question directly: learn the fundamentals first. Deeply. And get familiar with what modern browsers already give you out of the box.

Like
Reply

The ride had gotten bumpy for me,then I decided to slow and do a deep dive on JavaScript 

Like
Reply
Like
Reply

I’m currently on the fundamentals as I’m still figuring it out

See more comments

To view or add a comment, sign in

Explore content categories