This works for a freelancer mindset, but if you are looking to get a job, which most of us are, you have to not only know all these frameworks and libraries, you also have to be cloud devops master now. The list of requirements to be a developer aren't what they were just a couple of years ago. If you can make a good living doing freelance, more power to you.
Totally with you on this. Recently discovered the power of using just php (learning with Claude! plus did a like 10-year-old Udemy course on PHP). And yes Bootstrap plus a bit of JS ... boom! "Bob's your uncle", as we say in the UK. Stef's your uncle? So many cool things you can do with just that.
@@HephzibsGospel Hi. I thought I'd already replied but it doesn't seem to be here. What I meant was that I use Claude AI to help and explain things while programming.
The a good intro/animation can make a site look artistic and sophisticated, so long as it doesn't interfere with the user ability to use the website in any way.
I've been asking myself whether to learn React first or Svelte first. I'm wondering if I'm being difficult for not learn React as that's where the jobs are, or if I should just go straight into Svelte and get better at the technology that I actually want to use because it will make things easier to maintain long term. Svelte makes the most sense if I'm trying to avoid overcomplicating things on the front end (using Go on the Backend). But many courses online including the Meta FrontEnd Developer professional certificate use React. So React feels like the thing I have to know just because it's the industry standard.
My question is, isn't it kind of important to see what these different technologies can do so one day you can decide the fastest way to make your project? If you never used Reactjs, for example, and Reactjs would make your project faster, then you'd be in the dark because you never used it. That's kind of where I'm at. I don't know what technologies will make my projects faster because I never used them or know exactly what they are for
has nothing to do with 'speed', or not necessarily. It's more about maintenablity, features, sometimes speed of developent. What's often ignored in videos like this is that building a Web API is often done, because it makes sense. E.g. you have OpenAI API you can use with Python, JS etc (Doesn matter the language, but in context of the frontent JS support is relevant.). Now, for a regular web site using something like React, Vue etc is overkill. However, if you're building an interactive application (So, it is more an application, and not a web site/page) where you want/need a lot of ineractivity, and no page refreshes, you'll anyway use JS (there's wasm nowadays, but JS is probably still the best option for most things/scenarios.) SPA (Single page applications) are often a good or better choice. You may already have an API or multiple APIs, so you already have your data and backend, now you're basically building a frontent. Why design an application from scratch like that, for one because you want APIs which can be consumed by various services, applications etc. Doesn't even have to be a web appication, or a mobile. It can be a console application, or a service (Anything that can speak HTTP). However, nowadays you have options eg JS metaframeworks like Next etc provide where you can mix various techniques and have multipage application/site, but part of it can behave like a single page application. This has pros and cons, and often a 'classic' PHP whatever site can be a better choice, especially if that's what you are familiar with. It all depends on what are you building, and what are the long term goals.
If you use the react cool stuff your project will be slower in production and in build step That's the reality of any framework, the best thing you can do is to KISS
Totally happened to me in my last team project… the team wanted to over complicate things and all voted on an insane amount of complexity… long story short, we did not get our product out on time and it was embarrassing
As you always say, go after the market and not after hype Israel, i think yoy should learn old dead langs like pearl as there huge market of old apps, like bank, while react have huge market but amount of react dev killing the competition.
Great advice and points of view
0:48 exactly describes my boss and architect decisions about tech setup of our new project.
This works for a freelancer mindset, but if you are looking to get a job, which most of us are, you have to not only know all these frameworks and libraries, you also have to be cloud devops master now. The list of requirements to be a developer aren't what they were just a couple of years ago. If you can make a good living doing freelance, more power to you.
Back in the day the first thing I would do when seeing a flash intro was looking for the damn skip button so I could get to the site index page.
Totally with you on this. Recently discovered the power of using just php (learning with Claude! plus did a like 10-year-old Udemy course on PHP). And yes Bootstrap plus a bit of JS ... boom! "Bob's your uncle", as we say in the UK. Stef's your uncle? So many cool things you can do with just that.
hey nick, is learning with claude the name of the website to learn php?
@@HephzibsGospel Hi. I thought I'd already replied but it doesn't seem to be here. What I meant was that I use Claude AI to help and explain things while programming.
We're full stack devs, dev ops, ui/ux designers, tech lead, some add in ceo, book kepper, advertising, customer service ect. It's already a mouthful 😂
The a good intro/animation can make a site look artistic and sophisticated, so long as it doesn't interfere with the user ability to use the website in any way.
I see Uncle Stef, I click.
Great video!
Right on Stef
I've been asking myself whether to learn React first or Svelte first. I'm wondering if I'm being difficult for not learn React as that's where the jobs are, or if I should just go straight into Svelte and get better at the technology that I actually want to use because it will make things easier to maintain long term.
Svelte makes the most sense if I'm trying to avoid overcomplicating things on the front end (using Go on the Backend).
But many courses online including the Meta FrontEnd Developer professional certificate use React.
So React feels like the thing I have to know just because it's the industry standard.
and here you discover that the software industry is behind the times, and uses crap software
really good advices.
Glad you think so!
About that “Skip” button, was it pressed so often because returning visitors have already seen it or because first time visitors are pressing it?
First time. That’s why the intro fad disappeared.
Good question btw!
0:53
Interesting.
Uncle stefan - chad 🧑💻
Flash was also not compatible with SEO, that became very important the same time.
Peter Levels makes a fortune with plain ol’ PHP, Jquery, HTML and CSS, right? No fancy stuff at all.
"Is the juice worth the squeeze?"
- Project Manager
My question is, isn't it kind of important to see what these different technologies can do so one day you can decide the fastest way to make your project? If you never used Reactjs, for example, and Reactjs would make your project faster, then you'd be in the dark because you never used it. That's kind of where I'm at. I don't know what technologies will make my projects faster because I never used them or know exactly what they are for
has nothing to do with 'speed', or not necessarily. It's more about maintenablity, features, sometimes speed of developent. What's often ignored in videos like this is that building a Web API is often done, because it makes sense. E.g. you have OpenAI API you can use with Python, JS etc (Doesn matter the language, but in context of the frontent JS support is relevant.). Now, for a regular web site using something like React, Vue etc is overkill. However, if you're building an interactive application (So, it is more an application, and not a web site/page) where you want/need a lot of ineractivity, and no page refreshes, you'll anyway use JS (there's wasm nowadays, but JS is probably still the best option for most things/scenarios.) SPA (Single page applications) are often a good or better choice. You may already have an API or multiple APIs, so you already have your data and backend, now you're basically building a frontent. Why design an application from scratch like that, for one because you want APIs which can be consumed by various services, applications etc. Doesn't even have to be a web appication, or a mobile. It can be a console application, or a service (Anything that can speak HTTP). However, nowadays you have options eg JS metaframeworks like Next etc provide where you can mix various techniques and have multipage application/site, but part of it can behave like a single page application. This has pros and cons, and often a 'classic' PHP whatever site can be a better choice, especially if that's what you are familiar with. It all depends on what are you building, and what are the long term goals.
If you use the react cool stuff your project will be slower in production and in build step
That's the reality of any framework, the best thing you can do is to KISS
Totally happened to me in my last team project… the team wanted to over complicate things and all voted on an insane amount of complexity… long story short, we did not get our product out on time and it was embarrassing
What's the name of the hoodie you’re wearing? 🖖🏽
Man ... I wish I knew. I bought 3 copies when I came across it. I remove the tags when I buy new clothes because they bother me.
@@StefanMischook you should start making some merch!
The answer is you should always use rails.
Always 😂
I wanna create a flash intro about Ruby. I wonder how many skips it will receive
2A for life… lol. But yea, Flash was awesome.
As you always say, go after the market and not after hype Israel, i think yoy should learn old dead langs like pearl as there huge market of old apps, like bank, while react have huge market but amount of react dev killing the competition.
90% of the time unless your building the Next spotify you don't need REACT. You may not even need it then.
Even you build Spotify , you won’t need react. React is crap
Ember is the OG
@@train_xc what's ember?
You aren't losing your hair unc. You already lost it
LOL. True!
hmmmmmm
Leave unc alone, I’m barely 34 and it’s goin fast 🥲
@@CascadiaNow69you’re writing ruby too?
So why is DHH showing his shinny long hair in every podcast after 20yrs with ruby on rails?
Maybe uncle’s loss is due to PHP instead 😂
im still using django with plain html in my own app
I just use either jquery or Ember
What is sas? 0:30
SaaS stands for software as a service
To be fair, xamarin was always buggy as hell. Other mobile cross platform technology are more stable.
It's like what people know these days
Not reactjs if you want me to visit your page.
I choose reactjs