I promise you never want that.

Matt Cutts went from Google to the US Digital Service and did some amazing work. Maybe he’s an outlier, but I don’t think so. There are a lot of supremely talented people willing to take a massive pay cut to do good, meaningful work.

Three things:

1. Exactly zero companies, much less startups, are like the US Government.

2. He had 2 years at the NSA prior to his Google run.

3. I'm pretty sure he's one of the highest profile google engineers, you're not getting that for $500k.

No one has to read hacker news right now.

“I predict future happiness for Americans if they can prevent the government from wasting the labors of the people under the pretense of taking care of them.“

Where "wasting the labours of the people" seems in reality to mean "subsidizing rural schools so they have the same education standards as urban schools".

Of course the guy you're misquoting also had slaves, so I'm not sure if I give a shit about his predictions for American's happiness.

A lot of these tools show off what a full success backlog looks like, in reality I care significantly more about what failure looks like, debugging, etc.

Ha this is a really good point! I worked with so many different kinds of observability approaches and always fell back to traced logs. This might be part of the reason.

Yes but they do that without doing any of the labour.

It’s so wild to hear capitalist talking points come from a worker.

Brother they’ve been threatening that for decades. If that was possible they would have done it 40 years ago.

Wake up. Engineers in other countries are just as good as we are. The only reason we don't hire remote is that the business functions here keep the same hours.

You throw unions into the mix and suddenly dealing with the time difference becomes the lesser evil.

I hire remote programmers in multiple countries. I absolutely know that they’re as good as we are.

I promise you that capitalists aren’t really concerned with time differences.

Actually, it doesn't matter at all.

Giving up on that treadmill after investing 3 insanely intense years consuming everything about it was the best thing I ever did. Now I write elixir (phoenix liveview), sometimes I write javascript (phoenix hooks), sometimes that javascript uses Alpine. Zero pain.

I have never felt more vindicated understanding HTTP, Hypermedia, and HATEOAS than I have in the last three years.

I've only used Elixir/Phoenix as the backend with Elm as the frontend. If you're familiar with that, can you TL;DR what Phoenix Liveview does differently than a Phoenix/Elm/GraphQL stack?

Yes. You get to drop the javascript compile and the graphql and you speak purely in three languages:

  1. elixir: def handle_event("save_customer", params, socket)...
  2. html: <form :for={@form} phx-submit="save_customer">
  3. And sometimes rarely javascript: this.pushEvent("reorder_customer_priorities")

That's it. No compiler, no type annotations, no graphql layer.

Liveview nearly eliminates the boundary between backend and frontend. Your forms, inputs, outputs, whatever, just become another GenServer with a few special callbacks. You no longer have to worry about an API and syncing data from client to server. The transport layer becomes invisible

It's not even worth it to talk about GenServer or special callbacks. Any idiot can just think of it as "phx-{binding}" html attribute and "handle_event".

You don't need to migrate everything, just getting the ones from users that migrated from twitter would help a lot seeding Bluesky profiles.

You can also link Twitter to Bluesky with either OAuth, or a Twitter post with a Bluesky challenge to prove you have control of the account.

That sounds like a lot of manual work, as I don’t expect Twitter to offer an API for departing users…

Not an API but if you're a departing user: https://www.theverge.com/23453703/twitter-archive-download-h.... Bottom line: it's possible to download all account history with tweets in JSON format with dates, and more.

Sure, but now you're back to trust. Unless it's signed, which it doesn't sound like it is, anyone could fabricate their Twitter post history.