Live data from Hacker News

"No, it's less effort than that"

smartguess.is

371–380 of 388 posts

Re: "No, it's less effort than that"

#372
post #79

Earlier quoted context omitted.

What a weird thing to say. If you ask me how long it takes to grow a baby, and I say, 9 months. Am I not cooperating with the business when you want it in 6? No amount of effort on either your or my part is going to make the baby appear faster.

> Why do you need a baby? > Do you need to grow your own, or could you adopt? > Is it about birth itself? Does it have to be a human baby? > Does the baby need to be related to you? > What if we hire a baby actor? …

That's the best reply to the baby analogy i saw.

Thanks.

Re: "No, it's less effort than that"

#373
post #21

1975: Fred Brook's wrote[1]: “The bearing of a child takes nine months, no matter how many women are assigned.” Can't get better than this [1] https://en.wikipedia.org/wiki/The_Mythical_Man-Month

I have even smart managers look me in the eye and say things like "can we parallelize parts of this? let's map out the dependencies." EVERY EXTRA PERSON YOU ADD MAKES IT TAKE LONGER. The fastest delivery is a solo developer that you get out of their f**ing way and let them work.

If you want to go fast, go alone.

If you want to go far, go with people.

Re: "No, it's less effort than that"

#374
post #363

Earlier quoted context omitted.

If you’re not getting well-remunerated for your work at at FAANG or a startup that IPOs… you probably need to get some help finding or negotiating on your next job my dude.

> If you’re not getting well-remunerated for your work at at FAANG or a startup that IPOs… you probably need to get some help finding or negotiating on your next job my dude. Once again, you are missing the point of the last post which makes me suspect you are exactly the mediocre manager who gets complained about a lot. Let me guess, you hold weird ideas such as "If they don't do XX, YY, I will fire them" - never on…

Let me know if I can advise you on how to score comp you’re happy with on your next role!

Re: "No, it's less effort than that"

#375
post #370
post #365

Earlier quoted context omitted.

The dudes who respond to requests for estimates with sarcasm and cynicism get fired. I’ve fired them.

Maybe in some businesses. I suspect those business do less well than the ones that fire people like you instead.

I keep forgetting that HN skews more and more young every day.

Re: "No, it's less effort than that"

#376
post #364
post #362

Earlier quoted context omitted.

Internal competition can be good and bad, just like any other management principle. But at the end of the day, an organization needs consensus or it’ll implode, and some people are required to help build that consensus, amongst other duties that extend well beyond product. This is as true for business as it is in any other group dynamic.

You need consensus, sure. You don't time estimates from engineering estimates for it, and even if you did, badgering engineers to make their numbers smaller wouldn't make getting consensus any easier.

You do need estimates to unlock capital, plan budgets, plan for staffing. And badgering engineers to make their numbers smaller is often the result of engineers bullshitting their numbers, as I mentioned before. Engineering departments aren’t free from the same errors or fallacies or biases or mistakes that other humans make.

This is business 101 stuff.

Re: "No, it's less effort than that"

#377
post #374

Earlier quoted context omitted.

> If you’re not getting well-remunerated for your work at at FAANG or a startup that IPOs… you probably need to get some help finding or negotiating on your next job my dude. Once again, you are missing the point of the last post which makes me suspect you are exactly the mediocre manager who gets complained about a lot. Let me guess, you hold weird ideas such as "If they don't do XX, YY, I will fire them" - never on…

Let me know if I can advise you on how to score comp you’re happy with on your next role!

> Let me know if I can advise you on how to score comp you’re happy with on your next role!

I have already made my millions by working with sane ipo companies. At this point, I would much rather take advice from folks who prefer a good management structure. Please continue with your TC grind. Thanks for the offer though!

Re: "No, it's less effort than that"

#378
post #260

Typical action movie hacking scene: Leader: How long until you can hack the mainframe? Techie: The other hacker is really good; at least 2 hours. Leader: You have 1. Get it done! [commence flying around the 3d filesystem] Whenever I watch a scene like this, I mentally add a voiceover for the techie: [Techie thinks]: My actual estimate was 20 minutes. I can probably get it done in about 50, then I need to fly in the 3…

https://wiki.c2.com/?ScottyFactor

C2 has an article for everything!

Re: "No, it's less effort than that"

#379
post #374

Earlier quoted context omitted.

Let me know if I can advise you on how to score comp you’re happy with on your next role!

> Let me know if I can advise you on how to score comp you’re happy with on your next role! I have already made my millions by working with sane ipo companies. At this point, I would much rather take advice from folks who prefer a good management structure. Please continue with your TC grind. Thanks for the offer though!

Sure dude!

Re: "No, it's less effort than that"

#380
post #376
post #364

Earlier quoted context omitted.

You need consensus, sure. You don't time estimates from engineering estimates for it, and even if you did, badgering engineers to make their numbers smaller wouldn't make getting consensus any easier.

You do need estimates to unlock capital, plan budgets, plan for staffing. And badgering engineers to make their numbers smaller is often the result of engineers bullshitting their numbers, as I mentioned before. Engineering departments aren’t free from the same errors or fallacies or biases or mistakes that other humans make. This is business 101 stuff.

> You do need estimates to unlock capital, plan budgets, plan for staffing.

You might need some amount of estimation. You don't need a full schedule of every task, and producing one just in case is immensely wasteful. In my experience engineers are very happy to help answer questions like "should we be hiring more people for this project" when there is a real need and businesspeople trust enough to share that context.

> badgering engineers to make their numbers smaller is often the result of engineers bullshitting their numbers, as I mentioned before

Pretty sure the causation goes in the opposite direction. Most engineers are honest to a fault; the ones who pad their estimates are the ones who've spent too long working with crappy business people who do things like cutting time off estimates.

Post reply on HN