Lenin was 47 in 1917
(\r (frequencies "strawberry"))
the 'I' in LLM stands for intelligence
lots of onions cut in rings as they resemble parentheses the most
death by specificity is a thing...
HTTPServletRequest has a fuckton of methods but 90% of them could be eliminated if one treated the data as a simple fucking map instead of creating 4 methods for each key in every record of your schemas.
personally I'd sum it up this way: it is usually enough to abstract two parts of your code: the repetitive stuff and the stuff that can be separated from external dependencies like db or network. That should be enough to ensure readability and that you can test it properly and not have to deal with rewriting half your codebase when you decide to change an external dependency.
Funny how he is actually now a fan of Clojure yet the examples in his book are actually full of mutating data and side effects. And Rich Hickey also stressed that tests are no silver bullet.
tfw I recently worked on a side project where I was too lazy to change the log level but not sloppy enough to use raw printf so I'd just throw stuff into info and then remove the statements once I solved my issue
Good luck to AI-based legal "solutions" startups, hope they and their customers are generously insured to cover for the fallout of such blatantly ignorant stupidity that completely discards our current subject matter expertise, which clearly shows that the error rate is too high, while you're either right about the law or you're not.
...from people who seem to refuse to install paredit or coloring plugins for either? ps lisp syntax ftw, it's a feature!
Notesnook ftw