How to OVER Engineer a Website // What is a Tech Stack?

laatste update: 05-2022


A β€œtech stack” includes all the technologies used to build a complete web or mobile application – like frameworks, cloud services, libraries, languages, and APIs. Let’s over-engineer a tech stack for an MVP, then simplify it. Learn how to build fullstack apps in courses

#tech #code #dev

πŸ”— Resources

Learn about popular tech in the 100 Second Playlist
Petite Vue
Stacks of successful startups
LAMP

πŸ“š Chapters

00:00 Intro
00:37 What’s in a Tech Stack?
02:05 Popular Stacks
03:08 Frontend
05:34 Backend
08:23 APIs
09:23 Petite Fire Stack

πŸ”₯ Get More Content – Upgrade to PRO

Upgrade to Fireship PRO at
Use code lORhwXd2 for 25% off your first payment.

🎨 My Editor Settings

– Atom One Dark
– vscode-icons
– Fira Code Font

πŸ”– Topics Covered

– Choosing a Tech Stack for Web Development
– Comparing JS frameworks
– React State Management with Redux
– Containers with Docker and Kubernetes
– Mobile dev with React Native, Flutter, & Ionic
– APIs with GraphQL and Apollo
– How to build a website
– Cloud Computing Concepts

30 gedachten over “How to OVER Engineer a Website // What is a Tech Stack?”

  1. my girlfriend … why is this monotone nerd shit making you laugh so hard? There is nothing fucking funny about any of this

  2. skipping continuous deployment… hahaah sure. No. It takes a little bit of work to get going, but saves you SOOOOO much time in the long run, front end wise its a joke to get going with tools like vercel and netlify, backend can be a beast, but if I figured it out as a hobbyist using Codepipeline and Codebuild any real dev should be able to as well.

  3. Dude it would have been a whole lot more helpful if you told me how to write code in VS-Code submit it to a github repo then push it to my host be it a raspberry pi or google cloud services… i'll keep googling…

  4. That's so many program languages and things you need to know in order to make even a remotely decent product that I feel I would rather concentrate on my medicine studies.

  5. so here I am, as an embedded engineer, with my tech stack of… c, some random microcontroller the company wants to use, and some drivers the manufacturer provides. Maybe we'll use jenkins or something to handle unit testing to make sure we're not about to brick one of the microcontrollers with the next build, and git. We'll throw the whole thing together with eclipse or visual studio code and start going. It's a very different world.

  6. The pain is very real, as a full-stack and DevOps, I just can't…. the last part is a must see for any new-comer programmer.

    But if your project requirement is managed by someone else, just gave up and pray to god your overtime will be paid lmao

  7. Manual deployment may work for small applications built by just a handful of engineers. But as soon as you have multiple teams building upon code that was written by other people, and all of it must play nicely together, and you have an active user base that you dont want to risk disrupting with outages, the packaging and deployment processes get more complex and more critical. And frankly, they become a lot more of a pain in the ass, and can require more developer time being spent going through the motions. And that time is expensive.

Reacties zijn gesloten.