Live data from Hacker News

Story: “It would be career limiting..."

doomedprojects.com

21–30 of 342 posts

Re: Story: “It would be career limiting..."

#21
post #10

At Sun Microsystems this notion was so common that there was a TLA for it: CLM = "career limiting move"

I don't think they have it at my company. Or maybe nobody was nice enough to tell me. That might explain being just a midlevel after 10 years and a masters...

Re: Story: “It would be career limiting..."

#22

I could never relate to people who care about their career, "success", getting ahead, or climbing the corporate ladder. For me virtually everything else in life has been more important, and careers/jobs were just a necessary evil because it's almost impossible to survive without money.

Once you have a family, debt, obligations it does matter. Health care too.

Re: Story: “It would be career limiting..."

#23
post #6

> we hadn’t even received all of the specifications from the customer that we would need to complete the project > And then one of them said “It would be career limiting if the client were to hear this.” > I’d met my responsibility to the company – and the company had threatened me as a result. The author interprets that they were threatened. But really, for whom would it be career limiting? Perhaps I'm being too cha…

If you are a manager, and you make this type of remark, do not get it twisted. You have made a threat, and you have created an adversarial situation that limits your report's ability to trust you. You've telegraphed to them that you're willing to throw them under the bus, and they will remember.

If it doesn't feel like you're making a threat - it may feel to you like you're genuinely giving advice - then you have not really understood what it means to be a manager and what sort of power you have over your reports. Try to think of things from their perspective and imagine this coming from your boss.

Re: Story: “It would be career limiting..."

#24
post #12

Ah, that freeing feeling. I had that once. I was a new security champion for a team. The product had schema owner SQL injection vulnerabilities on every page we developed. I had a meeting with the department head and explained the whole situation and two remediation options. He chose the third option - do nothing. According to him we have a realtime DB backup. Has it ever been tested? No. Do you have procedures for i…

As long as you have it documented in an email ( issue plus proposed remediation ), you are good. You did your part. Sometimes it is best just to slowly walk away like you did.

Re: Story: “It would be career limiting..."

#25
post #18

Earlier quoted context omitted.

Some people thrive on their work and on problem solving. Not every employer is this malicious or incompetent. Given the necessity of work, I would rather enjoy my work and excel at it than sluff off.

"Given the necessity of work, I would rather enjoy my work and excel at it than sluff off." True, but from my perspective the career oriented people don't actually care about that stuff or solving problems. In my mind, the people I would label as career oriented are usually pretentious assholes preoccupied by the "status" of someday being in the C suite and driving the most expensive BMW/Tesla. On the other side, you…

I'm not sure I'd label every staff+ engineer at FAANG as a pretentious assholes.

Re: Story: “It would be career limiting..."

#26
post #12

Ah, that freeing feeling. I had that once. I was a new security champion for a team. The product had schema owner SQL injection vulnerabilities on every page we developed. I had a meeting with the department head and explained the whole situation and two remediation options. He chose the third option - do nothing. According to him we have a realtime DB backup. Has it ever been tested? No. Do you have procedures for i…

I'm not sure what's more depressing, that they didn't think that someone exfiltrating the data was an issue as long as they didn't lose it, or the fact that even if customer data was stolen, they probably were correct that there wouldn't be any ramifications for the negligence.

Re: Story: “It would be career limiting..."

#27

"200+ person project" being contracted. I can't imagine any successful big software (assuming) projects like this not done in-house. Anyone seen any?

It's on one side of the bell curve but still a reasonably common size in ERP space. Not all of those projects are successful, but not all of them are failures either.

(FWIW, my 2 cents - ERP project can succeed or fail on many key levers, including the approach (are we taking it as the business-transformation project that it is, or trying to treat it as a simple IT project); having a suitable client champion and involved/engaged/competent client team; clear goals, priorities and business requirements; explicit responsibilities and deliverables; and of course the competence & experience of the implementation/system integrator - not just on the development side, but on the functional, business transformation, project management, and most important client relationship management side.)

Re: Story: “It would be career limiting..."

#28

"200+ person project" being contracted. I can't imagine any successful big software (assuming) projects like this not done in-house. Anyone seen any?

Oh yeah. The product I worked on in the past went this way. We had a mature product that I said we probably needed to rewrite and modernize to handle any additional increase in volume or integrations with other systems. I left the team due to mostly politics. A year later, half my old subdivision was laid off and the project went to a contractor.

Funny enough, they're about 2 years behind schedule.

At least they took my advice about modernizing...

Re: Story: “It would be career limiting..."

#30
> (c) we hadn’t even received all of the specifications from the customer that we would need to complete the project.

To me that smells of incompetence on both the customer and local company. At that point the project might be entirely unsalvageable.

Post reply on HN