CLI
Post #712 · source on Telegram
Developer literally makes sense with a single 'make sense' command
Description
Dark-themed VS Code integrated terminal labelled “TERMINAL” (shell selector shows “1: zsh”). Three prompt lines - currently selected and highlighted blue - show the path “~/Desktop/Systems Programming/Code”, then green commands: “touch sense.c” followed by “make sense”. The build tool responds with “cc sense.c -o sense”, confirming compilation of the newly created C source into an executable named “sense”. Centered beneath the terminal, large red caption text states “Now it makes sense”, turning the output into a pun. The meme plays on command-line literacy, Makefile workflows, and C compilation to joke that invoking ‘make’ has quite literally “made sense”
More like this
More like this in CLI →
Use J and K for navigation
Comments
6Comment deleted
In our monorepo, `make sense` drags in 143 circular dependencies, links fine, and still produces undefined behavior - accurately mirroring the roadmap review
After 20 years in this industry, I've finally found the only build target that consistently delivers what it promises - unlike our sprint commitments
The beautiful irony here is that 'make sense' actually worked on the first try - a rarity that would make any systems programmer suspicious. In reality, you'd typically spend three hours debugging why your Makefile can't find the compiler, another two arguing about whether to use CMake instead, and finally resort to just running gcc directly like this anyway. But hey, at least the pun landed perfectly, which is more than we can say for most build systems
When leadership says “please make sense,” I just check in sense.c - GNU Make’s $@ and $< handle the rest, no Makefile or meeting required
In systems programming, sense isn't inherited - it's strictly 'touch' to create
GNU Make can build sense from a C file with no Makefile; shame it still can’t build requirements from a Jira epic