Working on a workflow library and node based editor that has a little bit of AI stuff for RAG and image pipelines that runs all in the browser (desktop next month, cloud whenever someone asks). Just a toy at this point.

https://workglow.dev/

I see Shadcn and Hero Icons

Carter gave up the presidency to save America then. Volcker did the right thing.

He does deserve some credit, but 1979 was a total mess for the growth, inflation, the dollar. Nominating a credible Fed chair to fight inflation was both a risk and politically expedient in the short term. Trying to build some economic credibility at the risk those policies slowing growth.

Reminds me of the history or radio and the absolute uproar that someone played a record on the radio rather than live performances!!

Who ever said they were finished? You think the laid off the team since everything is “done”?

It’s not for that. It’s for things like the car drove into a protest area and people are surrounding the car. Or police blocked off an intersection and the car is stuck temporarily with people doing otherwise illegal u-turns or driving the wrong way on a one way road to get out of it.

Oh yeah, point a q-beam at a Tesla at night, lol. Blindness!

And lets you rewrite queries on the fly. :)

Uh, any database of sufficient size is going to do migrations “out of band” as they can take hours or days and you never have code requiring those changes ship at migration start.

Small things where you don’t have DBA or whatever, sure use tooling like you would for auto-changes in a local development.

Very large tech companies completely automate the schema change process (at least for all common operations) so that development teams can make schema changes at scale without direct DBA involvement. The more sophisticated companies handle this regardless of table size, sharding, operational events, etc. It makes a massive difference in execution speed for the entire company.

Renames aren't compatible with that automation flow though, which is what I meant by "out-of-band". They rely on careful orchestration alongside code change deploys, which gets especially nasty when you have thousands of application servers and thousands of database shards. In some DBMS, companies automate them using a careful dance of view-swapping, but that seems brittle performance-wise / operationally.

Sure, but they don’t go out with the code. They go well before.

Right, but my point was that renames in particular typically can't go out well before the corresponding application change [1]. Thus, renames are "out of band" relative to the company's normal schema change process. (This is orthogonal to how schema changes are always "out of band" relative to code deploys; that wasn't what I was referring to.)

[1] In theory a custom ORM could have some kind of dynamic conditional logic for table or column renames, i.e. some way to configure it to retry a query with the "new" name if the query using the "old" name fails. But that has a huge perf impact, and I'm not aware of any common ORMs that do this. So generally if you want to rename a table or column that is already used in prod, there's no way to do it without causing user-facing errors or having system downtime during the period between the SQL rename DDL and the application code change redeploy.

Not to mention apps that may have differing versions deployed on client infrastructure with different test/release cycles... this is where something like grate is really useful imo.

Not to be confused with “human” thanks to SCOTUS.

Not unless they are marketing it as “autopilot” or some such that a random consumer would reasonably assume meant autopilot.

And I’d include “AI driver” as an example.

A random consumer doesn't actually understand what Autopilot means. Most people don't have pilot's licenses. And cars don't fly. Did you not see all the debacles around it when it first came out?