1,848 karma · joined February 21, 2014
1. Get people to change sides. This is difficult: people who already vote in a particular way are unlikely to change because of external pressures (and in fact, are more likely to dig their heels in if challenged on their views); or
2. Get more people to vote. This can be challenging in its own way, but can also just boil down to logistics problems.
Whether or not 100% voter turnout would have the same results is neither here nor there. If you accept that premise + the premise that the vast majority of American voters vote down the party line for one of the major two, then you have potentially 2x the number of voters for your desired outcome. All you have to do is go find them and get them to vote.
The automatic coauthor line is also just a pet peeve. It’s a tool, not a person. I don’t say that a commit was coauthored by vim - why should Claude get special treatment?
Less than half of the US population voted in the last election. ~50% of Americans _who voted_ voted for the party that is diametrically opposed to unions, but that group is only ~23% of _Americans_.
I had a 50/50 chance of guessing which side of the bell curve you were on and I was wrong. :)
* You're an engineer with 3-6 years of experience in a primarily IC role
* Maybe you've done some tech lead stuff, but you've never actively worked in engineering management.
* You feel that management (and HR for some reason?) is constantly in the way of you getting stuff done, and that your life would be easier if you could simply decline every meeting and only communicate through pull requests.
Humor me, please. I'll explain after.
Do you have literally any proof? Otherwise, this is all just a silly made up story as far as I’m concerned.
That claim falls apart as soon as it touches reality: there are a _lot_ of people who are involved in the drug trade, now and in the past. At some point, one of those people would definitely have had a CT or an MRI on their skull (e.g. my dentist does a whole head CT every 5 years as part of the normal process and insurance pays for it). Surely _one_ of those people would have noticed a brain implant.
This sounds extremely made up.
Then how do you know about it? This sounds extremely made up.
> your vendors are likely neurocompromised as well.
What in the world are you talking about.
They aren’t and they didn’t.
> Being a self-made billionaire means they created a billion dollars of value. They didn't take it from you or anyone else.
Nobody is a “self made” billionaire. That value you’re talking about didn’t just spring into existence. It had to come from somewhere. There is always a source.
Who flew the rocket? Who built the rocket? Who built the parts for the rocket? Who mixed the fuel?
Building big ambitious things is a good thing. But consolidating an amount of money that nobody could ever reasonably spend into the hands of one person (especially when that money is just the excess value produced by the workers) is unethical and unneeded.
The key difference between what you're doing and what Homebridge enables is to make the relevant app the "Home" app. If all of my IoT devices are controllable (and can be automated to some degree) through a single pane of glass that I can share with my wife, that's a big improvement over "Ok, to get access to our cameras, you need to go install these three apps and log in to all of them and accept my sharing invite, etc, etc".
Yeah, you can talk to Siri to control the devices sometimes, but that is at the very very bottom of my list of benefits. I want the app UI specifically, and Homebridge enables that. (one concrete example: Ring doorbells don't play nicely with Homekit on their own, but you can install a Homebridge extension and then your doorbell camera shows up as a Homekit-compatible camera in the Home app).
Web design _does_ sound much easier when clients can be anesthetized. :)
Three states over and back would be a day or two minimum, but potentially nearly a week on the west coast. (Depends on start and stop locations obviously, but if you start from eg Portland, three states over could be the Dakotas).
From a technical perspective, it doesn't seem to be _that_ difficult: it seems like KYC but for anyone who wants automated access to telephone networks. I know there are some existing efforts there that are more technically comprehensive than that (SHAKEN/STIR), but I don't know where they're at in terms of adoption/rollout.
What’re the actual, practical results of a package pushing you towards a higher go version that you wouldn’t otherwise have adopted right away? Why is this actually important to avoid beyond “don’t tell me what to do”?
Can you please elaborate on this? I've seen this argument from others as well, but nobody has ever been able to articulate what that actually looks like and why rebasing branches specifically is to blame.
My perspective: whatever happens to the commit history on your non-`main` branch is your business. I don't care about the specifics until your work is merged into a shared branch that we all understand to be the canonical representation of the software we're working on.
Gonna be honest, it has taken away from the message both times I've seen it. It feels a bit like you're LARPing your favorite humans vs robots tv show.
> In practice, pornography showing genitalia and sexual acts is not ipso facto obscene according to the Miller test.
I'm not sure you can make the statement that pornographic materials aren't protected speech. I don't think you can make the statement that they are though.
bombcar said "They're quasi-generated with random elements and fixed elements - similarly to early Diablo procedural generation." (which is true - you confirmed as much in the very next comment - "The levels are all hand drawn, not generated by an algorithm, even if they’re shuffled.". That's all early Diablo was doing.)
"Quasi-generated" seems like an appropriate descriptor here - stringing together level building blocks algorithmically is still "generating" a level in a sense. You're right - it's not correct to say that they were generated in the same way that an LLM generates things, but a) nobody claimed that and b) there is an undeniable element of procedural generation here.
I did not claim that it was the same security scheme or that it's biometric or anything like that. I did claim that you have to physically touch it to activate it.
Edit to add:
re 'Yubikey Nano is a "thing you have", TouchID is a "thing you are".', I would argue that your finger is in fact a thing you have. The loss of a finger might change a little of who you are depending on the circumstances that led to you losing said finger, but these both fall into "thing you have" territory for me. I don't think it's wise to consider Touch ID much more than that, personally.