Conversation

Notices

1. Embed this notice
   feld (feld@bikeshed.party)'s status on Monday, 05-Jun-2023 22:37:24 JST feld
   I honestly don't understand why so much functionality in huge, well-funded open source projects just goes completely undocumented.
   
   Today's lesson: Chef, :delayed_action
   
   delayed_action is not documented, but if you have something you want to *always* run at the end of the Chef client run and you have no obvious reason to do this with a :notifies, you can just do
   
   foo 'bar' do
   action: :nothing
   delayed_action :run
   end
   
   and it will execute your action at the very end
   
   https://www.rubydoc.info/gems/chef/Chef/Resource:delayed_action
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Monday, 05-Jun-2023 23:10:31 JST Alex Gleason

     in reply to
     @feld Ruby and Rails specifically has some of the worst documentation I've ever seen. It's like a fraternal cult where you pray to the blood god to write Ruby code.
   • Embed this notice
     node (node@poa.st)'s status on Tuesday, 06-Jun-2023 21:52:21 JST node

     in reply to

     • Alex Gleason
     @alex @feld DUDE I KNOW. What the fuck is wrong with the Ruby & Rails docs? guides.rubyonrails.org is OK. But if you want to start slingin' some slick Ruby code, and if you'd docs to show you how to call certain methods... Good luck. It's a nightmare. And yet there's all these Ruby nerds out there who talk about metaprogramming and stuff like they know some great secret and are just keeping it to themselves.
     Alex Gleason likes this.