Articles related to Antipattern from the team that helps B2C companies build and defend revenue with AI.
#post-dont-be-sloppy-with-ruby-env { background-image: url(/blog/content/images/2016/04/circuits.svg); background-repeat: no-repeat; background-position: 50% -600px; background-size: 150%; } This is part of our antipatterns series. Ouch! Updated for 2017! Ask yourself why you're using Hash#[]. It is is a great way to introduce silent bugs into your app. Use Hash#fetch
Read moreThis is part of our antipatterns and cloud security series. Per an official Ruby CVE in 2013: JSON.load should never be given input from unknown sources. If you are processing JSON from an unknown source, always use JSON.parse. I feel like that should be shouted from the rooftops.
Read moreThis is part of our antipatterns and cloud security series. Nothing's worse than a data breach, so protect yourself by cleaning up your gists—both public and private. git clone https://github.com/faradayio/gistkiller.git cd gistkiller bundle install ruby gistkiller.rb The first time you run it, it
Read moreThis is part of our antipatterns series. Ouch! With the recent bugs in ecs-agent 1.8.0, you may be trying to roll back to amzn-ami-2015.09.e or earlier to get a last-known-good ecs agent. If you have yum update in your userdata, however, it updates ecs-init and that,
Read more