rubber duck typing

Adam Chlipala, a respected figure in formal verification, writes: Code as we know it will become a throw-away automatic byproduct of the real long-lived artifacts, joining formats like assembly language that we mostly think of in that way today. … economic

In the previous post I discussed how LLM affect education in software engineering.

The programming education is finally dying for real!

I view my projects through the system engineering lens, employing system and ontological thinking, stakeholder and requirement analysis, complexity management techniques, and so on.

This is the second post in the series dedicated to ontologies in systems engineering: Perdurantism in systems engineering standards Vico, Descartes, and decay of knowledge in software Making is knowing, it makes things intelligible.

There seem to be at least two problems with the inaccessibility of mental states.

This is the first post in the series about ontologies in systems engineering: Perdurantism in systems engineering standards Vico, Descartes, and decay of knowledge in software Engineers need a way to talk about the world.

In the previous post on compiler correctness we asked: how do you know a compiler has a bug?

Plato impresses me not just with his ideas, but by his writing craftsmanship.

This post explores the notions of bug identity, bug identification applied to compilers.

I love being efficient and there is nothing like a feeling of wholesomeness at the end of the day when you realize that you have not wasted it.

A couple years ago I have started to write my second book, whose main point is to teach students elements of computer system design, largely speaking.

The time has come for me to work in Europe again.

In this post we are going to explore how the notion of function loses its significance as an abstracted module of program logic when we compile a higher level imperative language to the assembly code.

I am not a naturally good writer.

Covariance, invariance, and contravariance are concepts many students have difficulties to grasp.

There are many things I wish I knew when I started my journey as a programming student.

My personal experience with Coq proof assistant over the last years made me think, that such tool, as exotic and niché as it might seem, is invaluable in a programmer's education.

Can we put a sphere with a bigger radius inside of a smaller one so that it would be fully contained?

CompCert is a certified C compiler written in Coq.

I found a beautiful explanation about what essential property does the associativity capture: You can think of each element of a monoid as having two sides.

I have been lucky to be exposed to some very good teachers with different approaches as well as collect my own experience: I am teaching C/Assembly since around 2009.

Recently I've been lucky to spend a couple of days in Belgium.

IT folks are prone to prejudices, as we all are.

Proving dependent equalities in Coq is boring, but quite frequently done.

Our minds use the notions of cause and consequences all the time.

Sometimes you just want to prove that nasty ~ T = U for some types T and U.