I didn’t expect deriving a calculation for how much a level in a biconical wizard’s tower narrows from the floor to the ceiling would be part of the prep for the final chapter of our #ttrpg campaign, but here we are. Using pythagoran triplets made it especially easy, but the cool part was having the simplicity of it all dawning on me in the shower. #UnexpectedUseOfMaths
Also looks like someone at the UK's Royal Astronomical Society set up a Mastodon account and is crafting custom posts for it, but it only has ~300 followers compared with their >50K on Twitter:
I see this all too often -- major public/nonprofit organizations set up shop here, but don't know how to best cross-link/promote it, so the accounts get kind of lost. If you care about #astronomy & like their work, give them a boost or follow :)
A zillion years ago, I read of an experiment where the intro programming class was divided in two. One part learned iteration first; the other learned recursion.
The recursion people found iteration confusing.
The iteration people found recursion confusing.
The story is probably too good to be true.
Merry Christmas & Happy Holidays!
.. and Ruby3.2 is released: https://www.ruby-lang.org/en/news/2022/12/25/ruby-3-2-0-released/
#Browsers, time to bring back the RSS/Atom feed icon displayed when a website has an RSS/Atom feed.
It's long past-due!
Faithless lead singer Maxi Jazz dies aged 65
Oh jeez not another one. This is so sad 😥
Is there an intrinsic reason why some of the `Enumerator` subclasses (e.g. `Enumerator::Chain`, `Enumerator::Product`) can’t implement `#next`? It feels surprising to have an `Enumerator` instance which doesn’t support external iteration, but I might be missing some obvious detail.
>> innings = Enumerator::Product.new(1..9, ['top', 'bottom'])
>> innings.is_a?(Enumerator)
=> true
>> Enumerator.instance_methods.include?(:next)
=> true
>> innings.next
(irb):in `<main>': undefined method `next'
@marick@social.oddly-influenced.dev Longer comments will be blog posts, like: https://www.crustofcode.com/bricolage/
I might also copy topics into the show notes, but I don't know what would work best.
So the other day, I took my soonish-to-be-passed-along team of mostly junior devs on a spin in functional(-ish) programming land (as far as Python allows it). Maybe, just maybe, they’ll start to see the filters, the maps, and the reduces hiding in all those list comprehensions they reach for by default.
Don’t get me wrong. Comprehensions are a useful abstraction. When you know what they abstract.
I love that everyone is basically wandering around Mastodon right now wearing their weirdest hashtags and trying to find their people.
"Are you #Apiarist ?"
"No, sorry, I'm #ArduinoMusic ."
#ArduinoMusic turns around.
"ANYBODY INTO BEES?"
A hand goes up in the back of the crowd.
"NICE."
★ Just published a new episode of Oddly Influenced: /Talking About Machines/: copier repair technicians and story-telling.
Bonus: a dumb thing I did once.
Symmathecist in the medium of software, avid mob programmer, perpetual journeyman, moderately mad horse owner, and a tabletop RPG gamemaster and designer.