- Published
- Author
- Codemancers
about ActiveSupport::Notifications there is a railscasts on it http://railscasts.com/episodes/249-notifications-in-rails-3
At Codemancers, we believe every day is an opportunity to grow. This section is where our team shares bite-sized discoveries, technical breakthroughs and fascinating nuggets of wisdom we've stumbled upon in our work.
arr.reduceRightflash.now in rails, which allows you to have flash messages which does not persists across subsequent action unlike regular flash i.e it sets a flash message which is available only to the current action and not for next. http://api.rubyonrails.org/v5.1/classes/ActionDispatch/Flash/FlashHash.html#method-i-nowPost.none => #<ActiveRecord::Relation []>about:crashes url where one can see history of crash reports. Clicking on each crash report takes to mozilla website where one can see crash details"uglify-js": true this will run all the transformations, however you can use "useBuiltIns": true with that option to only include polyfills for your target browsersdocker-compose up -d --no-deps --build <service name> to do a zero downtime upgrade of services inside a running docker-compose stack.docker system prune -a will free up significant space on your hard disk if you have a lot of stopped docker containers and dangling volumes etcShowing page 38 of 42
AI is everywhere but it's unclear which investments will actually move your metrics and which are expensive experiments.
Most AI projects fail at the data layer. Pipelines, quality, access all need work before LLMs can deliver value.
Your engineers are shipping product. They don't have capacity to also become AI specialists with production-grade experience.
Aging, undocumented codebases make AI integration slow, risky, and expensive. They need to move first.