Last time, I've highlighted "treating code as text" idea as something that I want dedicate a few posts to. Let's talk in generalities some more this time.| zverok.space
Writing texts is the most useful and fruitful metaphor for software development. Intro to a series of posts on theoretical and practical implications of it. And something about war.| zverok.space
A view from a school in Zaporizhzhia, Ukraine| snyder.substack.com
The transcript of the talk given at EuRuKo'24| zverok.space
On making the Ruby Changes, and some consequences of this work| zverok.space
Some thoughts on how programming’s unlikely relations to poetry, and some implications of those relations| zverok.space
A “stories-first” approach to refactor a small yet complicated piece of business code| zverok.space
Understanding the core class design and usage via its evolution| zverok.space
Episode 01 of studying Ruby programming language design decisions, how they evolved with time, and how they look in a wider context.| zverok.space
This winter, Ukraine’s military is visibly running on fumes, as recent reporting shows M109 Paladin artillery outside Bakhmut receiving only smoke shells| War on the Rocks
I wrote the analysis of “useless sugar” features of Ruby for two months, and I regret nothing.| zverok.space
Or, about the virtue of exactly one phrase.| zverok.space
How the small syntactical simplification of allowing to omit values when they names are the same as keys affects code design and structure.| zverok.space
The final part of the article about pattern matching in Ruby, putting it in a broader context of the industry state, possible future usages, and a general effect on the language design.| zverok.space
They said “...just switch to the language that already has it, would you?”| zverok.space
...and what might be interesting about it| zverok.space
...that were written in a military training camp and accidentally grew to 5k words| zverok.space