331–340 of 464 posts
Or tell them to smarten the fuck up, and tell them your team works in Agile, or whatever your project management scheme was at the startup. They bough you for a reason, probably because you guys did something they couldn't, don't be afraid to remind them.
Tell me you never ran a large code base in production, without telling me. Past a certain point there are no "simple code changes" anymore. Automation and functional QA needs to ensure zero regressions, internal and external docs need to be considered, it all needs to be bundled in with many other code changes (feature and fixes), etc. There is no shortcut. Even FB had to dial back their "break shit in prod" mantra.…
You're presenting one way of running, "a large code base in production" as if it's the only way. It's not. The other way is to deploy frequently, accept some amount of bugginess, and build your systems to deal with it appropriately. Running and maintaining a large code base is not the huge technical challenge it once was, but unfortunately the relics of the past remain, and force everyone to do things their way, lest…
> So I reach out to the manager and ask what is going on. This is a simple task, I said. Why does it take an entire quarter for your team to deliver? He doesn't have an answer. Your simple task, which you think would only take a few days to implement, is probably one request in a long queue of requests that team is dealing with. That means they won't be able to start on it for a long time. That team probably set up t…
Echoing other comments, your company was acquired. The way you're used to doing things sounds like it's quite different from how the new owners do things. I can't make any sort of judgment call on which is or isn't "better" based on a brief HN post, but I think it's worth keeping in mind that it pays to be adaptable and to scout out the post-acquisition lay of the land before you let it affect you too much. You don't…
Look around and see where your former leaders are now? Are they gone or in positions of power? If no BIGCORP employees are reporting to them then you know the writing is on the wall.
Leave.
Earlier quoted context omitted.
> Take this as a learning experience: don't assume that you are at a startup where people will drop everything to handle a request from you right away. This doesn't explain why they wouldn't accept the offer of work from /u/lopkeny12ko. I've been in the same situation multiple times. Sometimes I've been allowed to do the work and sometimes not. In the cases where I was allowed to do the work, I certainly took longer…
Away team work is standard at Amazon. Of course you still may have to go to office hours and sign up for busy teams.
Earlier quoted context omitted.
Yeah that story is total bullshit. It's someone's fantasy. The equivalent of me telling the story of my epic comeback in the Superbowl.
I can buy the part about putting up fences between business people at the tech team. Been there, done that, modernized project management. But the "thank you"s, bonuses and all that? Complete fantasy. :)
This is honestly basic management technique. It is called the "Auntie/Uncle" problem.
I did some work for a Large Company. One Monday I try and log in, and my hyper-secure laptop won't let me do anything. Try a few more times and then call my immediate manager, wondering if they've let me go or something. Nope, they're aware of the glitch and are working on it. I hang out and wait. Call again before lunch. Nothing. Still nothing at the end of the day. I call again the next morning. "Still working on i…
Mid-size companies are where it's at. The huge ones (1k+ employees) are way too big and unwieldy and you'll get lost in the bureaucracy and get fed up with all the people promoted based on the Peter Principle. Good stuff if you want a peaceful-ish place to work at, maybe you have small kids at home and just want to work 9-5 and bring zero work home. In small ones (dozens) you tend to become the smartest person in the…