@@jgalvan09 facts, many computer science students i met in university don't even do programming.. i rather have cringy friends who are actually interested in these things than those who studied it just for the exams.
This is really me right NOW!! Was always a purist, till I started learning react about a week ago. Must say, I'm breezing through like it's nothing 😅😅😅..
@@RealLavalol bootstrap is better than tailwind and high in demand framework and if you learnt the concept of all css mechanism there is a high chance that you will be successful front end engineer
My current javascript portfolio is not getting any attention. I am now creating a react portfolio in hopes that it will be more impressive to a potential employer.
What props should i use, how many components to create, how to implement prop drilling, and css alignment are the common issues i have as a backend developer.
1. You use whatever props you need. If you don't need to pass information to components, you don't need props. 2. As many as you need as long as you're not overdoing it. And try to make them reusable. 3. You don't want to do prop drilling. Context API or Redux. 4. Flexbox. Or grid. Grid is more powerful. But flexbox works too.
@@mjmopperman React is anything but. It's so bad any derogatory description would be an understatement. If you must use something like React at least use Solid.js. But seriously anything else is better. Vue.js, Svelte, Angular even. I always assume people that think React is awesome must not have tried anything else. That or there is something wrong with them. There are literally no good reasons to use it.
A true programmer builds his own fabs, architects his own CPU, GPU, FPGA, MOBO, Chipset, RAM, SD, NIC, PSU, Power Cable, Firmware, BIOS mouse, keyboard, screen, RJ45, kernel....
Id argue that a true programmer just wants to do whatever they need to do to get their ideas out of there head and into reality as quickly as possible.
I dunno if I would go that far 😂, but I definitely loved it. I just feel like having javascript and the html living in the same world together like how PHP does it was a brilliant idea.
not mutually exclusive, but it's good to favor understanding fundamentals for sure. I go back and forth because I learn new concepts in a framework that I can go figure out how doing a similar thing works in vanilla js so I know things inside and out much better.
@@GABBAROCTO don't learn js learn go, rust, c++ since they are a lower language and are statically typed you'll learn pointers and once you learn their potential you won't use javascript
In my case I find react and next a quit irritating like for just a small task you have to make whole rollar coaster I mean like common vanilla javascript is simple and easy to understand my head aches everytime I write code in react
@@danielblank9917 When seeing his reaction I wonder what that means and went back straight down to the comments section to understand that somebody talks about this exactly..😂 lol.. Thanks Daniel Blank I got it now
I'm completely absorbed in this. I had the privilege of reading something similar, and I was completely absorbed. "Mastering AWS: A Software Engineers Guide" by Nathan Vale
