there were some things i ddn't knew about raspberry pis:
"Linux runs on that ARM CPU, we know that, but we might be surprised to learn that Linux on this device is only a second class citizen. The GPU cores run a real time operating system called ThreadX. This operating system is closed source and rules the system without the open source Linux Kernel being aware of it."
and guess who bought the ThreadX operating system last april?
Nice to see git addressing some of command line complexities. "checkout" command is way complexicated, the new "switch" and "restore" make sense. https://github.blog/2019-08-16-highlights-from-git-2-23/
If you are looking for a new job coding in Ruby remotely... we are looking for people in the early stages of their careers, as well as more experienced.
Feel free to DM/ask me about it, I've been the latest dev to join the (products) team.
Hey Ruby.social! I'm looking for Ruby-related blogs to follow. The ones I found on https://github.com/planetruby/awesome-blogs are pretty outdated or even not existing anymore. Thanks
Finally launched Faktory Pro, the commercial sibling of Faktory, my background job system for all programming languages.
If you want Sidekiq for Python, JS, PHP, Elixir, Rust or Go, this is your jam.
🏭 🏭 🏭
What I would like from a tool like this would be:
- To know if a build has failed because tests that have been marked as flakies before. Being new to a codebase makes you wonder on every failing spec if its a false positive or not.
- To know which flakies have the most occurrences (and prioritize tackling those over the rest if I have time or just too many)
And I think the best way to interact with the developer would be through an integration with Github/Gitlab/etc... on every PR.
On ever big codebase flaky tests are part of the deal, and usually don't have enough attention or even workflow/tools to deal with them.
I wonder why I haven't found any automated test services (CircleCI/Travis/BuildKite/SemaphoreCI/etc...) with some kind of feature/help to deal with those 🤔
The trickiest part seems to be how to identify/reference them as lines/files/names change across time & branches.
For those geeks that love data, after realizing the huge benefits of powermeter usage on cycling... I tried https://www.stryd.com
Surprisingly the numbers are very consistent with the ones from the bike (threshold power with the 3-9 min test).
It might not help much with pacing on irregular trails, but on road or any steady gravel path its really great. Having normalized power is awesome to measure/pace using laps (segments) on long distances, or on a vertical kilometer.
It's my 5th come back to running and the best in terms of injuries/blisters/soreness, and it might be because:
- I didn't try new shoes, just used the same models that worked for me last time: Sportiva Ultra Raptor & Asics Nimbus.
- I used custom insoles, because foot soles aren't usually flat and distributing pressure is important. Just 60€
- For the first time in my life I've done some core at the gym for an entire year.
- Running on asphalt I focus on cadence and proper step technique.
I'm back to running on asphalt and trails, just for having fun with my girl and complement winter strength training.
We did Sanabria's 3 stage Trail with incredible landscapes http://ultrasanabria.es, and now I think its the second most beautiful place I've visited, obviously Asturias is first 😏
Ruby web dev @ BeBanjo, cycling geek and rookie farmer @ Noreña (Spain)
A Mastodon instance for Rubyists & friends