frabjoused

This is very cool, probably should have gotten more inspiration from Porsche on the design UX. It's pretty rough.

Good to hear from you man, you too :)

I wrote the first commit for slice-ansi in 2015 to solve a baby problem for a cli framework I was building, and worked with Qix a little on the chalk org after it. It's wild looking back and seeing how these things creep in influence over time.

You're definitely a backend engineer aren't you?

Congrats on the bug bounties!

I’m not hyping or defending MCP at all: I’m just saying AI can’t figure out APIs well enough to be something you can promise as a product.

I founded an integration platform so definitely a developer and I’ve been living these problems every day.

Not all http based APIs have an SDK. It’s wildly inconsistent. And when you ask the llm to do something new, does it download the SDK on the fly?

This is very naive. How many different APIs have you authenticated with and connected to? Just the big ones? What happens when the docs are wrong or incomplete?

The success rate of this is impractically low. APIs are dirty, inconsistent things. Real-world connection to obscure APIs is a matter of hard sleuthing. Docs are wrong, endpoints are broken, auth is a nightmare. These APIs need to be massaged in advance and given a sanity-wrapper if you want any semblance of reliable success when a model calls them.

Ironic this post is written in repetitive SEO spam format.

I'm building an integration platform, would love to have a call with you and share ideas.

This reminds me of a time I lost an argument with John-David Dalton about cleaning up/minifying lodash as an npm dependency, because when including the readme and license for every sub-library, a lodash import came to ~2.5MB at the time. This also took a lot of seeking time for disks because there were so many individual files.

The conversation started and ended at the word cache.

You don't have to correct throwaway's opinion, you have to correct your online appearance. People reviewing your submission don't know these details you're giving and they won't ask. Unjust or not, that's the shallow first impression he got.

It's like if a user does something wrong in your app, you don't blame or explain to the user what they did wrong. You figure out how to improve your UX.

I came to similar conclusions from your public profile. The defensiveness of your response would be a 7th red flag.

This needs to be built in at browser level.

Very cool, seems like it updates on a delay though, which will probably kill usability.

This post is not even on it.

If light is hitting it, can you explain why not?

My money is on it just being a playing field for the game of life. A damn good one at that.

That's a good point. Are there no published numbers on FSD?

The thing that doesn't make sense is the numbers. If it is dangerous in your anecdotes, why don't the reported numbers show more accidents when FSD is on?

When I did the trial on my Tesla, I also noted these kinds of things and felt like I had to take control.

But at the end of the day, only the numbers matter.

I don't understand why this debate/probing is not just data driven. Driving is all big data.

https://www.tesla.com/VehicleSafetyReport

This report does not include fatalities, which seems to be the key point in question. Unless the above report has some bias or is false, Teslas in autopilot appear 10 times safer than the US average.

Is there public data on deaths reported by Tesla?

And otherwise, if the stats say it is safer, why is there any debate at all?

Your bot checker needs some UX help.

It’s an excellent detail that the nothing timer resets if you scroll down to read the copy.

I founded an integration startup, so my entire life right now is figuring out how to connect to and normalize an endless number of APIs.

His advice here is spot on. You can’t underestimate how inconsistent the API landscape is, and he’s right that the fancier ones are harder to use.

Some notes:

- Surprisingly less than 5% of APIs reliably use PATCH.

- I’m not sure it’s a good idea to return an Object under data for single resources, and an array when requesting multiple resources. Theoretically it sounds better, but in the end it makes it harder to consume.

Great questions! Emailed you.

This is why I’ve always fought against BEM in CSS. Tends to drive greppability to zero.

I've only used it a day or two and its been around the 150 range. I wonder what mid-week will look like.

Sure, do you want to email, or ask away.

I’m building an integration platform, think Zapier or Workato.

We’ve been hand coding full-service integration workflows for 2+ years on a large B2B agency model, and in parallel have been building a platform using what we’ve learned to build better abstractions.

We’re at an interesting point where almost all new workflows are being built on the platform, and we’re serving over 100 clients.

We’re prepping for public release in the next few months.

It's fascinating to me that these controls were "upgraded" to a VB-style interface in 2016.

I’m building an integration platform. There’s a thousand ways to deeply embed AI throughout it, both to build integration workflows faster, and to help us build smarter API wrappers faster.

But AI has always been a secondary augmentation to the product itself. It’s a tool, it shouldn’t be the other way around.

It’s already solved. It works well. Just walk away.