Teaching Programming Languages by Experimental and Adversarial Thinking: https://cs.brown.edu/~sk/Publications/Papers/Published/pkf-teach-pl-exp-adv-think/
A fascinating approach to teaching programming paradigms. Implement different language semantics in the same syntax, and ask students to write programs that distinguish between them!
miniblog.
Related Posts
What's the best string representation of a function? Comparing with other PLs:
Python: <function __main__.add_one()>
JS: [Function: addOne]
Clojure: #function[user/add-one]
Scheme: #<procedure add-one (x)>
I'm currently thinking about <fun add_one() foo.gdn:123>
I'm adding uptime data to my personal LLM bot. Does this information belong in the system prompt?
That was my initial plan, but I'm thinking that a tool would be better. Tools let me see information provenance ("queried the uptime tool").
There's also a small caching benefit.
There are docs resources like https://diataxis.fr/ that categorise documents based on format and intended audience.
They don't say where you should start, or what order you should write docs.
I'm currently thinking README > reference > tutorial > how-tos. Agree/disagree?


