Great article and really great pragmatism. Heroku was a pioneer in excellent software design and development, more than they may ever get credit for. It’s not a surprise to me that the author worked at Heroku and thinks like a pro.
I love Ruby. I love rails. I love gems. I love bundler. I’m not sure why the Ruby community is so much stronger at simple software design than any other I’ve been a part of.
I spend most of my time in Python right now, and it’s fine, but I don’t love it like I loved Ruby. The only reason I have to be in Python is because the world of data engineering chose Python as their language. That basically always puts me in the unfortunate situation of having to choose between getting a project/task done using a Python library, or have to write it more by hand in Ruby, and you know which one wins :(.
As far as I can tell, there’s no reason Ruby couldn’t be the language of choice for data engineering, it’s just that no one has spent the time to make it that yet. I wish I could commit my life to that, I would, if nothing else mattered.
Tl;dr, author’s point of view is great, I bet their control plane is great; Ruby is fantastic; and someone should go make a pandas for Ruby and name it something even better like raccoons!
Daniel has a few gems in this blog post and we tried to italicize some of them. My favorite one is around "There is no code without a theory of testing."
"If you have 100% branch coverage, it doesn't mean you've covered all the cases. But it does mean that, whenever an obscure fault is understood in production, or even merely observed in development, there is an incremental path to add it to the base of knowledge in the tests: there are no spans of code with no test model."
Also not surprised to find out that Ozgun from Citus is behind these strong principles! :)
Yea I mean that can basically be assessed as a paradox: how can you possibly write a line of code that you don’t know how to validate its correctness!?
I love Ruby. I love rails. I love gems. I love bundler. I’m not sure why the Ruby community is so much stronger at simple software design than any other I’ve been a part of.
I spend most of my time in Python right now, and it’s fine, but I don’t love it like I loved Ruby. The only reason I have to be in Python is because the world of data engineering chose Python as their language. That basically always puts me in the unfortunate situation of having to choose between getting a project/task done using a Python library, or have to write it more by hand in Ruby, and you know which one wins :(.
As far as I can tell, there’s no reason Ruby couldn’t be the language of choice for data engineering, it’s just that no one has spent the time to make it that yet. I wish I could commit my life to that, I would, if nothing else mattered.
Tl;dr, author’s point of view is great, I bet their control plane is great; Ruby is fantastic; and someone should go make a pandas for Ruby and name it something even better like raccoons!