I am listening to the @ttforall podcast with Jimmy Koppel on which parts of CS theory all software engineers should learn about (see also his blog post from 2021 on why programmers should(n't) learn theory). Now I'm curious to learn which parts of "theory" you think are the most useful for a software engineer.

Please boost this so this also finds an audience beyond the types community!

#SoftwareEngineering #Education #TypeTheory #ProgramVerification #AbstractInterpretation #ProofAssistant #HoareLogic #ModelChecking #SMT #OperationalSemantics #CategoryTheory #DomainTheory

#CallForPapers #EXPRESS / #SOS 2023 (Combined Workshops on Expressiveness in Concurrency and Structural Operational Semantics) "aims at bringing together researchers interested in the formal semantics of systems and programming concepts, and in the expressiveness of computational models" https://express-sos.github.io/ #concurrency #operationalSemantics #TCS

@martensitingale I may have painted myself into a corner such that I'm going to have to write a reduction relation that operates on the entire (top-level) program text, so I can pattern-match function bodies out of it rather than building an environment to hold them... this is not the kind of context-with-holes I would have liked #operationalsemantics #mistakes

because this language doesn't have lambdas, and I'm using a relatively shallow grammar for it, substitution-based reduction of function application gets... interesting #operationalsemantics

I want something bigsteppy to avoid specifying evaluation order for different elements in a vector to enable optimization #operationalsemantics

value domain consists of tuples, vectors, ints, bools, where vectors can only hold ints/bools #operationalsemantics

bouta maybe livetoot writing an #operationalsemantics