huehehue

E.g. "this is a one-off report" and "ok, how would you do it differently if we wanted to turn this into a feature at scale?"

It's great if an engineer gets there on their own, but there are so many tangents one could go on that I won't ding someone for picking the wrong one, or asking for the most relevant one.

I would expect seniors not to need that level of guidance on the job, with the caveat that expectations should be reasonably set in design docs, tickets, various bits of context, etc.

At a glance, rats are definitely ridden with fleas and disease, but there doesn't seem to be good data on transmissions. I'd still prefer not to have 10,000 tiny little catalysts for a new wave of the plague scuttling under my feet.

So we really are back to reinventing cable TV

If anyone wants this idea, you can even use the old WeWork signs, just flip the W upside down and change it to MeWork

I tried maybe 3 or 4 private office solutions during the pandemic's height, and each suffered from this. The "phone booths" are the best solution, imo, but they eat up credits and/or are always occupied.

I'd unironically like a huge warehouse of phone booths (like 3x3 offices) I can hole myself in all day. Why does that not exist? Is that just a cubicle farm with extra steps? I joke to my partner about setting up shop in our closet because it's quiet and distraction free.

> Duck: a feature added for no other reason than to draw management attention and be removed, thus avoiding unnecessary changes in other aspects of the product.

It was a low-stakes scenario, but...now I know better.

Especially at night, I find the backlight makes it painfully obvious that it's just a TV and I'd much rather have something like e-ink which blends into the surroundings.

"No worries, we have backups", I thought. Turns out those were more like replication, copying over every change immediately (including deletes).

In the end, fixed with a short script that cross-referenced tables and checked for missing relationships, but terrifying nonetheless.

The first tap to waken the screen often fails so I have to try one or two more times.

It's a small thing but, I have to tumble with it probably 100+ times a day given how often I check my phone for e.g. Slack. It should be the smoothest part of operation, imo.

It's anecdotal based on my social circle and their younger friends, but I'm wary of turning into my parents with advice like "you don't need a degree, just a firm handshake and an affinity for hard leetcode problems!"

Randomly during longer trips, the car will just die for no discernible reason. It's the Car of Theseus at this point with how much I've replaced, but the issue persists, and the nature of these intermittent problems makes debugging a nightmare. More puzzling still that the car starts up fine after a short nap.

I'm generally very defensive on any new apps, tooling, extensions, etc. Emailing a link only takes 5 seconds and I don't need to optimize it any further.

I also don't use bookmarks, or save anything for later, so maybe I'm just a heathen.

(originally linked from elsewhere in this discussion)

Things are different today, but interesting to think that the structural integrity on these old machines was so poor that you'd rather get hurled from the car in an accident.

I know you're talking about the fixed nature of programming logic, but this phrase is surfacing some repressed timezone debugging memories.

For example, some sloped areas have spikes to prevent folks from reclining or laying down, but it would be possible to build a chair/bed that's held in place by those very spikes.

I'm secondhand pissed at the recovery company, I have a couple of ancient SD cards laying around and this just reinforces my fear that if I send them away for recovery they'll be destroyed (the cards aren't recognized/readable by the readers built into MacBooks, at least)

I will say that going direct isn't without problems, though. I can't tell you how many adapters and dongles I've lost. At this point it feels like a wash with how much ends up in a landfill. I'd love for everything to support 3.5mm but that's not the world we live in.

Regardless, just because "outside" is available doesn't mean we can't have things inside as well. Going a bit further, AR was getting people outside en masse during the Pokemon GO craze, so these two things are in no way antithetical.

https://ods.od.nih.gov/factsheets/VitaminD-Consumer/

https://www.hsph.harvard.edu/nutritionsource/vitamin-d/

edit: I also found https://news.ycombinator.com/item?id=35878761 which suggests higher levels are safe, as long as you're not eating D3 pills like kettle chips. So I guess that answers it, though my points stands about there being such a wide range of info

In some ways, the lack of updates can be a feature. I'm sure we've all been frustrated by updates that break our workflows, deprecate useful functionality, or inadvertently degrade performance.

For bigger orgs, this is a chance to sanity check team fit and potentially re-route if longer-term interests align better with some other team. For startups, it can be more of a vibe check.

This is the key thing, and the formula's different for everyone. I know that my strategy of "look at the clock and remember" will work until I'm senile, as will "panic-check the mail every day until my last tax form arrives and file that night"

I have a very low tolerance for error in things like setting timers, playing music, getting weather, calling someone. This is because I can complete these tasks simply, quickly, and with 100% reliability by hand. The marginal improvements allowed by tools like Siri aren't worth it to me if there is any decrease in reliability.

I'm sure there are use cases I'm not considering, but I've also seen perfectly able-bodied folks shout "call Steve" into their phone for 40 seconds longer than it would have taken to navigate manually. Conceptually, the idea of stacking even more engineering onto these tools to get these tasks working reliably is funny.