Kalabasa

Nothing as heavy as the above but here's my small anecdote:

I was putting off security updates on my npm dependencies in my personal project because it's a pain to migrate if the upgrade isn't trivial. It's not a critical website, but I run npm scripts locally, and dependabot is telling me things.

I told Claude Code to make a migration plan to upgrade my deps. It updated code for breaking changes (there were API changes, not all fixes are minor version upgrades) and replaced abandoned unmaintained packages with newer ones or built-in Node APIs. It was all done in an hour. I even got unit tests out of it to test for regressions.

In this case, I was able to skip the boring task of maintaining code and applying routine updates and focus on the fun feature stuff.

Yep. I was looking for a tiling/scrolling window manager for MacOS. Setting it up, learning the configs, reading github issues, learning the key bindings take time. Then I gave up and it was done in 2 days with Claude Code to my preferences. No intention to polish up and publish this tool.

In video games or graphics, dithering can be an alternative to transparency. It's more performant too. I see this a lot in handheld consoles.

As screen resolution and density increases, dithering could even replace transparency as long as you don't look close enough.

I think it's pointing to a version of the repo, so npm installs the package.json of that version of the repo.

Object property access i guess. Like

myObj["myProperty"]

If it's a function then it could be invoked,

myObj["myProperty"]()

If the key was a symbol,

myObj[theSymbol]()

Shopify has an esports team called Shopify Rebellion

I think this was what Google Plus was going for.

Instead of friend graphs (mutual) or follower graphs (directed edges), they had Circles.

Circles sound a lot like group chats.

I guess "social circles" may be a better way to model social relationships than follower graphs.

Yep, there are a lot of layers and compositing operations (maybe more than necessary?). I suppose it could be simplified further.

Author here: Definitely cherry picked ;)

I did deliberately pick some "bad" examples like the blue+green image, and other multicolor images.

I wanted to add an upload function so people could test any image, then i realised I'd have to implement the compression/hashing in the client. Maybe i should!

Learned about the heart today! Thank you!

I wonder what other types of cells / tissues can be simulated by cellular automata?

Yep, a lot of headline readers here.

It's just a very advanced autocomplete, completely integrated into the internal codebase and IDE. You can read this on the research blog (maybe if everyone just read the blog).

e.g.

I start typing `var notificationManager`

It would suggest `= (Notification Manager) context.getSystemService(NOTIFICATION_MANAGER);`

If you've done Android then you know how much boilerplate there is to suggest.

I press Ctrl+Enter or something to accept the suggestion.

Voila, more than 50% of that code was written by AI.

> blindly committing AI code

Even before AI, no one blindly accepts autocomplete.

A lot of headline-readers seem to imagine some sort of semi-autonomous or prompt based code generation that writes whole blocks of code to then be blindly accepted by engineers.