The use of Claude Code with my day job has been quite different. In my day job, I understand the code and review it carefully, and CC has been a big help.

I like this take. I feel like a significant portion of building out a web app (to give an example) is boilerplate. One benefit of (e.g., younger) developers using AI to mock out web apps might be to figure out how to get past that boilerplate to something more concise and productive, which is not necessarily an easy thing to get right.

In other words, perhaps the new AI tools will facilitate an understanding of what can safely be generalized from 30 years of actual code.

> People who stress over code style, linting rules, or other minutia are insane weirdos

I feel like programmatically enforced linting is like keeping a shared house clean. Suppose you live in a house with roommates. You wipe off the counters, you clean up after yourself, you put dishes in the dishwasher, so that the house is tidy and pleasant. If there's a lint or style rule that requires judgment and is hard to enforce programmatically, perhaps better left as an occasional PR comment.

Programatically enforced linting also has the benefit of removing degrees of freedom that aren't very important and don't merit getting bogged down about.

https://digraph.app/

https://github.com/emwalker/digraph

If you can crowdsource the indexing, you get yourself a manually curated search engine with a nice topic graph that can be traversed. A piece of this puzzle that hasn't been tackled yet is a reputation system to keep the signal-to-noise ratio high and deal with spam.

> What’s an example use case of where you use that system to find a link?

An example use case is that I come across some interesting long-form article on a topic I'm following, e.g., Shackleton's expedition, that's published on a nice website and that I don't have time to read. I can just drop the link in the right topic and get back to it without too much difficulty. Or that's the hope, anyway. (Doesn't always work out that like that.)

Another thing I'm interested in is what the topic structure ends up looking like as it's more fully fleshed out. So sometimes I'll drop in random links even if they're not that interesting, just to build out the topics.

It keeps a history of every change to the graph in Git, so one day you could potentially implement some form of time travel and see what the graph looked like at an earlier point in time without too much difficulty.

I have used the app every day for years. I feel like there's something promising there that is of general interest, but I have not figured out how to communicate the value.

After tackling the refactoring of a complex Rails app that has a rules processing engine implemented on top of ActiveRecord, the true cost of Ruby's lack of static typing has become apparent to me. It's clear now that you can get a web app up and running quickly in a framework like Rails (as one example of a convenient, low-friction framework). But once you need to turn it inside out and make significant changes to the implementation, you're walking on egg shells and relying on previous devs to have built out good test coverage. A web app written in Rust would be easier to refactor in important ways at this point in the life of the app. It is clear there was a cost to using Ruby, but also that it was deferred.

On the backend, at least, Rust would be a significant improvement over Ruby, for example, once a business has gotten past the initial prototyping phase. I've spent years in Ruby development, and the duck typing makes refactoring a production system scary and drama-prone. No matter how carefully you proceed, there will be gaps in test coverage, and you'll regularly see new bugs in production from the refactoring work that would never happen in a typed language. I would gladly work in Rust over Ruby in a web development context. (Although my preferences lean towards Rust, there are no doubt many other typed languages that could do a good job here as well.)

https://digraph.app/

Agreed. It's like being able to call up a map on Google Maps for an area that you're already familiar with. The map can help you remember things about the area and terrain that you might not have recalled right away. A kind of cognitive aid.

https://blog.digraph.app/2020-06-13-democratization-of-searc...

This will import Wikipedia's serious flaws. But I'm hopefully that they can gradually be mitigated.