Gavin Morgan

Finally, another open model from OpenAI; I'm super excited to try out openai/gpt-oss-120b... just as soon as I get home from hanging out with the family, this week.

How can I keep four machines' configuration and utilities in sync? Still Chef?

Where is it even ergonomic to host an Elixir app? I'm of the mindset that Cloudflare edge workers are a nifty place to modularize "actor-like" business logic into, but what sort of PaaS maximally exploits the BEAM vm?

Comparison of nominal sizes of primary mirrors of notable optical reflecting telescopes, and a few other objects. Dotted lines show sizes of round mirrors that would have had equivalent light-gathering ability. The telescopes shown on this comparison chart are listed below, ordered in each sub-section by (effective) mirror/lens area, low to high, and then by actual/planned first light date, old to new. The "present-day" status is given as of the beginning of 2024. See also List of largest optical reflecting telescopes. Largest refractors (for comparison): 1) Yerkes Observatory's 40-inch (1.02 m) refractor, 1893 (largest refractor consistently used for scientific observations) 2) Great Paris Exhibition Telescope, 49 inches (1.24 m), 1900 (largest refractor ever built; had practically no scientific usage) Ground-based reflectors: 3) Hooker Telescope, 100 inches (2.54 m), 1917; world's largest telescope from 1917 to 1949 4) Multiple Mirror Telescope, 186 inches (4.72 m) effective, 1979–1998; 6.5 m, from 1998 5) LAMOST (Large Sky Area Multi-Object Fiber Spectroscopic Telescope), 4.9 m effective at best, 2009 6) Hale Telescope, 200 inches (5.1 m), 1949; world's largest telescope from 1949 to 1975 7) BTA-6, 6 m, 1975; world's largest telescope from 1975 to 1990 (when it was surpassed by the partially-completed Keck I telescope) 8) Large Zenith Telescope, 6 m, 2003; largest liquid-mirror telescope ever built; decommissioned in 2019 9) Magellan Telescopes, two 6.5‑m individual telescopes, 2000 and 2002; 10) Vera C. Rubin Observatory (formerly Large Synoptic Survey Telescope), 6.68 m effective (8.4‑m mirror, but with a big hole in the middle), planned 2025 11) Gemini Observatory, 8.1 m, 1999 and 2001 12) Subaru Telescope, 8.2 m, 1999; largest monolithic (i.e. non-segmented) mirror in an optical telescope from 1999 to 2005 13) Southern African Large Telescope, 9.2 m effective, 2005 (largest optical telescope in the southern hemisphere) 14) Hobby–Eberly Telescope, 10 m effe…

@miquai.bsky.social I knew there were observatories all over, but I don't know why it never occurred to me that we never stop designing and building bigger, better ones!

Very exciting to consider, and the scope of the data brought in is absolutely mind-boggling.

What's it gonna take for me to finally break ground on my garden plot?

Remind me to experiment with using Djikstra's pathfinding for agent-to-agent transaction selection. Or, at least, some kind of "movement cost" (to approximate, among other things, distance) estimation for my next economic simulation.

Imperfect—but nonzero—information!

Running into this weird cognitive dissonance when it seems like people are using the term #agentic to mean "IDE". I know it sounds crazy! I must be missing a piece of the puzzle, or else is it just evidence that we're not yet seeing agentic tool adoption outside of software industry?

Frankly, however, it's extremely attractive and compelling the thought of an agent daemon living on my machine and planning changes in response to the context of my open files and keystrokes.

I think it's probably critical not to give agents right access to anything that isn't in Version Control.

It's very easy to imagine a local desktop agent getting the notion in its head that there's something extremely inefficient or disorganized about your file system and spontaneously deciding to reorganize all your files while you're not looking.

Let me know how you and your customers are getting value into and out of agents?

Streaming voice is not lagging behind, but is it much of a departure? Screensharing is a promising affordance—in that it accommodates a wide variety of subordinate affordances in an "everything, everywhere, all at once" sort of way—but I'm not sure how the value of personal sousveillance comes home.

I'm struggling, however, to envision the truly revolutionary points of intervention from which agentic sorties cascade, and to which swarms return bearing gifts. I've seen two popular affordances, so far: the text field, the chat box, the file upload dialogue.

I'm psyched to explore implementations of agentic systems leveraging, eg, Javascript's event queue or Erlang's actor model—although, frankly, I'm oblivious as to which fledgling frameworks exhibit the most promising ergonomics.

I'm legitimately excited about MCPs, about agentic architectures, and the stunningly sophisticated workflows they can reproduce—and surpass!

YouTube video by Grant Kot Dev Roadmap: Liquid Layers Maker, VoxelMash, Liquid Crystal Online

Don't sleep on Grant Kot's in-browser physics demos!

Lol, too true; especially in the bad old days. But these quasi cyclical references not inevitable, today.

Either reference CSS only in HTML, or else just wield utility classes in your JSX, and it abstracts away to, merely, a few more arguments passed to \#createEl().

Oh, damn! My average resting heartrate went up 10bpm this past year. I gotta get back into running!

Just discovered a self-service kiosk that returns 503 Service Unavailable on payment requests iff you skip the "tip" option. 😂

😭

"In the end, we will remember not the words of our enemies, but the silence of our friends."

— Martin Luther King Jr.

Oops, Artiodactyla split off from Rodentia ~65 MYA.

Deer are just large mice, are they not?

Hands are cold, neck is sweaty.

Dear body: CIRCULATE!

I don't worry about my knowledge of the software industry going stale because some of the best ideas from 14 years ago still haven't caught on.

The history of software is the future of software.

Catch up on your history!

"For someone who is a traditional Node.js developer coming at this—they're used to having a file system, they've got a long-running server; you know, they're just thinking in that approach—the switch to the serverless mindset is a bit of a hump."

🤔

Adam Wiggins coined the "12-Factor App" in 2011.

"The standard way of deploying code somewhere has always been a container."

Oh, my sweet summer child.

Sometimes, you don't even need to do the thing. Just being mentally prepared to do the thing can enable you to do other, more immediately actionable things.

And, you can still do the thing!

I mean, heck, JSON-with-comments might do the trick.