... your awesome vibecoded project has now told you what to unpack first.
729 karma · joined November 2, 2013
... your awesome vibecoded project has now told you what to unpack first.
... I'm suddenly reminded of Iain M Banks' "Surface Detail".
I was working in the Techstop (40) @ Google, 2011-ish, when a nice person from PeopleOps came through and politely requested my admin powers to help them install Steam on their corp-issued Windows laptop.
I'm sorry, what?
Well see, PeopleOps was going to have an onsite intending to help recruiters better understand Engineering types, and part of the whole business was going to involve everyone firing up a copy of Portal and playing a puzzle-solving video game.
So I immediately got to it. Never heard back as to the success of the endeavor, but turns out there are circumstances where you can break out your Steam library at work.
"Assuming that the house is paid for, of course; if your net worth is really only $300K, odds are you don't have the house paid for either"
A long while back, I read (and just now refound) an article about a biologist's take on cooperation and competition. David Sloan Wilson is quoted as saying "Selfishness beats altruism within groups, [but] altruistic groups beat selfish groups, and everything else is commentary."
https://www.theguardian.com/society/2012/mar/06/david-sloan-...
Perhaps with sufficient intelligence and time, altruism/cooperation is discovered to be a better fit for any given environment, and that's passed on.
Serious question, as I understand the ex-Japanese market rights were sold to a Chinese corp over two decades ago, and the in-Japanese consumer device market rights went to a different Japanse company several years ago too.
Apparently they've gone back to focusing on their roots?
"99 bugs in the code, 99 bugs in the code... Fix one bug, compile it again, 101 bugs in the code!"
(To the tune of 99 Bottles Of Beer)
That is, given a lot of users' contexts, the way they can and the way they want to use these models are increasingly disjoint.
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.
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.
I'd personally prefer a belt-and-suspenders approach.
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.
"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
... and you get a running version of whatever $stuff is, immediately built from head, quickly - no matter the set of dependencies, or which language they were built in. I can just try your thing out immediately with a common interface for all the builds, and I don't need to understand the build at all, unless or until I do, and then OK, absolutely every single build is always expressed in exactly the same way, same idioms, same patterns...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-...