HN user
"Your new models are great, but uh... How exactly am I supposed to use them?"
That is, given a lot of users' contexts, the way they can and the way they want to use these models are increasingly disjoint.
I believe it's much to do with blue light emitted by screens:
You've probably got a certain level of trust or delegated authority, but you want input and you're giving your leadership the opportunity to steer the decision if they feel they need to, and you're balancing that against the urgency of action.
By very direct analogy, I think there's a dictum in the US military to the effect that a bad plan executed quickly can be better than a perfect plan that's executed too late.
ETA: ... and you're potentially speeding the decision/action by giving leadership the opportunity to confirm/redirect on receipt of the email.
They literally gamified it? Amazing.
they are the most repairable.
That's a really weird way to spell "incumbency and network effects".
In fairness, you're not wrong, but that seems to be a very specific framing that hides a lot of what this whole discussion is about.
Yes, perhaps they do allow for greater flexibility, but that's complex and difficult to do well/reliably, and doing it well/reliably requires signal analysis gear and software modeling that's out of the reach of normal consumers.
I think your point about the loss of case generally stands, but surely the genitive isn't lost?
As opposed to relying solely on engine braking (or the EV equivalent thereof)?
I'd personally prefer a belt-and-suspenders approach.
If your server is Indian, they'll likely react positively, and get you what you want.
"I'm just asking questions!"
Probably for a number of reasons, starting from our desire as a society to ensure they are as broadly applied as possible, which is in turn driven by our desire as a society (read: "collective") to ensure that they're as effective as possible, which means driving for herd immunity and even things like permanent eradication.
For those who aren't aware of any "blanket liability immunity", I found https://www.hrsa.gov/vaccine-compensation/faq a useful starting point. I hadn't heard of such before.
Probably not in the way that you might mean it, but for me (Xoogler, 2010 - 2023) internalizing bazel means:
"Hey, where's your tool's code in $MONOREPO?" "<path/to/stuff>"
Cool:
g4d my-citc-client # moral equivalent to `cd ~/repos/stuff`
blaze run path/to/stuff:target
Wild to see the usenet/uuencoding model reproduced on the web w/ jpegs.
That's a feature, not a bug /s
Probably both, to respond to the risk tolerances of any given org.
... and the standard reply to this standard reply is "The market can remain irrational longer than you can remain solvent."
It's been interesting to review my portfolio, such as it is, against this situation, and see that I'm down relatively little. Not because I've bet against anything per se, but I made a conscious decision years ago to diversify out of the SP500 ("VTSAX and chill!") into broader and exUS indices.
I'm reminded of people inside Google arguing with Vic Gundotra to drop the Real ID requirement for Plus :(
There are outcomes where the US government seizes the company. Not super likely, not impossible.
Are there historical examples in the US specifically where we've nationalized a business?
Because we've certainly invaded countries and assassinated leaders over exactly the same.
ETA: I could have answered my own question with two minutes of research. Yes, we have: https://thenextsystem.org/history-of-nationalization-in-the-...
I can't speak to their quality, but every time I see their name, I wonder about how they're received in England: Americans might generally be unaware, but "smeg" as a name doesn't land well there, as I understand it.
Some of us have hands (and wrists and arms) that are dealing with RSI. Keyboard use reduction is very important in these cases.
Greg Priest Dorman [0][1] had other physical issues such that he had to regularly switch between sitting, standing, and walking during his workday. His solutions included (in part) some very specialized keypads, but TTS might well have been another solution for someone with similar needs.
Another fellow on my team refuses to write/type anything other than pure code to solve issues at work, but will absolutely talk for hours on end about designs, considerations, issues, what-have-you, so we're actively trying to get him to adopt a TTS-based workflow for knowledge transfer, writing tickets/bugs, etc.
[0] https://computerhistory.org/profile/greg-priest-dorman/ [1]: https://www.cs.vassar.edu/people/priestdo/wearables/top
Various European cities come to mind: Narrow streets are something of a trope in certain movies/genres.
They're still out there; people are still posting stories and having conversations about 'em. I don't know that CmdrTaco or any of the other founders are still at all involved, but I'm willing to bet they're still running on Perl :)
I feel like Daniel @ curl might have opinions on this.
As covered literally just a few days ago (IIRC), you absolutely can demand payment: https://github.com/LGUG2Z/komorebi actively works to detect MDM, and if found, demand payment.
Not open source, but an interesting counterpoint, I think.
I feel like this is exactly the use case for things like Hooks and Skills. Which, if you don't want to write them yourself, I get it. But I do think we can get the tool to do it; sounds like you want it doing that a little more actively/out-of-the-box?
... If there were an ever-evolving landscape of awful things crawling up out of my sewer through my toilet, I would very much want to pay for automated toilet updates to prevent the most recent awful crawling horror from appearing in my bathroom.
Right, this is just a variation on "If you have nothing to hide..."
ETA: You're not wrong; folk who have specific, legitimate opsec concerns shouldn't be using certain tools. I just initially read your post a certain way. Apologies if it feels like I put words in your mouth.
I left in 2023. From memory at that time:
1) go kinda eliminates a lot of the reasons for style guides to exist w/ `go fmt` and separately, I think the Go readability team made a conscious decision to approach readability differently anyway,
2) ... once you had a couple people on your local team w/ readability, if your team wanted to do things a certain way, well, style guides and formal readability wasn't really an issue anymore.
"The market can stay irrational longer than you can stay solvent"
Why are people so allergic to materialism?
At the risk of starting a fight... I would point at America's religious history, and the continuing threads of that today that increasingly see scientific/materialist thought as a direct threat to their ideas of how a society ought to be organized.