mcc

The way I want to go about writing code is by building up a library of things I've done before and copying the things I've done before into new projects. The most straightforward way to do this is to look through your own previous source repos.

I am kinda badly fucked on doing this by the fact that Bitbucket banned all my repos for the crime of using hg circa 2020, and then this year I started moving the repos I had just finished moving to github to codeberg

Dec 19 at 8:44pmWeb
Show threadmccDec 19
Oh another big problem here is there's no "search all my repos for this string" function on codeberg last I checked, so maybe I need to write my own lookaside index? It's really shocking how many small coding projects I'm forced into by ceasing use of any service that uses or sells "generative AI"
Show thread∴ esoterik ∴Dec 19
@mcc yeah, i never really recovered from losing bitbucket. rip.
Show threadAMTDec 19
@mcc I somehow suck at this. Whenever I see my old code to harvest in a newer project, I hate it and end up rewriting it and the cycle repeats. I can’t believe the naïveté of past me.
Show threadMarius GedminasDec 19

@mcc I ended up with a ~/projects/ with symlinks to all of my repos, because my ~/src/ is full of clones of random stuff and sometimes I want to ripgrep just through my own stuff.

The symlinks mean I need to explicitly append */ to the rg command line but eh.

Show threadmccDec 19

@mgedmin I have a very intentional, careful organization system but it's spread across multiple computers

Github lets you search across your repos but codeberg doesn't :(

Show threadalan Dec 19

@mcc

The more AI slop drowns the web, the happier I am that I keep a grimoire to copy/paste from. It feel like that's going to be more and more important going forward.