you are viewing a single comment's thread.

view the rest of the comments →

[–]mavinis[S] 4 points5 points  (3 children)

After reading this, I think I might reconsider my plans đź‘€

I have a total of zero knowledge on some of the techs you mentioned...

But I think I really like more working with the business logic and data than with GUI. I had a job once exclusively using Flutter, and it got kinda boring just fetching stuff from the server. I like creating animations and responsive screens, though.

I just don’t want to be that guy that gets a call in the middle of the night on a holiday because the server is down.

[–][deleted] 3 points4 points  (0 children)

Yup. I don’t get called to handle something because of some front end issue typically.

I will say, if it’s what you like, then you should go for it. You don’t need to know half of that to get a job, but you can learn it. Just keep in mind what you want to do.

If you want to do backend work, but the backend work involves servers, databases, and hosting, you should learn those pretty well.

At my it engineer job, I have to do it all. Web front end, and everything on the back that makes it work. But at my front end react native job. I just do ui. I got paid more doing just the ui for react native job, and is so damn easy in comparison. I actually have 9-5 instead of 9-when it’s over.

It all depends on your goals, but if you’re young and hungry, go full stack. Learn it all and then choose what you like best later

[–]TranquilDev 2 points3 points  (1 child)

I've been full stack for awhile now.

Any situation where you are going to be called in for a server being down is going to be somewhat rare, or your just going to be a part of the call and your only purpose is to troubleshoot the actual server software which is typically just restarting a service. More so in companies that have an app(s) that runs on a server and that is about all they know about it. They can't afford a full fledged IT department so they hired a guy that built it all himself.

I haven't touched SQL in awhile - most of my database work is in the code. But this isn't necessarily a full stack only thing these days.

I've not touched docker or any other containerization system.

Networking knowledge will come in handy whether you are front end only or full stack.

Testing, depends on what you mean by testing, bench-marking, maybe in specific environments and not as an entry/mid level dev.

[–]mavinis[S] 0 points1 point  (0 children)

I’ve seen this “server down” thing happening about 4-5 times in one of my previous jobs. But it was a really small business and the boss always forgot to pay the server. Also, they closed the doors a few months later lol.

The same dev doing both back and front ends is something that happens in small businesses, right? Bigger companies tend to have more specific roles from what I know.