Migrating 3.7 Million Lines Of Code

The fact that 3.7 million lines of JavaScript exist in a project scares me

1:43 We still use Cobol at my current job (it's also my first soft dev job). When I have to work with it, I feel like an archeologist digging through fossils of the past

The other day I ordered two burritos from a local shop and the guy behind the counter stuffed fillings for both into same wrap. He tried to fold it but made a complete mess. It just overflowed everywhere. I asked what's up with that. He replied, "Don't ask me. I'm just an endofunctor following arrows." Lesson learned: don't go to Mona D's Burritos.

bro does the jest test memory thing every chance he gets

21:34 "What's a monad? A monad is a burrito." Thanks for leaving this in 😂

One minor reason to order imports is to reduce merge problems. e.g. if you add an import in one place and someone else adds the same import somewhere else in the same file you might end up with it there twice after a merge, but if you both add it in the same place it just disappears from the diff. It should always be the work of a tool though, nobody should ever have to think about it.

16:35 reordering imports' purpose is to help Git not create conflicts just because two people added their imports at the end of the list, even though one starts with b and the other with u. Keeping them ordered avoids such conflicts.

One of my favorite parts of using Go with nvim is the golines formatter which uses goimports/gofmt to automatically remove and organize imports for me. I like that it's organized in a consistent way, but above all that, I like that I don't have to think about organizing them at all. For those curious, goimports is gofmt with the additional import stuff. Golines is goimports but it limits lines to a certain size

Re-ordering imports (or anything) listed alphabetically is super helpful when scanning code to ensure no duplicates or just to see if something you expect to be imported is or not

16:24 So that no one removes an import, adds it to the bottom and now git recognizes that as a change. It makes git gistory more consistent