Notesnook ftw
I am working on fedi software that is hoping to allow Kodi, Plex and Popcorn Time get rid of IMDb/TMDB dependency. Dm me if you’re skilled in SvelteKit and/or Go, especially the Fiber framework, or machine learning with Rust and willing to contribute.
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
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.
we had a plenty of more deterministic tools for parsing human readable text to machine-readable long before llms
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
fr the system is in such a deep terminal crisis that talking to people in their 20s feels like talking to pensioners since in countries like the US or UK the life expectancy is declining due to not being able to afford healthy food, stressful and precarious work, mental health crisis and addictions, worsening healthcare, climate change, moldy cramped housing, proliferation of larger and thus more dangerous cars, new zoonoses etc. etc.
typescript is a linter
wonder when Rust will saturate it’s niche as a C/C++ replacement, I’d guess 3-6 years would be when we might start to see some stabilization.
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.
…made using the arguably the most criminally environmentally disastrous tech we’ve invented in the past few decades. How ironic!
Why does it have to always be a hype that is a literal kick in the eye of gamers? Previously it was shitcoins, now it’s hallucination engines… I’m afraid what’s up next.
Somewhat useful with (neo)vim, where it’s (however tiny af) context window spans every open buffer