Notes on code, text, and war. Week 2: If code is text, then what?
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
At this point in time, I believe that the West preaches Russia religion, and its relationship with Russia is close to that of ancient people's attitude towards wrathful gods.| zverok.space
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
I don't build systems. I imagine them, then write them.| 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
I write to Ruby community in days of war Russia leads against my country.| zverok.space
The transcript of the talk given at EuRuKo'24| zverok.space
On making the Ruby Changes, and some consequences of this work| zverok.space
On a new approach to implement that long-envied feature. In Elixir1, there is a pipeline operator that allows rewriting this code: a(b(c(d))) into this: d|>c()|>b()|>a() which helps to write code in clearly visible “pipelines” corresponding to the order in which data processing is happening. The concept is so captivating that many languages that don’t have an operator like this have either language proposals or libraries that implement one. Ruby is no exception. This is a story of my ta...| zverok's space
Comments| lobste.rs
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
Silent changes in payment methods on big creator funding platforms raise some unpleasant questions.| 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
I wrote the analysis of “useless sugar” features of Ruby for two months, and I regret nothing.| zverok.space
A diary of preparing Ruby 3.3's annotated changelog throughout the December of 2023.| zverok.space
I don't build systems. I imagine them, then write them.| 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
To not become "old news," I write to the Ruby community in days of war Russia leads against my country.| zverok.space
Final part of adventures in understanding, explaining, and challenging the facts that should be obvious.| zverok.space
