islandert

Would the JVM ecosystem almost be a working example of this? Since there are a variety of languages with editor integration that all compile down to the same byte code, it feels pretty close to what you’re describing.

I made a CLI tool called kilojoule that is similar to jq. I addition to the normal suite of JSON manipulations, it also has support for a couple of other file formats and can call other shell commands.

https://github.com/stevenlandis/kilojoule

I’ve found it to be a pleasant multi tool for interacting with the shell when I need something a little more than bash.

It took a couple of weekends and evenings to get working but was a really fun way to learn about parsers, interpreters and Rust.

TikTok?

If you don't have access to COPY if the postgres instance is managed, I've had a lot of luck with encoding a batch of rows as a JSON string, sending the string as a single query parameter, and using `json_to_recordset` to turn the JSON back into a list of rows in the db.

I haven't compared how this performs compared to using a low-level sql library but it outperforms everything else I've tried in sqlalchemy.

I love that writing LLM-friendly docs is just... writing good docs. There's a ton of overlap between accessibility work and preparing things to be used by LLMs.

I wonder if an unintended side effect of this AI hype cycle is a huge investment in more accessible applications.

There’s a straightforward way to reach this testing state for optimization problems. Write 2 implementations of the code, one that is simple/slow and one that is optimized. Generate random inputs and assert outputs match correctly.

I’ve used this for leetcode-style problems and have never failed on correctness.

It is liberating to code in systems that test like this for the exact reasons mentioned in the article.

Not high level but a RTO policy seems like an easy way to downsize without having to fire people now that interest rates are higher.

I'm finishing up reading Cadillac Desert, a book describing the history of dam building and irrigation project in the US. It goes deep into all aspects of irrigation projects from environmental to economic to political.

Very cool to hear that this dam is getting torn down just 30 years after the book was published.

My take is that dicts are fine as long as your code is well tested. Yeah, dataclasses and frozen classes have much better typing support, but if you code is mostly reading and writing JSON like many modern cloud apps, it can be easier to use plain dicts combined with decent tests to make sure you don't break downstream services.

I remember when that popped up on my screen in college. Fun problems. There was one where you derived the page rank algorithm, but they framed it as radioactive decay.

Definitely a little questionable though for them to use their browser monopoly and search history to poach developers...

wayback machine link from April 21: https://web.archive.org/web/20220421205808/https://fastertha...

I agree with most of you points, but the one that stands out is "push for unit tests over integration/system tests wherever possible".

By integration/system tests, do you mean tests that you cannot run locally?

WHich has a more powerful processor, the gameboy or the raspberry pi?

I'm working on a python script that downloads web serials as ebooks. It's set up to check if a new chapter has been posted, and if there's a new chapter that finishes a book, it outputs the book as an epub so I can read offline.

To add a new story, I just write a function that takes a webpage and returns the next link and chapter content. It's low enough overhead that I can easily add new stories.