duncan-donuts

I often have to ask myself if I’m asking for something different because of preference or need. I don’t really know what others are doing but I see this comment a lot about needing to always correct agents. I can’t figure out if it’s an exaggeration or not because once I’ve planned how I want something done I pretty much have zero need to intervene.

I don’t think anyone thinks gun control was passed to help school kids. People have been begging the govt to pass stricter gun control laws to protect kids for decades with very little success.

The article does say that he’s already given away this amount of money since the founding of Craigslist 30 years ago. From the sound of things he’s always actively doing philanthropic work, but I could be reading into it too much.

The key distinction here is that the temporary workers would presumably be people who are in federal custody and currently housed in ICE facilities. The temporary housing isn’t the issue.

Serious question – what’s the grift?

I think the terrifying part is just how fast software practitioners completely gave up trying to understand anything. As if these oracles actually know anything about our bespoke systems. It was almost overnight that SMEs were lost.

Introducing “unknown” feels like another kind of hell like undefined in JavaScript.

I think people are actually searching for Lisp far more than we are willing to admit.

I think authentication is about proof of identity. Identity can mean a lot of things imo. Applications identify me all the time without me giving them any proof of who I am. This happens in meatspace all the time too. People project identity and we make assumptions about what we observe. We don’t necessarily ask them to verify this identify through mutually agreed upon terms.

Second the room treatment. It should likely be prioritized over everything. Specifically you should look into getting bass traps and a gobo or three. There’s budget stuff out there but sound is fickle. Control those reflections. Expensive mics still sound bad if a room sounds bad.

I’ve had limited success with the null object pattern but there is one case that it worked really well for me. I worked on a feature that was highly dynamic and users could compose reports selecting data points from tangentially related models. Null objects were a really helpful pattern because it was hard to anticipate how models would be composed and if a developer made a mistake it was hard to notice there was no effect. Our null objects would raise exceptions in development and explain what you need to change but wouldn’t prevent execution in production.

You could easily argue we should have just presented this exception to the user in all cases but this is where we landed. It’s probably the only case this pattern was beneficial for me.

Idk if I’d take that explanation at face value.

I’m trying to recall a time in my career where I’ve heard this phrase and it was actually a technical problem. Most of the time this is a dismissive response that is more political than it is technical. And let’s be honest — we’re the ones inventing the architecture of the applications. If a feature is desired but it “conflicts with the architecture” then you figure out how to resolve the conflict.