isjustintime

the slop that you didn't know you needed :) thanks!

Last night, I wanted to build a casual "compare frontier LLMs" page as a Pokédex. I went off the rails a bit and ended up with an entire game where claude opus and gpt-5 can fight each other in an SF coworking space and you can watch them burn $$ as they fight. Obviously extremely vibe coded.

I wrote this and I’m happy to answer any questions about savings, infrastructure, how we built and tested this in our environment, or open sourcing it with AWS.

Repo is here: https://github.com/aws-samples/sample-spot-balancer-spark-ek...

Yes, dataclasses are great. I often use them as a pretty clear and adopted way to handle serialization and deserialization, configs, etc.

Very cool. We use Tiktoken and I'd love to see the performance impact. Pretty great decision to make it drop-in compatible.

I love the visual approaches used to explain these concepts. Words and math hurt my brain, but when accompanied by charts and diagrams, my brain hurts much less.

I'm also interested in the details on how this works in practice. I know that there was a front page post a few weeks ago about how Cursor worked, and there was a short blurb about how sets of security prompts told the LLM to not do things like hard code API keys, but nothing on the training side.

This is great. pip-tools` is so valuable right now in helping mitigate these dependency tree issues. I'd love to see some form of support in core Python. I really hope this becomes pushed out, similar to how `pip` actually has a dependency resolver now. Relying on running `pip freeze` to create a quasi-lock is a horrible pattern for enterprise environments and for packages. I'm really looking forward to how this turns out, even though it's still in a proposal-type phase. `

Hah, yes. I used to work at a company that sold a popular DNA product. I built part of the GDPR data deletion pipeline. During my last week there, I submitted a request to delete my data from the systems. The final integration test!

I liked Scala and was excited about learning and using it when it was picking up steam many years back. Unfortunately, it felt like there wasn't as much traction, and Scala has been siloed into some niche domains like Spark. It's a bummer since it's so nice to write with.

I feel like Java has calmed down a bit and is more focused and thriving in its niche with enterprise systems. I recall the days when we believed that Java and the JVM could solve all of our problems.

I worked a lot with Spring and Spring Boot a while back and I can't help but smile when I think back to the discussions where a room full of us were arguing about beans.

Neat idea! If you can, someone figure out how to get Nextdoor animal-posters to join and participate, this would be really useful. Last time I saw a dog on the street, I pulled over to catch the dog, re-installed Nextdoor, made a post, and brought the dog to the local shelter. It's hard to beat not only the neighborhood aspect of Nextdoor, but also just the volume and mental "this is where it goes" vibe. What's not hard to beat about Nextdoor is the NIMBY and triggering comments so you're halfway there, hah!

This is pretty exciting. DuckDB is already proving to be a powerful tool in the industry.

Previously there was a strong trend of using simple S3-backed blob storage with Parquet and Athena for querying data lakes. It felt like things have gotten pretty complicated, but as integrations improve and Apache Iceberg gains maturity, I'm seeing a shift toward greater flexibility with less SaaS/tool sprawl in data lakes.

Personally I never found myself using my NFC payment watch. It felt like if I was venturing far enough to the store, I'm just going to bring my phone with me anyways. I wonder if this differs for areas that don't get as much suburban sprawl.

Very exciting! I've since left the Pebble ecosystem for Garmin/Withings but I have always had a very fond and memorable experience wearing Pebble watches.

Long-time lurker, first-time poster! So pretty excited to be sharing.

I really enjoy writing Python, but I’ve noticed a recurring pattern in organizations where it slowly turns from a productive tool into a frustrating mess. The more Python spreads across teams, the more fragmented it becomes—every group has its own way of using it, dependency management spirals out of control, and deployment workflows end up duct-taped together.

I wrote up my thoughts on why this happens, based on what I’ve seen in different companies. This is just my perspective, but I’d love to hear how others have tackled these challenges. Have you seen similar problems and how did you deal with them?