Software Development in 3 Principles & 4 Metrics Editorial The principles are simple: Use fast feedback cycles and validate results with metrics, then you’re off to the races. This philosophy is called “DevOps”.
Easy HTTPS and .WWW Redirect on AWS Resources However I still wanted a redirect from apex domain to www using HTTP and HTTPs. I wanted a free, no-code and no-infrastructure solution on AWS. The solution is an Application Load Balancers and Route53 DNS.
Rack Walkthrough Ruby Rack is the HTTP interface for Ruby. Rack defines a standard interface for interacting with HTTP and connecting web servers. Rack makes it easy to write HTTP facing applications in Ruby. Rack applications are shockingly simple.
Introducing await Resources We’ve open sourced our await CLI to address these problems. The await command is primarily designed for Kubernetes init containers, but may useful in other async scenarios.
Docker Project Boilerplates Docker Working with containers makes encapsulating the development and testing process easy for all types of applications. This is why I'm sharing these project boilerplate repos. They provide an excellent structure to build a production ready project
Cron Data Scraping with AWS Lambda Tutorial The data sources are commonly HTTP APIs so there is nothing uncommon there. The next question is how to run this this cloud and adopt continuous delivery? It turns out that AWS Lambda in combination with a cronstyle event source is a fantastic solution to this problem
Replacing Rake With Make Ruby The answer is simple: stop using rake. Odds are you're using rake as a way to run ruby code. Instead create a CLI to do the the thing. This should make you consider how to design, thus how to test it, and thusly create better software. You'll thank me in time.
Rethinking Software Architecture Talk Resources I challenge the idea that the ruby community knows and understands how to architect and design code bases. We do not respect SOLID principles. I think on the level ruby community produces programs that ignore fundamental architecture boundaries.
Using The Ruby Logger Ruby Ruby has a logging built in. Simply require logger and you're off to the races. Don't waste your time with log4r or anything else. The standard logger is good enough for almost every use case I've heard of. Less dependencies are always important. Use the standard library when you can.
Present Yourself: Presenters in Rails Resources Pages are composed of different components. Each component has their own presenter. A page presenter will provide an interface for getting a presenter for each component. That presenter is passed into the partial as a local variable. It works out pretty well.
