169. What Is A Back-End Developer?

Рет қаралды 7,651

Күн бұрын

Пікірлер: 32

@IvanRandomDude Жыл бұрын

The biggest downside of BE development is stress. I was BE developer for 4 years and then switched to FE. As FE developer I sleep easy. When something does not work on FE most of the time it is visual thing and fix is easy. On BE however, some bugs can corrupt the data and create huge loss so now fixing it not only requires to fix the code but also requires data migration and it is usually a headache. There is also security concern.

@runtimmytimer Жыл бұрын

I can see how that may be stressful for someone. BE development takes a little forecasting IMHO. After doing this for 25 years it's pretty easy to know what kinds of problems to watch out for, how to design databases/components to encompass certain resiliency/flexibility issues. In my experience, it's pretty rare to have to go back in and fix data. BE development requires far more diligence when it comes to testing. That all being said, FE development doesn't make many of these concerns disappear.

@IAmTimCorey Жыл бұрын

Yeah, it all depends on who you are and what you are comfortable with. I love back-end work. Give me a complex logic problem and I'm good to go. Ask me to design a UI that is accessible, logical, and that interfaces with the back-end cleanly and it will take a bit longer to get done.

@kylekeenan3485 Жыл бұрын

Backend has never been that tedious for me accept for my current job with an application where all changes were logged for history/audit trail and it brakes for changes without history entries. So when something went wrong you couldn't just fix it with a script in the database you would have to use postman to hit endpoints to make sure all the changes were logged correctly. The endpoints available didn't always work for multiple users so you would have to set up complex postman sequences to hit a few endpoints and then run that for each user affected which could be thousands. It's rediculous.

@opietwoep1247 Жыл бұрын

Thanks for the video. It’s amazing how many levels this industry has and how deep you can go with each level. I’ve been in the IT industry since 1998. And im still learning every day. What’s put food on my table all these years is SQL Server. I was in the trades before IT but it’s very much the same thing from the different roles needed to the crazy personalities we deal with. 😊

@IAmTimCorey Жыл бұрын

Thanks for sharing!

@cirezno5960 Жыл бұрын

I waited for this topic for longtime. Thank you very much Tim 🙏🏾 From Fr 🇫🇷

@IAmTimCorey Жыл бұрын

You are welcome.

@cirezno5960 Жыл бұрын

@@IAmTimCorey Hi Tim. As a BE engineer how to explain/justify time cost on unseen tasks to clients ou chief. Unlike FE tasks, our tasks are unseen technically. For example : spending 7 days finding why that is a server blocking silently an application from writing in specified file. Had to estimate BE time costs. Thank you

@antoniusivan8767 Жыл бұрын

Since you blown my mind about. Net 6. I change job. I already deploying private kubernetes, and also writing 1 golang services, 2. Net 8 C# with open telemetry already deployed on Production. Like Microsoft build sample you talk about. 🎉.

@IAmTimCorey Жыл бұрын

That's pretty aggressive.

@antoniusivan8767 Жыл бұрын

@@IAmTimCorey also rewarding, Doubled my salary. Kick me out from old dead end job.

@greg1486 Жыл бұрын

Squats and glute squeezes tend to work pretty well

@IAmTimCorey Жыл бұрын

So that's what I've been doing wrong.

@quazeemadesope Жыл бұрын

Great video

@IAmTimCorey Жыл бұрын

Thanks!

@nGAGE0nline Жыл бұрын

I feel like working with Blazor lately, is bluring the lines between front-end and back-end quite a bit. In our current project I've mainly been responsible for the backend/services etc, but it's often required to build a base front-end structure as well (to interface with the backend correctly) for other developers to work with. I assume that's common practice, or should I have a word with management? :D

@runtimmytimer Жыл бұрын

I advertise myself as a backend developer and try to avoid front end work. However, as Tim said, it's hard to avoid. I don't do a lot of FE work but it's there unless the project is to develop APIs only. Which is pretty rare. I have this habit of just going ninja and writing tools to automate certain tasks because the product owner won't prioritize features that are beneficial. They end up being either windows forms apps or console apps. Oddly, a lot of these things turn into product features. We are entirely Azure so to spin up an ASP for this stuff isn't feasible, so I go legacy UI.

@IAmTimCorey Жыл бұрын

There aren't typically clearly-defined lines, which is why they often get blurred. At the end of the day, the company just wants the job done. What role you play in that isn't as consequential to them. It will be up to you to advocate for what is best for the process and for you as a developer.

@jesse4589 Жыл бұрын

Tim must have goofed up during editing this video. He let this part in. “PHP is a great back end language” 😂

@IAmTimCorey Жыл бұрын

lol. For as much as I love C#, I can acknowledge the greatness of other languages as well. PHP can do amazing things. The coolest thing, I think, is how easy it is to get a website developed that accesses a database using PHP. It only takes a few lines to wire a form up to a MySQL table and a few more to display that table back to another page. Without PHP, we wouldn't have Facebook, Wikipedia, WordPress, Drupal, Joomla, Magento, or Shopify. That's a pretty impressive list and there is a reason why so many big players have used PHP to build their web business.

@miyu545 Жыл бұрын

Just because you can use something to build something, doesn't mean you should.@@IAmTimCorey :)

@SpiritVector Жыл бұрын

It sounds like you may have experienced a lot of those situations of accidental dba.

@IAmTimCorey Жыл бұрын

I have. I was a consultant for years. I created a few of the problems myself, but I've seen even more problems caused by others that I had to help clean up.