nikanj

37 ms·

751.
by nikanj 4y ago
What you’re describing is the first step of enshittification ( https://pluralistic.net/2023/01/21/potemkin-ai/#hey-guys )
752.
by nikanj 4y ago
This would never pass the code review today. "Why are you optimizing this?" "Why use a magic constant?" "Optimization is evil!"
753.
by nikanj 4y ago
It’s always DNS
754.
by nikanj 4y ago
Time to crank the monetizing tap, add a mandatory monthly subscription to everything and deprecate well-working gear
755.
by nikanj 4y ago
We picked Bitbucket instead of Github many years ago, basically because the person setting up the repos already knew Jira I’ve been very happy about that past decision lately, Bitbucket is just…boring. It works, rarely gets in the way, and
756.
by nikanj 4y ago
The sane solution: ban massive cars, give exemptions to people with true professional needs The ’murica solution: get an even bigger truck yourself, so the other party sustains most of the damage
757.
by nikanj 4y ago
If a production environment gets contaminated, they just take the whole product behind the barn.
758.
by nikanj 4y ago
If I had to guess: because fuck you, that’s why. They don’t care, because they know you’ll be back regardless of the price
759.
by nikanj 4y ago
Not to defend Microsoft, but isn’t everyone?
760.
by nikanj 4y ago
I’d rather be seriously injured than killed, yes. I think most people would pick the same. If you observe the rush hour traffic for an hour, how many of those people have broken legs, severe disabilities or a debilitating case of elderly? T
761.
by nikanj 4y ago
I don’t know lots about physics, but I’d much rather be hit by a 40lbs bike going 12mph than a 5000lbs truck going 45mph
762.
by nikanj 4y ago
My biggest shock: they included trucks. For the past many years, the restrictions on cars have been tightening, but everyone drives a truck that’s exempt from the requirements
763.
by nikanj 4y ago
The same reason Brother has not beat HP in the printer market, despite the latter having scores of customer-hostile policies w.r.t ink DRM.
764.
by nikanj 4y ago
Called it, the issue is fixed and the decision wasn’t final after all https://twitter.com/craig1black/status/1645822291497062402
765.
by nikanj 4y ago
It's final unless you know someone who works inside the company, or manage to catch enough traction on some news site to catch the attention of someone who works there
766.
by nikanj 4y ago
Fortunately he was able to reach the real Google customer service (HN front page) and this issue will be fixed quite promptly.
767.
by nikanj 4y ago
This writing sounds like stuff from James Mickens ( https://mickens.seas.harvard.edu/wisdom-james-mickens )
768.
by nikanj 4y ago
I haven’t been this shocked and surprised since the sun rose from the east this morning. What a completely unexpected, massive plot twist
769.
by nikanj 4y ago
I think the most convenient way is the metric system. You had 1.5 desiliters of milk and 4 desiliters of sugar, but want to a half batch instead? Must be 0.75dl and 2 dl then
770.
by nikanj 4y ago
Pool should be mandatory part of Y Combinator. Really teaches you that ideas are worth jack all, and solid reliable execution wins the game every time
771.
by nikanj 4y ago
It’s interesting how well cryptos have adapted to monetizing stolen aws credentials.
772.
by nikanj 4y ago
Because once a corporation grows larger than some singularity threshold, there seems to be a bug event horizon where all bug reports just disappear. Send a bug report to a five-person software company, their lead dev contacts you the same
773.
by nikanj 4y ago
The biggest surprise for me was Microsoft actually fixing it.
774.
by nikanj 4y ago
Remember when people paid good money for Second Life real estate?
775.
by nikanj 4y ago
Every investment fund is under strict orders to plow money into AI, because it's going to change the world
776.
by nikanj 4y ago
It's the model familiar from previous bubble rounds: 1) Get funding 2) Put a lot of effort into appearances and presence 3) Get acquihired by Google / Microsoft / et al.
777.
by nikanj 4y ago
”There’s a bug, so we should rewrite the entire thing”
778.
by nikanj 4y ago
I’m mostly impressed how shite the ”webscale” codebase is, if everything bursts to flame the moment the programmers stop babying it. Considering how many man-hours they’ve poured into the product, you’d think it would be somewhat bug free
779.
by nikanj 4y ago
There are compromises like ”do not pass everything around as JSON” that swamp any language. The cost of constant re-parsing really adds up
780.
by nikanj 4y ago
The dogma for the past few decades has been that one is supposed to wholly ignore all performance concerns, and then try to slap some profiling-guided lipstick on the pig at the very end of the development process. You can’t hot loop optimi

More ›