Related Posts
Am I the only one who is happy I got into IT?
Hi fishes, I'm having below 2 offers. I'm little bit confused. Can you help me to choose one. Factors : career growth, work life balance. YOE : 2.7 yrs 1.Shell - Senior process data engineer (11+ 2L(variable) + 2.3L joining bonus (1 year) ) 2.Tiger Analytics - data science - python developer (14L fixed + 1L(2 year clause)) Shell Tiger Analytics
More Posts
Conversation Starter
Rising Star
Hey guys,
I got selected to HCL Technologies , had submitted my documents and all the required information also updated my joining form in discover HCl website. It also shows that my bgv is completed but I have'nt recieved myoffer letter it has been more than a week. I also have a service agreement to fill it requires my date of joining which I think will be in my offer letter. Can any one help me and say how will this move from now.
Fly day miracle! Exit row to myself!! 🎉🎉
Additional Posts in Software Engineering
Anyone have experience working CWX side of Facebook (Meta) ? These are the full time contract roles that potentially turn into permanent roles directly with Facebook (Meta). Had a recruiter reach out and offering me comparable TC and such, just curious if anyone has experience in these roles and success/failure of transitioning into permanent role. Thanks in advance!
New to Fishbowl?
unlock all discussions on Fishbowl.
Do full stack
There's no reason to not learn both
You don't need to be world class at both, but you'd be better at either if you knew both
Imagine a sandwich.
The front end is like the bread and toppings. It's what you see and touch. It's the part of the website or app that you interact with.
The back end is like the filling. It's what's inside, working hard to make the sandwich tasty. It's the part of the website or app that you can't see, but it's important for making everything work.
Full stack is like making the whole sandwich. It means you can do both the front end and the back end.
Which is more lucrative?
Full stack is often considered more lucrative because you can do more jobs.
Which has a better work-life balance?
Front end might have a slightly better work-life balance because it's often more focused on the visual aspects.
Which is harder/easier to learn?
All three have their own challenges. Some people find front end easier because it's more visual, while others find back end easier because it's more logical. Full stack is the hardest because you have to learn both.
Remember: The best choice for you depends on what you like to do and what you're good at. It's important to have fun while learning!
It’s like building a building. Front end, you can build the exterior, walls, what it looks like, etc. Back end, you’re worried about shipping lanes (api calls), how the trash gets taken out, the AC lines, etc. For website context, front end will be the user interface, the buttons you click, how things look on the page, etc. It separates at the api call when you actually click something. From there, it talks to the server. Now you’re in the backend. Then you’re focused on the processing, writing to the database, integrating with other parts of the website, etc. Full stack can do both, but usually the knowledge is less-deep than someone who specializes.
Pro
Full stack usually is more about money, as in the company can't afford to hire specializations and instead they ask one person to do all the jobs.
This might be great for the right person. It works out well if you like variety and doing a little bit of everything. Usually people are stronger in either the data and algorithms part (backend engineers) or the presentation part (front end) and they are just sort of ok in the other part.
Frontend makes the pretty
Backend makes the data
Full stack is the everything
Now go to bed!
Titles in the software development industry are meaningless. Even with that title one will know what you do because there are so .any variations in technology. The biggest benefit in titles to me is sociological. It's a negative tell if someone in the industry is caught up on titles. They haven't figured it out yet.
Hello! I did a bootcamp myself more than a year ago and it worked out well for me! I landed a job as a full stack developer, mostly doing backend. I work at a smaller company, so we don’t really have “front end developers” or “back end developer”. Everyone is full stack.
In larger companies, which you’re unlikely (not impossible but much harder to break into a larger company without experience or CS degree) to end up at for your first developer job, they separate development teams. Most devs I know from bootcamps ended up at smaller companies where they’re obligated to do full stack. I think once you get your first job and get some experience then you can think about specializing. They both result in similar pay. Front end is more creative and back end feels more technical, but they’re both hard in their own ways.
To be a front end developer or backend developer, you have to learn how to do the opposite side so you understand how to implement the backend into your front end or Vice versa. So really if you end up becoming a developer, you’re going to end up learning both, you’ll probably prefer one over the other and can specialize in it later on in your career. Good luck!
It was a bootcamp local to my city. It wasn’t one of the national ones.
full stack often means 2 FTEs of work.
Very simplified: front-end is building what the users see and use. back-end is building what the application does. And full-stack is building both.
Traditionally, full-stack developers have slightly higher salaries, but that's because they have to know both front and back end coding.
And work life balance is an attribute between you and the company you work for, not the type of developer you are.
That is the thought, but with frameworks (like React). I find some developers really don't know the underling technology (like Javascript). They then over inflate the skill set of the framework because they run into issues in which the framework doesn't do well.
If you ever what to make a React developer ghost white, have a javascript developer ask him why they use React. The answer is because that's what the job posting ask for however nobody is evaluating the need, so if you ask they don't know
Idk big dog just do whatever you want