2024 Presidential Election
Yesterday
243
Canceling debt isn’t inflationary or costing tax payers
Tech Industry
2d
9617
What happens when most of your team is Indian?
World Conflicts
10h
898
Why do Indians support Israel so much( on blind surprisingly) when Israel really thinks 💩of them ?
Today I Learned
Yesterday
1687
White male privilege is real
Ask Blinders
Yesterday
617
Everything seems great with this guy, except basic attraction. What to do? My friends say it’s no big deal
Let’s get this outta the way: TC: 98k YOE: <1 (3 months) I’m currently a “full-stack” SWE at Northrop Grumman. I’m not entirely sure a long-term career as a full-stack dev is a good choice. I don’t feel like I’m mastering any part of the stack. I feel okay at both BE and FE but not an expert on either. How do I know which one to choose? I find frontend state management to be a pain in the arse. I also don’t like CSS at all. I’m in awe and I admire the people that do amazing FE work however. I don’t think I dislike anything about the backend yet. How do I know which to choose? Is a fruitful career as a full-stack dev even realistic? Looking to leave NG soon and I want to make sure I choose the correct next job. #software #engineering #swe
I personally chose to work on backend because I liked it, and also because I felt the opportunity cost was greater otherwise (trying to get working experience on distributed systems at scale on your own is pretty much impossible, whereas I could always just spend a couple of weeks working with a JS framework and get something working). Ultimately, I would suggest you not make a pre-emptive decision so early (it’s only been 3 months, you’re not going to master anything yet), though it does sound like you already have some ideas on what you like or dislike. Give it some time, and then base your decision on what you feel works best for you.
Thanks for your genuine response. I know it’s really early and I might be overthinking it all. But blinders here say that the true decision makers and the best payed are those that are experts in a specific domain. With full stack it feels really hard to “master” it all. I guess I’ll give it more time.
I see where you’re going with this, perhaps you might be misunderstanding the advice from other blinders. It’s indeed true that often, highly paid jobs are niche roles that are very domain-specific (i.e autonomous vehicles are big now), but you’ll notice that the reason is simply because of demand and supply (a niche role has less supply, hence demand and TC increases). Optimizing between full-stack, backend and frontend stacks doesn’t really narrow down your domain, you’re effectively still a generalist software engineer, there are tons of other people in this role to compete with, so you’re unlikely to see the same niche TC that you’re hoping for. Early on in your career, you want to go broad and general first so that you have a wider view of the market, your skillset and preferences, and then slowly ease into specializing in any domain that you feel is appropriate. Really, my best advice to you is to not try to over-optimize for TC early on, and focus on growing your skillset first. When you’re a good engineer, the TC will always come to you.
BE for challenging work...FE for easier interviews and chill WLB
Ignorant statement
Too early to choose. Work with interesting and smart people and decide later (5+ years).
Where are you located getting that much in defense?
Los Angeles