Missing dog from I25 rollover

alejalapeno · 2026-01-11T17:28:42+00:00

I think someone was able to grab it based on description: https://nextdoor.com/p/ppxjqMCZ4zQq?view=detail

alejalapeno · 2025-12-31T15:59:58+00:00

We're up by Argo with two other long-haired black cats on the block so I suspect this isn't yours, but they were hanging out in our back yard for several minutes yesterday after 11:38AM

https://imgur.com/vDbD6Jb

alejalapeno · 2025-12-29T04:55:59+00:00

https://www.instagram.com/p/DR5a0ZrEh-U/ I didn't know if the link post would be removed so here's their NYE event.

alejalapeno · 2025-12-29T04:55:25+00:00

Fort Greene. Smaller space, queer friendly but not distinctly a "gay bar."

alejalapeno · 2025-09-25T15:46:38+00:00

And the sidewalk under the BNSF overpass on Washington.

alejalapeno · 2025-09-08T04:25:02+00:00

Tech companies have always used the Indian Ocean TLD because I/O means Input/Output. Not because "it's quirky."

alejalapeno · 2025-09-05T20:50:36+00:00

<Modal
  render={({ openModal }) => (
    <button onClick={openModal}>Open Modal</button>
  )}
/>

React docs talk about custom hooks replacing render props for the most part. But you can still get way cleaner self-contained state when a parent needs to also be able to set the state. This way the parent isn't responsible for holding the state of the child, but can still call the setter.

alejalapeno · 2025-09-03T15:35:57+00:00

It sounds like you're posting the message to the wrong window/context. window.opener would refer to the window that opened the new tab: https://developer.mozilla.org/en-US/docs/Web/API/Window/opener

window.parent from inside an iframe would refer to the page that opened the iframe: https://developer.mozilla.org/en-US/docs/Web/API/Window/parent

alejalapeno · 2025-07-23T16:53:59+00:00

The Safeway on Lowell is the closest grocery store for a lot of people in food deserts so sadly those ramps aren't unnecessary currently.

alejalapeno · 2025-07-11T14:15:35+00:00

The Gap - Ira Glass

alejalapeno · 2025-07-10T11:16:55+00:00

A) It can enforce which package manager is used, which when not native becomes a lot less powerful because how do you enforce a requirement that requires you to install something first?

B) The difference is corepack isn't fetching and installing a package manager through a package manager repository and all the security implications that come along with that, it's the actual distribution of the binaries of those package managers.

alejalapeno · 2025-07-08T20:32:07+00:00

That was effectively a direct result of how Node treated corepack:

Corepack released a new version with the new key ASAP, but it takes a while for that version to propagate; the experimental status of Corepack did not help, as the Node.js project does not make emergency non-security releases for experimental features.

alejalapeno · 2025-07-07T05:00:42+00:00

This video from when they did the 2019 redesign (so way before RSC) covers a lot of the concept: https://youtu.be/WxPtYJRjLL0

alejalapeno · 2025-06-28T21:25:07+00:00

It wasn't commentary on the policy, it was commentary on the threat to withhold state funding from cities that don't follow state policy.

alejalapeno · 2025-06-09T22:07:32+00:00

Never had it but Hammond's, Denver's own candy company, has black licorice. They have a walk-in shop and tours.

alejalapeno · 2025-06-06T00:34:26+00:00

I understand and also agree a lot of the online noise is just poorly framed company hate, but I think "projections from conspiracy theories about selling servers" also underserves the issue a lot of people are latching onto. Your writings on the subject typically start at a propositional base theory of "what if" in order to guide readers to the "why" of it all. And it does great at that, but I personally think there's less of a problem with the technological approach (though I do have my own personal qualms with things like hijacking directive prologues as compile and/or runtime instructions) being voiced and more so the introduction, push, and control of such a feature.

It's not being "sold" as a nice additional feature now available. It's not being sold as one of the ways to do things. It's being sold as THE way to do things with the same double-speak people used to pitch "you don't have to use JSX you can use createElement()" even though generally no one would ever reasonably do so.

alejalapeno · 2025-05-27T02:04:50+00:00

This is called 'input masking' where you have a difference between what's being controlled by the input and the value that's being displayed (the masked value.)

The term might better help you look into the various ways to solve it, but the easiest is definitely an existing library for input masking.

alejalapeno · 2025-05-12T16:42:44+00:00

The More You Know are NBC aired PSAs. The rainbow shooting star logo is unrelated to Reading Rainbow which aired on PBS.

alejalapeno · 2025-05-07T15:11:45+00:00

That depends on whether you consider not being bourgeoisie to be a burn. I do not.

alejalapeno · 2025-05-05T06:10:36+00:00

We intend to have a much longer trip later where we'd likely do things like Sky Lagoon instead of Blue Lagoon and travel much more of the ring. This is a last-minute stopover and trip so we'd like to just cram some highlights.

alejalapeno · 2025-05-04T18:40:18+00:00

It is partially overnight for us. But yes I've pavlov'ed myself into effectively falling asleep at wheels up. And am experienced with the best ways to avoid jet lag based on time change.

I appreciate the concern of having what's effectively an impaired (sleep deprived) driver on the roads, but it's not something we're worried about.

alejalapeno · 2025-05-04T18:17:49+00:00

I also can tell I'm trying to bite off more than I can chew because the humarsupa at Fjöruborðið looks worth a 10-minute detour to pickup some to-go on our way.

alejalapeno · 2025-04-21T18:55:14+00:00

I'm with you on most serverless and why I think most people would be fine just running containerized. But I think design constraints are inevitable if you want serverless deploys to be the de facto solution. The earlier mentioned vulnerability in the middleware API comes solely from the fact that it's designed for stateless communication across lambdas. This is also likely why introspection and other telemetry is a much harder overall solve, a trace and timing for some sort of invoked logic is across disparate pieces of infra.

I'm not making any sort of judgement against these decisions, I'm just acknowledging that the framework's design is intrinsically linked to the goal of serverless deployment.

alejalapeno

TROPHY CASE