Show newer

Listening to a webdev podcast I enjoy, whenever the show runners bring up Typescript (all the time), I mentally substitute specs.

Cloth over-masks dramatically reduce glasses-fogging

Finally used fnil in : to extend a function to support nil case without NPE-ing you! My use: a function that needs to handle strings, collections, or nil, and doesn't know which it will get.

I oversaw the creation of a app for room five years ago. It has been good, and has been in heavy use since then -- but suddenly has some issues, probably from logic -- and I desperately want a a la .

The data coming through the pipeline on one view was missing a crucial piece. It was sweet to be able to add it to the back-end function that is gathering the data, evaluate the form, and boom! It was there for my front-end view as soon as I used my usual endpoint.

Every time I have to resort to using a string selector in , I feel dirty.

I have my to both a file and database. It appears to just STOP after a few minutes of operation -- but we have no idea why. Restarting fixes it for a few minutes. WHY?

RT @fndriven
To Dos:
- Hammock time and think about ...
- ... how to create a XTDB query (Datalog) programmatically

RT @fndriven
In the past weeks I had fun with biff. It taught me a ton abt backend programming. I upgraded my project several times with no problems. Only problem was me trying to fight the framework bc I'm only used to do SPAs. Time to remove the printlns. biffweb.com/

I have had several problems lately where I never come to understand a "why?" but have a good work-around.

In reagent (react), why was stuff having bizarre browser focus errors if I PASSED a value from my front-end DB, but fine if I gave it the info to retrieve that value itself?

VSCode Cursive seems to roll with the "one repl window to rule them all" approach on full-stack projects, with changes by context. I've seen recent Cider has that option, too, but I much prefer having separate buffers for my CLJ and CLJS repls. Who prefers the unitary version and why?

In , select-keys against a set instead of a vector must be better or worse. Does using a set actually help? `(select-keys {:foo 1} #{:foo})`

Logic: "if it's not an atom, make it one." Note that `atom?` is not in core.

I'm not ashamed but can anyone think of more elegant way to do this?

Show older
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.