eddyg

This is a great data-backed resource to refute made-up claims about data centers:

https://www.andymasley.com/visuals/ai-prompt-footprint/

It’s all about the harness, not just calling the API.

If you’re gonna capitalize the “D” you should also capitalize the “G” (since it’s the first letter of his last name…)

Thanks for the reply!

I went to make the change, and all the sudden it started working with “>” again (not URL encoded) so this appears to have been a transient issue.

From 27 years ago... you could almost search-and-replace "PCs" with "agents" and re-publish it today...

Dig more coal -- the PCs are coming

https://www.forbes.com/forbes/1999/0531/6311070a.html

The guy who led the Aperture, iPhoto, RAW Camera and Core Image engineering teams (an 18-year Apple veteran) is behind Nitro, which works on macOS, iPadOS and iOS.

https://www.gentlemencoders.com/nitro-for-macos/

I do something similar, but tell the agent to write a recipe into a justfile. Then it can run `just` and get a self-documenting list of all the tooling for the project (just build, just test, etc.)

https://github.com/sindresorhus/quick-look-plugins lists some good ones. (I still use Peek.)

Attestation is already in place from STIR/SHAKEN. You can test your carrier here: https://clearlyip.com/services/attestation-service/

The FCC’s database of compliance is here: https://fccprod.servicenowservices.com/rmd?id=rmd_listings

This is the next step in KYC.

"It is (and, increasingly, was) used to signify that a bibliography entry has the exact same author(s), editor(s), translator(s), or corporate author(s) as the previous bibliography entry."

https://danieljtortora.com/blog/3-em-dashes

From the GitHub COO on April 3rd:

    Platform activity is surging. There were 1 billion commits in 2025.
    Now, it's 275 million per week, on pace for 14 billion this year if
    growth remains linear (spoiler: it won't.)

    GitHub Actions has grown from 500M minutes/week in 2023 to 1B minutes/week
    in 2025, and now 2.1B minutes so far this week.

    So we're pushing incredibly hard on more CPUs, scaling services, and
    strengthening GitHub’s core features.

They also had a recent blog post about availability: https://github.blog/news-insights/company-news/an-update-on-...

I don't envy the scaling issues the GitHub engineers are facing! #HugOps

There are tons of good options for window management these days.

I’m currently trialing https://tangrid.app/ and it’s got some nice features.

For ref, fere’s the FRED chart on credit card debt:

https://fred.stlouisfed.org/graph/?g=1Vus3

Telemetry (if it’s truly telemetry) is nowhere close to “tracking”. People conflate the two all the time. One can provide useful, anonymous metrics (e.g. “user enabled feature X”) without doing anything but incrementing the counter for “feature X”.

The “Firefox Problem” is that all the power users disable telemetry, so all the “cool” features that power users like (but never get used by “regular people”) get ignored or removed instead of improved because, according to the metrics, “nobody uses them”.

^X^E in bash takes your current prompt and moves it to your $EDITOR.

for zsh:

  autoload edit-command-line
  zle -N edit-command-line
  bindkey '^X^E' edit-command-line

Jira excels when there is a Jira governance committee comprised of people who actually understand data flow and are the only ones with admin privileges.

Too often some manager asks for (and is given) admin access and starts “improving” things.

Sure, anybody can create custom fields and screens and slap together a janky “workflow”, but well-oiled Jira Ops prevent an explosion of custom fields, they curate the create, browse and edit screens of each issue type to only show the fields that are important at that stage, use custom screens on workflow transitions along with validators and conditions to help ensure an issue is always in a reasonable state, etc. Then users don’t complain about the tooling.

But Jira governance takes time, effort, discussions with stakeholders, etc. And without it Jira gets a bad rap.

The scale of growth they’re dealing with is insane.

“There were 1 billion commits in 2025. Now, it's 275 million per week, on pace for 14 billion this year if growth remains linear (spoiler: it won't.)

GitHub Actions has grown from 500M minutes/week in 2023 to 1B minutes/week in 2025, and now 2.1B minutes so far this week.”

Source: GitHub COO on April 3, 2026. https://x.com/kdaigle/status/2040164759836778878

Bebop⁽¹⁾ is my preferred method. I can open it directly and capture an idea or note with one tap, or use its share sheet to capture links.

It can be configured to append to an Obsidian “Daily Note” in an iCloud vault, which works great.

No third-party services FTW.

⁽¹⁾ https://apps.apple.com/us/app/bebop-quick-notes/id6477824795

[dupe] https://news.ycombinator.com/item?id=47851242

[dupe] https://news.ycombinator.com/item?id=47851948

[dupe] https://news.ycombinator.com/item?id=47851948

[dupe] https://news.ycombinator.com/item?id=47851086

[dupe] https://news.ycombinator.com/item?id=47851242

[dupe] https://news.ycombinator.com/item?id=47851086

I'd like something like this for week-long+ road trips.

The day before we leave on a trip, I manually use 10-day forecasts from something like weather.com to help figure out what to pack and see if it's worth making scheduling adjustment. I'd like to know what the forecasted weather will be in each of the planned stops. High/low temperature and weather for each stop (we might be at a stop for many hours, so the weather can change), plus forecasts for any "overnight" cities, so we know what to expect while at the hotel/campground/etc.: at arrival time, the overnight conditions, and in the morning at expected departure time.

I'm more concerned about weather during planned stops than "weather on the way".

Something that integrates with https://furkot.com (the best road-trip planning tool ever!) would be great!

+1 for imperial units

Jira (hasn’t been JIRA for a long time) is great when you have proper Jira governance in place, with admins who say “no, you can’t have a new custom field, use this one with a new context”, configure good workflow transitions with validators and conditions, design appropriate create, view and edit screens (instead of using the same one for three separate operations), etc. The problem is always crappy administration, not Jira. Jira can be fantastic when properly managed.

FWIW, they sold to Amazon in 2008.

https://techcrunch.com/2008/08/01/amazon-to-acquire-abebooks...

Airpods Pro audio quality "garbage"? That is beyond harsh, and a quick search will find countless reviews extolling their audio quality.

e.g. https://www.soundguys.com/apple-airpods-pro-3-review-close-t...

A lot of live updates here:

https://www.mirror.co.uk/news/world-news/stryker-live-iran-c...

Does Ghostty have iTerm's native tmux integration feature yet?⁽¹⁾ That is a killer feature these days.

Other things in iTerm that I've come to rely on:

- Instant Replay

- Scrollback timestamps

- Scrollback annotations

- Completion from anything in scrollback (Cmd-;)

- Global search across all tabs

- Automatic profile switching (via shell integration) when ssh'ing to different machines

- Keyboard-based select/copy mode (to avoid having to select with the mouse)

I'm sure I'm missing other stuff, but these things make it hard to switch from iTerm (which has always been a powerhouse for me!)

⁽¹⁾ https://iterm2.com/documentation-tmux-integration.html

Open-hardware e-paper: 13.3”, 1600x1200, 75Hz, HDMI & USB-C, Mac compatible: https://www.crowdsupply.com/modos-tech/modos-paper-monitor

https://specstory.com/specstory-cli is another tool in this space (it writes clean Markdown session files into the project for future reference)