corrral

Used to do "!wiki http status codes" to quickly get to that page.

Now I just go to http.cat.

It's in the name.

Webster's 1913:

Maid (?), n. [Shortened from maiden. ?. See Maiden.]

1. An unmarried woman; usually, a young unmarried woman; esp., a girl; a virgin; a maiden.

My iPhone doesn't have these problems with my nearly-a-decade-old Honda Odyssey's BT stereo system. Neither does my wife's iPhone, nor the couple others we've owned while owning this van. That thing (the stereo / "smart" entertainment system) has got plenty of "how the shit did this pass QC?" quirks, but none relating to its interaction with my phone.

It's the car's fault.

> You're part of the in group, you made it, you have achieved sameness, you have an iPhone.

Orrrrr we tolerate repeated mistakes on Apple's part because every time we poke our heads up and look around at the rest of the market (or even try switching for a while!) it's clear we'd just be trading every one problem for three others.

I sincerely wish any other tech companies would at least credibly pretend to actually be competing with Apple head-on, rather than just avoiding them and trying to fill other niches.

You could use a trigger to cascade soft-delete flag toggles, provided all the relevant tables have such a column. Still have to factor that into your other queries, but at least you wouldn't have to make potentially-impossible-to-exhaustively-check joins to figure out if a given row was "deleted".

The DB's responsible for maintaining the integrity of data in it, unless there's some very good reason you can't let it do that. It's faster and better at it than your application, 99% of the time, and it can keep doing that even when/if a second application starts using the same database, or when being used from a SQL prompt, or whatever.

I'd add tagging, for anything that could conceivably use it, when you're doing DB design. May as well start with support, even if the functionality's initially dormant. Someone will ask for it, directly or indirectly, and it won't take long before they do.

Not just SF, and not just bikes. My experience is that cops don't give a shit about any theft unless it happens right in front of them. No amount of evidence you can hand them will convince them to spend so much as a minute investigating.

You can send Swift Playgrounds apps to other people over messages. To pick just one example, from what's often the main target of these "LOL these aren't real computers" sorts of complaints. If you're on a desktop, there are tons of ways, most more accessible than Back In My Day.

I do think we lost something when Flash in particular died, but less apps/games (there are... a lot of very, very indie games made these days by solo hobbyists or enthusiasts, check places like itch.io, it's an overwhelming number) and more the independent animation scene, which was huge during the heyday of flash but seems mostly dead now.

> They don't endlessly complain to Zuckerberg that their business's page is slathered in Facebook Blue, but if the Web site's buttons aren't the precise shade of mauve that matches their CMYK offset press business cards, they pitch an unholy fit.

I, for one, am extremely skeptical that the intense focus on making sure every little thing on every page or app is "on brand", and the significant costs that preference incurs, has positive ROI. Nonetheless, every company seems to have become obsessed with it.

Plus, if you miss a mistake in a shoot it will be expensive to fix after shooting wraps, if not impossible. Bugs might get more expensive to fix over time, but most don't, really. Not like that—not with such a very-near-future cliff after which they get far more expensive. And I'm not sure how many more you'd catch doing daily team reviews versus less-frequent targeted code reviews, anyway. The practice sure sounds brain-meltingly dull, to me, and with little benefit.

Horror stories about the lines these days, unless you buy the extremely expensive passes that let you skip them, are why I'd hesitate to go even for free. I don't get why people pay for it. 55 minutes in a line for every 5 minutes of fun is a shit deal even if it's free, IMO. Sounds like hell.

The rootless docker image + SQLite storage is pretty damn easy. SQLite's certainly fine for a team of tens, and probably even into the low hundreds.

Damn, that changed fast.

I expect using a truck as a truck, for a situation in which a roof rack or a small trailer towed by a lesser vehicle wouldn't have sufficed, 18-19 days a year would put you way above average for non-business truck owners in my area.

Never stopped country folk before. See also: shooting stop signs.

Doesn't work for suburbanites with trucks, though.

I know how to set up and manage Gitea pretty well.

... maybe I should start a Gitea-as-a-service company.

> A two seat pickup is a niche vehicle, about as useful for carrying a family around as a two seat sports car.

Not to country folk—kids ride in the bed. Or crammed in the middle if there aren't too many of them and they're still fairly small and you're lucky enough to still have a bench seat.

> There's a subset of contexts where they make sense although I think for _most_ people they're infrequent enough that it's way more sensible to use a cargo van or a sedan and then just rent a truck during the minority of times when you actually need one.

Even a minivan can tow a small trailer for occasional lumber store runs or towing a jet ski or two. Or just use the roof rack and some tie-downs. Or take the seats out, many of them will fit some plywood inside without trouble. For a larger boat, you can often rent a slip at your usual lake or whatever cheaper than the difference in annual TCO between a truck and a smaller car. Not helpful if you move your boat from one body of water to another a lot, but the only folks I know who do that have small fishing boats that a van could probably tow just fine. Besides, you can pay for several construction deliveries and probably pay to have your boat moved a couple times a year for the difference in annual cost. No sense paying all that extra gas, insurance, and up-front cost for something with features you only use every other month or less, when you can just pay less money to do a daily truck rental periodically, for a delivery service, et c.

But no, people need their immaculate $50,000+ trucks in the 'burbs just to show that they could blow $50,000+ on a truck they don't need, and so they fit in with their buds who also own trucks. Quite a few are purchased for good reasons, but a lot are mostly purchased for social signaling.

Sure, but in practice most people ignore the prototypal features, especially if they're using the "class" keyword, so it may as well not be prototypal. Which is good, because the distinctly prototypal pieces are usually bad behaviors to rely on. The wrong kind of magic.

Yes, the hoarded data is per se dangerous. It should not exist, as in, it should be very illegal to collect and retain. That goes for non-tech companies that do similar things, like credit card companies.

[EDIT] That is, things like credit card companies selling your purchase history. Obviously they do need to retain some of that information to operate, but they shouldn't be able to sell access to it or use it for any other purpose. Ditto banks, magazines selling subscriber lists, all that crap. Should not be legal.

My last experience in mobile dev was that everyone wanted everything to look like Material UI everywhere, because that's what was trendy on the Web. And that even Android had, bizarrely, pretty poor support for Material compared with the Web, so it ended up being a huge pain on both mobile platforms. I guess it's like how you used to have to call out to JavaScript on Android to get a decent Google Maps address & location library because the Web versions were better than the native Android one, which made no damn sense but seems to be part of a pattern with Google of treating their own mobile OS as a second class citizen compared to the Web.

Part of this isn't designers, but "stakeholders" and managers and such wanting to put their stamp on things. They often do this through design, I suppose because you can show anyone a screenshot in a powerpoint and they can appreciate it, but you can't show everyone a program logic flow chart and have them appreciate it.

One way to push back, if you use anything like story points for estimation and scoping, is to point low-design and high-design options separately, for any elements where design choices may have a major effect on that. "This is a 5-point feature with a basic button with the correct brand colors and a spinner for busy state—but a 13-point feature with what's presented in the designs, including a bouncing hover animation and the button morphing into the company logo as its busy-state et c."

Part of the problem is the cost of design on the development process, not just making initial mockups, is often ignored or not correctly accounted for. If you make it explicit, lots of times it turns out a simpler version (which is going to be better for users anyway, 90% of the time—but being good for the users isn't the reason for a lot of UI design, see: constant user-hostile but flashy redesigns across the industry) is in fact acceptable if it means you can fit another feature or two in a given sprint. "We can come back and do the fancier styling & behavior later when we have less feature development to do" but then, as with most things that get deferred, you never will, which is for the best.

> Hell, what's wrong with a phone call?

You have to remember to take notes.

I hate going to find something in Slack history and seeing a phone call right around where I think important information may have been conveyed. At best, I have to go look other places to find it. At worst, there's nothing. And since I may not have been on the call, it may not even be possible for me to have notes, short of bugging the people who participated and hoping they took notes.

This even goes for personal stuff. I much prefer when my wife sends me important info via chat (not Slack, in this case) rather than calling, unless it's super time-sensitive, for basically the same reason.

Email evades the objection to calls, sure, but I've yet to see an email client that doesn't suck for low-friction multiparty chat. Yes, including gmail. I'm pretty sure this could be solved by a client, but I've not seen it, and I think part of the problem is having to accommodate other clients' default quoting behavior and threading and such, so it may be something that could technically be solved by a good client, but couldn't in fact be solved by a client.

Or foreign governments or corporations (think: taking down a competitor or extorting business favors) for blackmail purposes.

Breaking basic language norms in this way is the equivalent of CONSTANTLY RAISING YOUR VOICE. It's distracting and attention-getting. Which may be your goal, but if your goal is to be easily understood and sympathetic to your reader, it's counterproductive.

I thought it did, though, since it mainly restricted anti-abortion laws that apply in the first trimester, with it (and later decisions) allowing significant restrictions in the second and, especially, third trimester? It definitely didn't ban abortion restrictions entirely.

I'm pro-choice but every time I read an online thread on the topic I spend the whole time face-palming over "my side's" bad arguments and total failure to understand pro-lifers' positions.

It's actually not the only topic on which I think it'd be a lot easier to work as a conservative operative or pundit crafting or delivering arguments against what I believe, than as a liberal operative doing the same in favor of what I believe. I'm not sure if that's true for a lot of people regardless of their beliefs—that is, that it's just way easier to argue something you don't actually believe, in general, so there are also some conservatives on the other side going "man, it'd be so much easier to argue for liberal positions"—or something about the level of nuance or whatever required to vigorously defend current liberal positions versus the difficulty of defending current conservative positions. Hard to judge which is the case, for me at least.

I'm... pretty sure that's not true. For one thing, I can't ever recall having to enroll a child with insurance or having them on any of our insurance cards before they were born. They are, in a sense, covered, but not in the same sense they are after they're born.

Gotta have a carve-out for the folks participating in an MLM scheme out of their house. They're quite popular.

Of course it also benefits remote tech workers who have an LLC or whatever. And handymen, et c.