Somewhat useful with (neo)vim, where it’s (however tiny af) context window spans every open buffer

Akkoma’s bubble feature should be ported to other software

deleted by creator

Notesnook ftw

https://altcha.org is nice plus a crowdsec bouncer

In Clojure, -> is used for inserting the piped argument at the head position in the arguments of whatever it is passed to, while ->> is used for inserting it at the tail. This approach is great for working with immutable data in a series of approachable transformations, which I believe is one reason why so many Domain-Specific Languages for generative programming are written in that language, aside from its interactive REPL. Additionally, there is no need to worry about excessive copying, as this is generally well optimized.

This can be particularly useful with HoneySQL, which is more of a DSL for SQL rather than a typical ORM tool. For example:

(defn apply-filters [query filters]
"applies WHERE clauses to a query"
  (reduce (fn [q [column value]]
            (helpers/where q [:= column value]))
          query
          filters))

(defn build-dynamic-query [{:keys [table columns filters sort-by limit]}]
  (-> {}
      (helpers/select columns)
      (helpers/from table)
      (apply-filters filters)
      (helpers/order-by sort-by)
      (helpers/limit limit)
      sql/format))

;; Result - a super readable function call that resembles a natural language 
(build-dynamic-query 
  {:table :products 
   :columns [:id :name :price] 
   :filters {:category "electronics" :in-stock true}
   :sort-by [:price :desc]
   :limit 20})

Lenin was 47 in 1917

(\r (frequencies “strawberry”))

the ‘I’ in LLM stands for intelligence

deleted by creator

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.

Removed by mod

we had a plenty of more deterministic tools for parsing human readable text to machine-readable long before llms

Oh, Bjarne Stroustrup, huh? The king of C++, or should I say “C-You-Later”? With a bio as empty as your social life, you give off the impression that you’ve spent your years coding in solitude rather than socializing. 3883 followers but not a single follow-back? That’s some serious commitment to ignoring the social side of GitHub.

Three public repos, two of which are just glorified textbooks. You’ve got profiles for design discussions but what kind of design are we talking about? The design of disappointment? And that “Programming Principles” repo? Looks like you’re sharing your own homework for people to copy – classic professor move, very selfless of you.

Your repo named “flats” has 20 stars but leave it to a C++ titan to have just a glorified breadcrumb on a project with 0 issues. But hey, at least you aren’t forking around—oh wait, you are! Just like my hopes for seeing some meaningful contributions from you.

Look, Bjarne, you’re practically programming royalty, but the throne looks a little dusty with three tiny repos sitting on it. Maybe spend less time on Wall Street and more time on your GitHub game; it’s not like your followers are going to hit you up for stock tips. Code like your reputation depends on it—because it does.

thankfully shitflare and it’s lazy or clueless customers are helping make it absolutely unusable day by day

Antarctic

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