All You Need To Know About Backend Engineering

Here's all you need to know about backend engineering. What is back end development exactly? How hard is back end engineering? Should you become a backend engineer?

[ultrahalf]

Frontend = neck pain
Backend = back pain
you feel me?

[ddd]

1) APIs
2) Databases
3) Third-party services
4) Infrastructure

[saadakhtar]

Really enjoyed it, always loved your content. Exactly right combination of major works in Back-end.

[musa]

Your energy when explaining things is so so good. I was engaged from the word go. Thank you so much for this info.

[MeggaMortous]

Even though I would ideally like a combination of both backend and frontend, backend and logical thinking will always be my main drive for programming. That being said, I'm still a big noob on software architecture design, so thanks for some of these tips :)

[techwithwhiteboard]

youtube recommends this to me in an hour

me : extreme unsatisfaction

i need this recommended in 5 minutes

[dshaane]

Thank you for this video Clem! Very informative as always

[ordep]

Hi, Clement. First of all, congrats for your great work here. You express your thoughts clearly and the videos are all very insightful.

This video is not different, great separation of concerns on backend responsibilities here and I would also add the work on developing code related to the domain you are working with, solving the problem your business is in.

From my experiences, all front-end development have similar domain, it means the main issues we face are related to UI, state management, network requests, etc.. But when working in the backend, *understanding* your core domain, designing a model that better fits the needs you have and developing code related to it is a day to day activity.

Keep the great work!

[Brandon-sewn]

Thank you for this video, have been looking for something like this for a long time

[ansonyu]

This video earned you a sub, straight to the point and super useful information :)

[daijagibbs]

So far, these videos are precisely what I've been looking for.

[bitwisedevs]

It's always really good to hear your point of view and I can agree to all of what you said. Your message is clear and straight to the point no unnecessary extra technical word and all idea really comes from solid experience. You are one in a million idol.

[timsims]

Speaking of API design, would you considering make some api design videos or interview videos ?

[helloWorld]

yes. long form, but separate videos with all the information you can give us about the types of work (emphasis on beginner, we're watching videos after all) of both frontend and backend work. answers to questions like: per role - how much do we need to know and of what before we can seriously apply to jobs in that role? i'm focused on backend but i'm sure people would also be interested in frontend information too. great vids, and thanks for everything.

[ChandanNayak-lqpd]

Hi Clement,
At the outset I love your content, and I have watched all your videos.
Please do the comparison video between frontend and backend, as well as mention the resources for the same.
It would be nice, if you made a video on machine learning/data science.

[GinChunkz]

Very good info. Definitely clears up my idea of a back end engineer. Thank you!

[ArchHyperion]

Just want to let you know Clement that I freakin got 5 job offers in my recent job hunting using your algoexpert tool. I'm a mid-senior guy doing fullstack. Thanks to your tool I had sleepless nights deciding what country I should move to..

[jetmartin]

Great quick overview of the backend development role. Thanks.

[Beny]

Thanks Clemente. This is a brilliant post.

[Grr]

One additional point to note is that backend engineer has to take into a account large volume of simultaneous calls of his APIs. This is something that front-end engineer typically is not concerned about, but for back-end engineer scallability, reliability, and all those ility words requires a lot of attention.