ENV.fetch('CONFIG_PATH')
.then { File.read(_1, encoding: 'KOI8-U')
.then { JSON.parse(_1, symbolize_names: true) }
.dig('metadata', 'created_at')
.then { Time.new(_1, in: CURRENT_TIMEZONE) }
(JSON.method(:parse) >> method(:puts)).call("[1, 2, 3]")
method(:>).call(a, b)
a.method(:>).call(b)
if_(stories == 1, ()=> chance(2/3, ()=> [1, "Pizza Hut"]))
var points = range(resolution).map(
i => ({x, y: y - (i * height) / resolution})
)
I don't think this corresponds to my experience.
I am working as a staff engineer in big production codebases (with all the traits of those: some code is good, some is bad, some is unrecognizable legacy, sometimes we are in a hurry and write awful code, sometimes we have time for refactoring etc.)
And my observations about the logic and perception of the features are drawn from the practice of code reviews, mentoring new people, and discussing ways of solving tasks in this environment. Obviously, I am frequently a driver of new code practices, but I am also trying to be a good person and a good colleague and notice how comfortable people are with various parts of the codebase, various idioms, etc.
One of the main topics of this article series is uncovering the language's logic and intuitions (to stop perceiving it as a "bag of random syntactic features you need to learn or should guess") and using those intuitions for code that is, yes, better for the reader, but the code that can be created in a quickly-changing production environment and rewritten fearlessly.