News for hackers. Stuff that matters.

cmp0

Re:Jeffrey Snover: "Welcome to the Room" on Saturday February 07, 2026 @05:22PM (#46928779)
> Risk is much more tolerable in the last mile than the first one

Is that objectively true? I think you could also make the argument the other way that things compound when you innovate at the root.

I think it's your opinion that that's the case, and it generally makes sense to me as well, but I'm still saying it's a judgement call.

There are a lot of things / decisions at a company that don't strictly matter for the customer immediately but they still eventually matter for the customer - because they have a downstream impact. In this case, maybe you save that money and spend it somewhere else.

Re:Jeffrey Snover: "Welcome to the Room" on Saturday February 07, 2026 @10:26AM (#46924596)
Surprised by the hate here, I thought this was great.

Microsoft (and anyone's) success is probably a function of strategy + execution + luck.

So I think it's hard to solely judge this philosophy by Microsoft's success or not.

He's basically saying: "You must take calculated, strategic risks. But don't be wrong too much."

What's a better strategy?

Re:Jeffrey Snover: "Welcome to the Room" on Saturday February 07, 2026 @10:11AM (#46924478)
You make a good point I think the blog post still works.

"The real estate team should not be a risk center." - Why not? Sure, I agree with you it doesn't make a ton of sense _to me_ to fire 90% of the janitors.

Satya said he wants his team to be "Intellectually honest".

I'd argue that a plan to fire 90% of the janitors today is not that realistic, but if some real estate exec thinks they honestly have a plan that could be successful, are tracking data, and change their plan if they're wrong - what's the problem?

Maybe they're crazy enough to have figured something out we don't know....or not in which case Satya says you'll be gone if you make it a habit.

Re:BeeWare – The IDEs of Python on Thursday May 28, 2015 @01:39PM (#9619754)
If you're looking for a PyCharm color scheme that's close to Sublime, check out:

https://github.com/mekwall/obsidian-color-scheme

I agree that the switching costs aren't technical. Maybe for small teams in a startup it's easy to relearn a new product, but don't underestimate the stickiness with large groups of people all using and relying on it. Just think about how many large (& small) organizations still use email even though it's terrible for intra company communication.
Sounds like an R* tree or some variant of that?