I suggest channeling your ambition into your own projects, hobbies, and interests. If I'd spent more time making my own game engine rather than working on theirs, I'd still have it today.
It’s been 7 months so far and throughout the first 6 months, I have fought and resisted how BigCo operates—it left me tired and even more miserable. Within the last month however, I have stumbled across the same advice as has been given by the wise members above. This advice is invaluable, accept that within these organisations a lot is outside of your control. Rather, focus on projects, learning and hobbies outside of your work that bring you joy.
If your feelings remain unchanged within a couple of months to a year then consider making a change to another Co. Good or bad, these experiences are invaluable in helping us to decide on how we wish to pursue our careers.
Nobody in my family ever made more than $10/hr growing up. I turned out okay. I think. :)
Make sure there's not a golden path that you're missing? Or that your reasons for departing from it are really insurmountable?
everything is a ticket
ssl is expiring,
- make a ticket for the customer,
- request a quotation,
- wait for approval,
- finally issue the cert manually,
- finally deploy it (manually, using some tool of course)
shock horror maybe they might actually ... get more done and therefore need more stuff :D
Sound advice.
The HN community (rightly) skews towards entrepreneur hackers who have a general distain for BigCo employment.
I love this quote from Prof G on joining BigCo:
https://youtu.be/ffDVe-NgFt4?t=662
You're going to have access to what is the greatest wealth generator in history and its called the US Corporation.
On a risk adjusted basis, you're better off working at a Big Corporation
On the contrary, I find that most work at bigco or smaller companies and come to HN to play out their dreams of what it would be like to take the risks that people with lots of wealth can make freely
Look at the lifers at BigCo, and how they roll with it. They choose their battles carefully, they don't fight the system. They are good colleagues, and they are paid well for their long service. They also go home on time!
I'd say do a couple of things -
a) Provide constructive recommendations on the specific friction points. Sometimes, especially coming from a small company background, you fail to realize the need for a process or review. It doesn't mean it can't be improved but resist the immediate urge to hate it.
b) Plan ahead. Once you get familiar with how the processes work, set aside time to raise request before you actually need the resource. I was terrible at this and it came to bite me many times. Anticipate and plan ahead.
I would never hire someone again if they have worked at a bank for more than a couple of years.
This is an interesting perspective but perhaps crosses the line.
After a release, there was a very short period of watchfulness where issues found in production would either be marked as "minor" (this will hold until the next release and the users be damned) or "major" and the entire system would be rolled back (for now). So every release had a bunch of awful bugs that drive users insane. They'd complain, of course, but the senior brass would just disperse "release notes" via fax to the branches and tell them how to work around issues. In other words "button it". So the users wouldn't create incident tickets.
Fast forward a few weeks, you're bored because you're waiting for project approval, so you make use of the incident process to make some improvements. Perhaps it crosses a line. But I had some direct managers (lower rungs) who loved the idea. "Fuck it", they'd say, "the process is there, use it!"
All that from taking the ITIL course seriously. If you're going to hack the system, understand it
The bank I was at had the best data practices of any company I’ve worked at by a mile. They wouldn’t hesitate to write huge checks to make sure that the hardware systems and teams supporting those systems were perfect. Software management was a bit procedural but the results were consistent and high quality.
The friction is there to protect the firm.
It's true, though, that upper leadership tends to be incompetent. Don't hire them.
But finance tech VPs and ExecDirs are often highly skilled, smart people.
Navigating the regulatory landscape to introduce change is high skill and art that I've rarely seen but does exist.
Sometimes you work on some cool project for a while, then it becomes boring, etc. Or sometimes you're stuck with that job because of lack of other local opportunities. Or whatever other reason.
(I never worked in a bank myself.)
I had a huge amount of freedom, really. But after a bit over a decade I finally moved to the world of startups. I’d never go back.
So while you can definitely work on removing your own personal frictions, and it’s absolutely worth selectively breaking the rules, I’m not sure you’ll ever be as happy as you could be in a different environment if that’s how you feel now.
Yeah, I agree with this. My strategy has been to figure out what my boss wants to do, figure out what I want to do, and figure out what my job duties actually are. Then focus on the intersection of the first two and doing the minimal work necessary for the third. This means trying to get around process for your boss's pet project or to work on what you want while making your internal customers go through as many hoops as your organizational structure allows when they want you to do your job duties.
This probably comes off a bit cynical and I do have some pride in doing a good job, but this is kind of my basic corporate strategy.
Especially if you are already doing a good job at what you want to be doing and keeping someone senior happy, it’s often possible and sometimes even surprisingly easy to evolve your official/main duties in that direction too.
Thing big and slow, and you’ll work it all out.
The complexities of both running a large operation and operating globally are vastly greater than a small operation. Simply the number of nodes that must communicate has a combinatorial explosion. So, there needs to be a standard way of dealing with that, or entropy also explodes. So, bureaucracy happens, with processes that sorta fit everyone but rarely exactly fit, so friction increases.
A saying I heard from Africa: "If you want to go fast, go alone, if you want to go far, go together". GP is going far and together, and yes the other people will necessarily slow you down vs going alone.
The decision is whether one really wants this journey, in which case, learn how to work within the large org, or actually wants the faster but less secure career.
Love this! Definitely gonna use this sometime.
I work for a very small "non-tech" company, have been here 12 years, and have a great income. The tradeoff I had to make was a much higher level of responsibility. (I'm at the very top of the tech stack - if something isn't working, there's no one for me to blame, aside from a vendor like AWS)
Relatedly, best advice I received was that the grass is green and brown on both sides.
*standard disclaimers about at-will employment
One answer is to accept the way things are at BigCo and to just coast along in your role, which is not necessarily a bad thing.
Another answer is to work at an early-stage startup or a small non-tech company where you can move fast. The tradeoff there is lack of job security and lesser pay.
Don't ever expect to move fast at BigCo. It's a BigCo for a reason. By moving fast, you could upset the cash cow, hence the friction placed in front of you. But this can work in your favor. Excellence will not be expected of you at BigCo, and if anyone complains about why nothing is getting done, you just repeat exactly why. As long as the company is making money and you haven't made any enemies, the chances of you getting fired are slim to none.
IMO, you have to look at the big picture. If you ignore the friction factor, is life at BigCo so bad? Are your hours reasonable? Do you like your coworkers? Good pay? Learning to let go your frustration with how you think the company should be run may be the most favorable choice. Remember, all jobs suck, more or less. A year after you change companies, you will find things to hate about that one as well.