Had to click because this content is underrated In the context of conveying alot of information smoothly and draw intuition quickly beyond words. and it shows you put alot of thought into it. MindMaps FTW Thanks Caleb !
This is golden content. I'm glad I came across this video, as someone who has been in the field for some time I can agree that knowing all this as a developer will make your life super easy. Subscribed so that I can get more of this.
Thank you very much for this video! I am actually in college and taking a database development & design class! Seeing this video reinforces my energy, and mindset. 🔥
Great tutorial Caleb! I've been learning webdev for a few years now and have come across most of these terms you cover, but this is the first time I've had them all explained from a higher-level viewpoint. The penny drops when I see how you've grouped things together, since I may already know, for example, what a webhook is, but didn't realise it's place in the webdev world is alongside REST. Very helpful - thank you. Duncan.😁
We were waiting for the step-by-step roadmap. And continue this type of content, you could do it on the frontend and after the accea and full-stack, devops, etc. You would have one video for the mind map and one for the roadmap for each. Keep Up The Good Work!
This video really explains everything I'm curious about and it's perfect. As a junior frontend developer, that explanation is very basic and understandable
Great video concept. I’d like to see another iteration where you take all the languages, frameworks, and other concepts you don’t know well and reference the docs for a more accurate and concise explanation. Your audience are engineers after all.
Thank you Caleb so much I have I long career in technology this is the most valuable video I have EVER watched. I have taught in corporate universities and mainstream universities. The world must be mad if this doesn't become the definitive back-end reference video. Looking forward to seeing you speaking at conferences :-)
I watched this video to learn about the core concepts used in backend development, not just technologies. I mean concepts like message queues and design patterns-whether they are part of this roadmap or not-along with a quick example for each concept. But it turned out that it was literally about the technologies used. Maybe it’s my fault for thinking that the complete roadmap for backend engineers was only about technologies. Anyway, I don’t mean to belittle your effort. Thank you. I just hope that you focus on teaching concepts rather than technologies, because technology is always evolving, whereas deeply rooted concepts remain unchanged. If anyone here has any idea about what I was searching for in this video but couldn’t find, please don’t hesitate to share, even a little.
Delphi / Lazarus are very powerful contenders. Blazing fast compiler and binary, very expressive language (in-built readability) which is great to manage large code bases and their back-end development capabilities are simply not talked about. I often wonder why.
Please, if you are a junior just starting out, please know that simplicity is the most important goal you should go for. Fight with tooth and nails to keep another technology out of it. A simple postgres and a monoloitic application on Linux, without docker, kubernetes and etc, can take you much further than it looks. I speak from experience. It is much more painful to recover from overengineering than to introduce a new complicafion when you have already exhausted all your other options. Also be very critical. If someone tells you gRPC is faster then JSON and REST benchmark it in real world situations. Be very critical of any new thing. And if you can avoid adding it by just doing a few manual steps, do those steps.
Speak for yourself man , my repo is %68 go, %21 docker, and %11 bash scripts, I'm having a blast. I have developed an innovative antipattern: The Modular Monolith Monorepo
@@Dom-zy1qy why do you feel we are talking about different things? I am talking about when you introduce microservices, kubernetes, teraform, rabbitmq, logstash, elastic search, Kafka and gRPC to the same project. Your project structure actually seems pretty conservative when it comes to backend.
My choice for backend technology is Swift and Hummingbird. Server Side Swift is not necessarily tied to Apple although developers that know Swift tend to come from iOS/MacOS. Swift has evolved really nicely as an open source programming language for many years. It is a very modern language with amazing performance. I've chosen Hummingbird as it is much simpler than Vapor, they are both based on Apple's SwiftNIO framework. I believe this choice is much easier to implement while achieving better performance than most others, if not all. I must admit that a big part of my choice is the fact that I'm an iOS/MacOS developer and using the same language for both the client and server is a big advantage, specially when in Swift you have the Codable protocol which allows you to easily transfer any Codable Struct between client and server using the same Swift code for defining the models. For my personal projects ( outside my day job ), as the only developer, I'd be more than happy to have a successful App targeting iOS/MacOS only without support for Windows or Android.
Hi, Caleb. I wanted to apply for the mentorship but I won't qualify because I'm from South Africa. But, thank you for this amazing work here, esp with this road map.
Hey caleb , really nice video ! I was wondering if I could help you with more Quality Editing in your videos and also make a highly engaging Thumbnail and also help you with the overall youtube strategy and growth ! Pls let me know what do you think ?
Prisma support for MongoDB is very limited, specially if you want to do something a little complex like search on the whole table or a combination of tables (joins)
Usually, the most cost-effective thing you can do is define what your business goals are, identify the market, your risks, your advantages, and other product canvas topics. The hardest part of creating a product is knowing what you want to make and figuring out how to measure success, not in the specific coding language. Good luck!
Each one has their own preferred technology stacks. The best thing you can do is learn something you are interested in and make something cool with it. The specific languages are secondary to understanding the general concepts and demonstrating that you have talent and motivation, but mostly motivation. Good luck!
