24
dUcKtYpEd
16d

Im kinda coming to this unfortunate realization that to improve in this line of work, you have to continue to make lateral moves. Every time I try to settle down with a company, theres always a spurt of work maybe for a year or so but ive often come on board near the later years of the platforms development and end up doing a bunch of clean up work. Clean up doesn't teach shit other then analyzing skills as your read over other peoples code for days on end, trying to root cause things.

I cant do this shit any longer. You can pay as much as you like, I cant. I have to be doing something that moves things along and expands my knowledge. I have to work with new tools, new paradigms, new ideas, new patterns. I cant sit around for years of my life just helping reduce churn on some old system.

At the same time I've got 4 kids, a mortgage, 2 cars and desperately need stability. Im going to try stressing again this week that im on an edge here and need to be moved elsewhere or given more chances. Ive been greenfielding with agencies for years. I did not join on to fix shitty angular 1.x code

Comments
  • 6
    Shit man, If I would have known about this I would have told you about a vacant position we have where I work :/ shit is closed now and we have a candidate pool. We start interviewing soon, ill let you know how that shit goes.
  • 3
    @AleCx04 slip the cv in the deck from the side? 🤭 did I say that out loud, my bad.

    Good luck @DuCkTyPed, hopefully you find something soon.
  • 2
    Have you looked into consultancy work? If you like Greenfield and find yourself looking for a new job after a year anyway, consultancy may be a better bet. You're usually employed to do a particular set of work, and generally you're paid more for it in a consultant position than you are in FT.
  • 2
    @AleCx04 I appreciate that. Honestly Id love to stay where im at, I just really. need to emphasize that Im bored out of my mind and need more purpose. I hear all the time from upper management "we need to be doing and shipping constantly" and yadayada about how devs should rotate teams and yet theres no executive action on it. Im about to take it into my own hands and apologize later if needed
  • 1
    @AlmondSauce Ive thought about it really. Just working full time, ive not liked how consultants have been treated and I still crave this form of stability even if i know i dont like staying put lol. I guess i dream of staying somewhere for 10 years but realistically I always jump ship after a year or so.
  • 1
    @dUcKtYpEd Yeah, it's not for everyone - just something worth considering if you find yourself moving that often.

    Greenfield dev is great, but in many ways it's a very natural cycle anyway - it doesn't stay greenfield forever, eventually the project is done and you're stuck in maintenance mode (or just cramming more features into it, which can get boring after a while.)

    The only way to really stay put for a long amount of time in greenfield dev is to either join a mammoth project that's going to take years to complete, or join a company that has mammoth amounts of greenfield projects they need doing, and you get to move onto the next one when you've done the current one. Those roles do exist, but they're rare.
  • 1
    @C0D4 wish i could :( its an electric process, I would've hooked the homie up
  • 2
    @dUcKtYpEd We sort of do a bunch of boring maintenance but do get to build our own tools and applications in whatever we want from time to time. There is glory in what we do since our stuff is used by a looooooooot of people and departments, but we don't do a lot of the cool hip flashy dev stuff that a lot of people do. Our work tho, stable, you would need to fuck up royally and beyond recognition to even get a write up, the pay is steady and good for the region. If stability is what you want of course.

    We in a different state than you, but its a state that loooooves Dolly Parton.
  • 1
    @AlmondSauce that second example you gave is actually what I’m in pursuit of. A company that is large enough but in mid growth where they still need dramatic roles involved to spearhead and have years of work ahead of them. I don’t have to lead the development of a companies core product but I just need to be doing enough where I feel like I’ve made progress at the end of the day and can measure my success in projects by the end of the year. Looking back on 2020 sucked. Well I resolved 75 tickets, 15 of which were requests for information and log analysis. It really sucks
  • 1
    @AleCx04 that sounds like a decent workplace honestly. I don’t mind maintenance. One can’t always be in stressful crunch time. There had to be transitional periods and down time but keeping someone in maintenance for a year is neglectful. No one should be stuck there
  • 1
    @dUcKtYpEd The alternative (which may be easier to find, and more stable) is that you find an established, large company in a "round two" of their tech stack. That means you're writing systems from the ground up to replace existing ones which are old, crappy, unmaintainable, expensive, etc. with modern replacements.

    The advantage of that is that the company is established and not going anywhere, and by the time they take on projects like this, they're going to be financially stable (otherwise they couldn't justify the investment.) This pretty much sums up what I'm doing - it's stable work, there's loads to do, there's no tight time constraints (the old systems still work after all, just badly), there's little to no budget constraints, and you still get to play with all the latest stuff. In our case we've pretty much got full autonomy over what tech stack / cloud provider we use as well.
Add Comment