Aidan W Steele

I try to tweet novel things about AWS.“Shit-poster extraordinaire” according to @LastWeekInAWS. He/him. AWS Serverless Hero

[Aidan W Steele @__steele]

This is probably the most delightful thing I have ever read about myself. I love it so much.

@forrestbrazeal: thank you for *getting* me.

Everyone else: read the whole article, it’s great.

https://t.co/TQf8S3pekt

[Aidan W Steele @__steele]

@astuyve Excuse the blurry photo taken by my ancient iPhone Air. It looks much better in person, I swear

[Aidan W Steele @__steele]

@astuyve

[Aidan W Steele @__steele]

@hameonline @dannolan @michael_timbs It’s already been available for six hours, how have you not changed your entire workflow around it?

[Aidan W Steele @__steele]

iPhone duo + Amp has got me thinking I don’t need a personal laptop any more. It’s orbin’ time.

[Aidan W Steele @__steele]

@michael_timbs Wtf that sucks. Does it show an error? Or just does nothing?

[Aidan W Steele @__steele]

@ShortJared Same, but I lucked out and was able to schedule a pick-up in a nearby store and get it. So far my main complaint is that it just mirrors the display when plugged into a screen. That's a missed opportunity IMO.

[Aidan W Steele @__steele]

Best practices: don't use `4` as your CA's private key.

https://t.co/p4ieF9wZQG

[Aidan W Steele @__steele]

@astuyve @apparentorder Shit now I’m going to have to rotate all my IAM Roles Anywhere certs with a private key of 4. 7 is still safe though, right?

[Aidan W Steele @__steele]

@tvanhens Oops I meant handwriting synthesis. E.g. take a photo of some handwriting and generate more handwriting in the same style. It’s for a new side-project I’m working on 😁 it’s noticeably quicker and cheaper than Opus 5.5. For everything else I prefer Haiku/Opus 5.5

[Aidan W Steele @__steele]

@ronny @AmpCode I definitely don’t think it’s better this way. But it’s the workaround I’ve been using for now. I’d be keen to know the logic. Maybe something to do token caching? 🤷

[Aidan W Steele @__steele]

@ashishlogmaster I like that idea! I gave it to an agent to investigate. The indexing is likely better suited to Lambda because it needs a lot of CPU and memory. But serving the contents of individual files is perfected suited to Workers. I'll dig further. Thanks for the idea :)

[Aidan W Steele @__steele]

AI has made my abandoned "browse any Docker image" website side-project useable. It now indexes images twice as fast, files can be deep-linked, og:images, and the ability to view only hidden files. E.g. here's a file left behind in a CodeBuild layer.

https://t.co/5YqNO0QR0Z

[Aidan W Steele @__steele]

AWS just enabled scalable network bandwidth, so now the perf has increased again. It now indexes a 6.52GB image in 16.5 seconds instead of 43.7 seconds.

[Aidan W Steele @__steele]

AI cut indexing time in half, but now the limiting factor is network bandwidth. AI asked AWS to enable scalable network bandwidth. It's now checking on that request every hour. Then it will experiment with perf in dev while I sleep and push to prod once validated. What a world.

[Aidan W Steele @__steele]

@zackkanter @diegosantiviago It’s not quite a Rust runtime, but it might get the job done until that arrives https://t.co/cy4Pn9m7y2

[Aidan W Steele @__steele]

Lambda Web Functions aren't strictly limited to only Node.js, despite what the docs and launch blog say. You can instead run Go (or Rust) on them and save money through better CPU and memory utilisation, and easier multi-threading.

3/4

https://t.co/TkUnyyXilB