4 ms·
"In software this would be the equivalent of just writing components or html for an extended period of time without any variety, which is soulcrushing." I actu
by giantg2 5y ago
"In software this would be the equivalent of just writing components or html for an extended period of time without any variety, which is soulcrushing."
I actually want less variety. I never get consistent work. How can I be an expert if I don't have a steady type of work. I'm really struggling right now. A lot of that is because I know that anything I learn at work will be used once and then thrown away. What's the point of learning it at all?
For example, right now they want me to learn AWS Step Functions to automate our regression testing. The first thought I had was "there's nothing else I can see us using this for on our team". My second thought was "how will this work when the test data constantly changes and the tester's time is dominated by troubleshooting issues, mostly data issues".
I want strategy I can believe in and a role that allows me to grow into a respected expert. My only option is to switch jobs which is depressing (not a lot of good stuff out there for me based on my past). It sounds like this is anyone's best option when the underlying issue is dissatisfaction with the work.
- iheartlife 5y agoYou could try to become a respected expert in learning then? There is a lot of use for people who can pick up XYZ in a timely manner. Especially in software where the world moves so fast (unless you do C or similar) that yesteryears knowledge is outdated this year.
- rraihansaputra 5y agoPersonally I think the kind of work I do rewards learning things/executing things fast. I take extended periods of doing the same things as a.. bonus? Things will always change, and in FE development I feel like it's all integration. Which is fine for me, and what I want to sharpen is to be quick and have a feel of what kind of integration does the business/story/ticket needs. Balancing that with maintainability and teamwork is what's interesting. The programming part is only a tool for me. I'm happy that I get paid to solve problems mainly with my programming/abstract thinking skills instead of managing skills or negotiation skills; not programming itself.
- giantg2 5y agoBut it's usually not respected. You end up like me - an intermediate developer who is willing to pick up the shit tasks that nobody else wants. The only thing that will help get to higher compensation or a senior role is to become an expert to the point where you can leave and get a job almost anywhere. Stuff like FileNet, Neoxam, ASC, etc doesn't have a market. It's a necessary and important role for the company, but nobody wants to do them and very few people use them (or procedures for ASC vary too much).
- csharpminor 5y agoThat’s a tough position. I felt the same pressures when I was an SWE. The way I solved it was to go into sales engineering, and overall it was a great career choice. My product is pretty technical so there are enough challenges to keep it interesting. But at the same time I’m always playing on home turf. I’m (usually) well respected by customers because of the reputation I’ve developed for my expertise. I’ll spend 10-20 hours each quarter per major customer to unblock their team / launch a project. For me it’s more rewarding than closing endless JIRAs. My base compensation is less than the equivalent SWE level, but with bonuses my take home ranges from being on-par to significantly more. It comes with the intangible benefit of developing a much broader professional network. Your mileage may vary. I consider myself extremely lucky and have no illusions about sales being a cakewalk. But if you’re looking for a way to find routine, going to into technical sales with a product you respect might be a good route.
- giantg2 5y agoI haven't seen many sales engineer positions around here (PA), any my wife won't move. It sounds like it would be right up my alley. I imagine the ability to quickly grasp the concepts and thi k about it from a systems and cost/benefit approach would be useful (stuff I tend to do well with). And it sounds like the minor technical details aren't too important because you have the dev team to fall back on.
- TehShrike 5y agoI think fondly of the two summers I spent mowing and wheedwhacking. There was a skill curve, I practiced and got better, and then got to ride that peak for a while.
- giantg2 5y agoI've been in software 9 years. My peak was 4 years ago. It's all downhill from here.
- coliveira 5y agoThe sad reality is that programming as we knew years ago is going into extinction. The only thing that remains is to work as library integrator and debugger for X, where X is something that is popular this week. All interesting software development left is in open source, and SEs are now just required to integrate existing libraries into a GUI done by somebody else, or a server side component that talks to that GUI. With AI coming into the picture fast, the prospects are even worse.
- isatty 5y agoThis is not true at all. Software engineering is about solving problems. Are you not solving problems with existing libraries?
- gyulai 5y agoYou have to be extremely senior these days to be in a position where they actually let you solve problems of any kind. (The paradox is: At that level of seniority, you are no longer capable of actually seeing the problems). I'm a software engineer with a Ph.D. from an elite university and 10 years experience. For me it has consistently gone like this for the past 10 years, and that was in a huge variety of different companies: Manager: We need to add field X from data source Y to interface Z. Please do that for us. Me: This will take 93 days. Manager: That's perfectly fine. Me: The reason it will take 93 days instead of 3 days is that your whole architecture is a pile of shit because of problem A, problem B, and problem C. Fortunately for you, I happen to be someone who is capable of seeing and solving problems. So here is what I'd like to do for you instead: I'll use 30 days to solve problem A, 30 days to solve problem B, 30 days to solve problem C, and, with those problems solved, 3 days to add field X from data source Y to interface Z. Your spending is the same, plus it's an investment in your software architecture that will pay dividends, because there's a good chance that next week you'll want to add field V from data source W to interface Z, and solving those problems, that too will then be a 3-day project instead of a 93-day project. Manager: Wow, you are great at identifying and solving problems. I'm glad I hired someone who is such a great problem solver. But please don't do any of that. We just need you to add field X from data source Y to interface Z without touching any of the things you just said you'd like to fix. Me: But it will take 93 days, and you are paying me a shit-ton of money, don't you care about that money and how it's put to use? Manager: We have enough money to not give a shit about the money we give to you, and part of the reason we are giving it to you is so I don't have to expend my mental effort evaluating proposals like the one you just made. So, please just do as you're told. Me: Okay. sound of soul crushing