I continue to work on my #OpenTelemetry demo. Its main idea is to showcase traces across various technology stacks, including #asynchronous communication via an #MQTT queue. This week, I added a couple of components and changed the #architecture. Here are some noteworthy learnings; note that some of them might not be entirely connected to @opentelemetry
ruby drama on stage with Cristian Pianas and Anatoly Mikhaylov. @tenderlove most famous pictures made it to the presentation as the epitome of the cool ruby developer. well deserved!
next speaker up, the creator of the Short Ruby newsletter, a teacher and mentor, a polymorphic software engineer as he calls himself: @lucianghinda Lucian Ghinda at Ruby Day!
Got my first development environment (Jekyll website) running in NixOS on my Framework laptop using devenv. That makes this my first successful dev environment in nix. :) Nice work @domenkozar!
I've been job hunting full time for 2 weeks now. It's exhausting! If you know of any place looking for a Senior/Staff Software Engineer, I have 15 years experience working with Ruby, Rails, and Javascript. More recently the Node.js stuff has been in React. I'm also interested in Rust, Go, and Elixir. Any leads are appreciated!! #ruby#rails#rubyonrails#RubyHire#fedihire#getfedihired
The developer of LastLogin.io has implemented FedCM on his end, but he needs the help of a Discourse plugin developer to test the complete login pipeline with his own community forum.
If I had a two pence piece for every time @andycroll's One Ruby Thing acted as my second brain, I'd be able to spend all day in a Brighton arcade on the 2p machines.
The next #meetup is this Thursday at New Relic. I will be away at #RubyKaigi but I'm so thrilled to see the new organizers making this happen monthly! We already have host companies offering space for the future events.
This year, @rubycentral announced that 2025 will be the last @railsconf. While I’m sad to lose a favorite Ruby conference, it’s for the best. The Ruby Central team will be able to focus on their core mission: supporting the Ruby language.
Ever find a tutorial that was broken is some subtle but deeply fundamental way?
Ever WRITE a tutorial that was broken in some subtle but deeply fundmental way?
I just released RunDOC 2.0. A tool for writing tutorials that run and embed the results into a markdown document. Check it out https://github.com/zombocom/rundoc
Current status: I opened about 100 links to articles and threads from Google results comparing #ruby, #golang and #rustlang and I'm planning to read them 🫠
(no, I'm not really considering Go, mostly just trying to convince myself that I'm not making a mistake starting to learn Rust and not Go 🦀😛)
He is a dynamic #Rails & #Ruby core team member and Sr Staff Engineer at @Shopify! When not innovating in tech, he loves whipping up culinary delights, cuddling with feline friends, and crafting quirky software.
It's so annoying to see developers calling failing tests "flaky".
Last week I found a factory that assigned a random age to a user instance, so no wonder a test that used the age in some bit of logic failed sometimes. That's not a "flaky test", that's a bug in the factory.
Today I saw a date parser bug be called a "flaky test". It was written on the 21st of April and worked fine until it began to fail today, the 1st of May.
"Tests provide the only reliable documentation of design. The story they tell remains true long after paper documents become obsolete and human memory fails. Write your tests as if you expect your future self to have amnesia. Remember that you will forget; write tests that remind you of the story once you have." (Sandi Metz, "Practical Object-Oriented Design")
I really want to write something bigger in #RustLang 🦀, but I just can't think of anything else beyond that regexp matching where I'd need that raw speed (where #Ruby is not enough), except maybe an indexer for an AppView, but I kinda have too many things open atm to start working on that… 🤔