This is often the advice given by senior folks and I think it is somewhat similar to say that you have to "lie a bit on your CV". Still, I always wonder what would I do if I make these big promises to clients/bosses/management and I fail to deliver. Wouldn't that be worse than having said "no, I won't be able to make it in time" from the beginning?
For context, I'm early in my career (3 YOE) and I don't deal with management that much yet (I'm still shielded by my tech lead and PM), so I'm always looking for advice on how to navigate these things. I really can't just say "YES, YES, YES" when I know *very well* that something won't be possible.
One hedge I always used to make was, "I think we have all the information we need for now. We'll get you an estimate within 3 business days."
And then I'd sit down and bust my ass trying to find out if it was feasible or not. :)
If it wasn't, we could always come back with a lesser approach and people seemed to be happy with that. ("It turns out Android doesn't widely support [feature x] so we recommend [feature y] instead.")
Exactly this. I'm in a situation where I have to tell a customer that we won't be able to do the thing that I've spent a long time investigating.
My answer won't be "no, we can't do it." It'll be a form of "we have to use this alternate method to get to the goal, how does that affect your budget?"
Well said, and on the flip side the strongest signal that your management sucks is their absurd sense of entitlement and inability to handle "no" correctly. Their lack of curiosity and ambition will cause the business to miss out on so many opportunities.
A naive junior shouldn't stump them, but it really does happen all the time. If all they have to do is ask what it takes to flip it to a "yes", the same information is communicated. The only thing ever truly at stake was someone's ego.
Nonsense. The client that made me a job offer as CTO listed the fact that I wasn’t afraid of saying ‘no’ to unreasonable requests or unrealistic deadlines one of the things he valued the most in my work. He had plenty of experience with contractors that would always say yes, promise anything and then find themselves unable to deliver because they underestimated the complexity of the task.
Saying no is what makes a professional so valuable. Of course you always want to offer alternative approaches.
While there are certainly people who are rich enough and spoiled enough that they have probably never been meaningfully refused anything in their lives, that produces terrible people, and absolutely everyone needs to learn how to accept being told "no" when "no" is the correct answer (or a reasonable one).
One trick I learned: If you have the type of manager who doesn't like "No", then say "Yes", but continually keep him in the loop as the project progresses to failure.
If you're up front honest, they'll think you're being lazy - even if you have good reasons.
If you say "Yes", and then fail for all those reasons while providing regular reports, the manager views you as "Someone who is willing to do things".
They often don't care about your actual success/failure rate, but instead use your attitude as a proxy for the actual success/failure rate.
Also, as the project is moving to failure, he'll usually intercept with "OK, how about we changed the requirements to ...?"
If you asked for that change in the beginning, the same rationale as the above applies.
Internally, it’s important to understand that every ask should have a business goal associated with it. The thing being asked for is rarely (never?) the only way to accomplish that goal.
Great engineers focus on the customer or business need and find/propose alternatives that are possible.
> and I think it is somewhat similar to say that you have to "lie a bit on your CV". [...] For context, I'm early in my career (3 YOE)
Please consider this input from my YOE battle scars:
1. Don't contradict your team while in a meeting with outsiders, but then you're obligated to follow up with your team offline, to try to mitigate any damage, and try to make sure it doesn't keep happening. For one example of why, I've seen one person consciously "mis-promise" things to customer, and when I talked with them offline about we couldn't be saying that, because it wasn't true, their response was "they won't remember". Narrator: "They did remember." And that's possibly why that person and a few others aren't very wealthy today.
2. Not everyone believes in "lie a bit on your CV" nor similar dishonesty. You'll probably meet colleagues, who you respect, who react to that with surprise and disappointment. You could also get fired for it, with cause. Especially if you're calling yourself an engineer, since determining and telling the truth is much of your job.
3. Though, on the other side of CV honesty, be careful about always using team-speak/think when in an interview context. Out of habit, you might naturally say "we" when talking about something you were instrumental in. But some people who think lots of people lie on their CV are going to hear that "we" as you generously including yourself in the accomplishments of others. I've started switching modes a little more for interviews, expressly claiming more credit, such as by saying unambiguously when I was the sole designer and implementer of something.
It took me years to notice that folks who confidently made stuff up or provided incorrect info in meetings were looked upon favorably. No one ever knew or cared that the thing the person said was incorrect. Just the confident way they said it.
Aside: start getting that exposure to management people now. You can book regular skip levels with your bosses boss and the PMs boss. Better than waiting until you get promoted and having to learn how to do it with a weight of expectation.
When everyone in a game is cheating, you will lose by playing fairly. And like other commenters have suggested - everyone expects similar behavior.
> For context, I'm early in my career (3 YOE) and I don't deal with management that much yet (I'm still shielded by my tech lead and PM), so I'm always looking for advice on how to navigate these things. I really can't just say "YES, YES, YES" when I know very well that something won't be possible.
It depends on a lot of things, like how big the company is, how critical the project, culture, management style, etc. - but you'd be surprised at what is actually possible that may sound impossible. I've had those "this is impossible" thoughts a lot early in my career and more often than not I was wrong. The few times I wasn't wrong, I made sure to highlight risks I saw at the outset, and when the risks materialized, point them out at the retrospective or whatever for CYA purposes.
The things you do want to avoid at all costs are death marches, impossible deadlines with consequences at the end of it, maintenance slogs which will tie you to a very annoying treadmill for your entire tenure - it's hard without experience to know where these things lie, but if all else fails, you can do what everyone else does, try the impossible thing, and either surprise yourself, or when it becomes clear it won't happen, toss it to some overly ambitious sucker (I don't condone this, I just have seen it happen far too often).
You need a minimum threshold of karma in order to downvote others on HN. Additionally, accounts with more well received activity are harder to identify as shills. That's why there are black markets where social media accounts are bought and sold and the price is typically proportional to the account's karma.
Currently working on my own education by learning C from Antirez's C course on YouTube.
I've been working as an ERP developer for a couple years now and the job is so dull and boring that I'm already starting to feel stagnant. So, I am learning more advanced things now in order to: 1. Advance my career, and 2. Maybe code some linux tool (for personal use only, for now!) and stop looking at enterprise code.
I just used “less” to read them, if I were to do it again I’d find something that at least kept my place on program close. I think I only accidentally closed it like once in that three months, but over time it would have been a problem worth solving.
As a migraine sufferer this sounds scary and only today I have learned about it. What was it like? If I may ask. Is there a way to prevent it? I googled it and it seems to appear rather arbitrarily and suddenly.
It's very rare. I was a migraine sufferer, but this is how that time it was different:
- I was under severe stress at work
- I woke up with aura, realised it when looking at the mirror, I had only one eye
- visual symptoms (aura) didn't go away after 1 hour. That's the limit where you MUST seek medical advice
- having "a migraine" that day raised my stress level... because work...
- symptoms persisted... and after getting better over a year, what was left became permanent (blind spot where the migraine started in my field of vision)
DO NOT take triptans during the aura. DO NOT take any vasoconstrictors during aura, since it's a phase where blood flow is restricted. That could have caused my stroke.
When a migraine hits, I take aspirin, stop all stressors, ALL stressors, try to calm down (I've used anxiolytics occasionally), breathe and rest. I'm often off for 2 days. It happens about once a year.
Again, migrainous infarcts are VERY rare. You'll be fine, just let the aura pass, and know to seek medical attention if it doesn't.
For context, I'm early in my career (3 YOE) and I don't deal with management that much yet (I'm still shielded by my tech lead and PM), so I'm always looking for advice on how to navigate these things. I really can't just say "YES, YES, YES" when I know *very well* that something won't be possible.
Maybe it is just a sign of being too junior?