Why Frontend development Is More Important Than Backend?
Vložit
- čas přidán 6. 05. 2024
- ► Join my Discord community for free education 👉 / discord
► Full Projects, Mini courses, Resume reviews, and Coaching 👉 thetotalcoder.com
► 33% OFF on my Go + HTMX + Templ Course 👉bit.ly/3UFruxO
► Enjoy a 60% Black Friday Discount on My Golang Course 👉 fulltimegodev.com
► Follow me on Twitter 👉 / anthdm
► Follow me on GitHub 👉 github.com/anthdm
#coding #softwareengineering
A backend developer doing frontend will give you a functional but not so pretty product, a frontend developer doing backend will give you Internal Server Error.
😂
server error is straight forward error easy to google to fix. issues with css positioning, flexbox, container queries, js perf issue ?? good luck
@@tomjones8293 A server error is not necessarily easy to fix, it depends on what caused it. Could be a deep nested race condition if you're not careful. You completely missed the point though which was that a backend doing frontend simply results in a product that could look better, whilst a frontend developer doing backend will result in a non-working product.
@@InfinityNnot working product ??? serverless api gateway easy to fix !! what you on about ? front end js memory leak jumpy content. slow asss loading and so on.. you need IQ over 110 to fix those front end unlike clear cut server errors which are very straight forward error.very easy to fix hope this helps
@@tomjones8293oh sweet summer child if that's all you think backend is...
This man is true legend
Fugazi - nice reference 😂
I have been developing front end for 1 year, 8 months of which I developed at my workplace. However, what front enders miss is not caring about backend logic at all.
It works both ways. Flip front/end in your statement and will also be true. ¯\_(ツ)_/¯ Once, Bootstrap had been called: "framework for lazy backend devs". Now it's the same with things like templ and htmx. The problem is, backend "just" works, but frontend sells. (backend dev here)
But you could fake frontend reactivity with backend rendering techniques. e.g using things like htmx. All you need is a nice css and you're done (I would argue that although css is frontend, this techstack is more backend-heavy. Just like you compared having nice frontend and an excel backend).
Edited: Bad UI falls into UI/UX design. I would say you can have a dedicated web designer for that - in which frontend dev would just be handling code (meaning that it would still be backend heavy).
Hey Anthony, I had a small question. What would say about learning Swift, using go and swift for fullstack ios macos apps? Is this a good path or should I stick with flutter and go?
Swift very good for mobile!
@@anthonygg_ hey thank you so much man, NGL your videos helped me get from a timmy to a chad real quick in go
fact!
Smoke and mirrors baby, if it looks good you will get people interested, if people are interested then you get more time and budget
Next zee yes
😅 was is that bad
@@anthonygg_ not at all its unique
Sorry what do you mean by “behind the scenes it was a fugazi” … please explain with clear examples of what this means, rather than generic english words. Are you saying that the frontend (written in next.js) was making calls to backend owned by some 3rd parties and not your company?
likely that there was just no backend at all, or it was super basic, or that it was using something like firebase/supabase.
@@user-ek2jc1xf3y Probably some shared excel file :)
And fullstack ain't hard these days with stacks like VILT and TALL (for Laravel devs)
You don't even have to leave JavaScript with MERN. Sure, your project may turn out to be memory hungry garbage, but still.
Without a frontend, there is no backend?? That's a crazy take to say
yeah, in case of those applications that don't need any frontend
Frontend doesn’t matter for devops. Devops users are power users and they’ll be on the terminal as much as possible. Outside of monitoring dashboards etc.
90% of what makes your life run is old, reliable, back-ends.
I don't know why everyone thinks they're going to work for the next big start-up, or create something brand new. Most of us will work for established companies that are using frameworks, back-ends- and infrastructure that you'd consider outdated.
you'd be surprised, I'm confident in saying most people work for immature startups, underpaid.