Many startups believe 'if they build it, they will come', but this only leads to disaster as they build the wrong product for an imaginary audience. Find out why this is such a horrible mistake, why so many fall into the trap, and what to do about it if you find yourself there.
Templates and .railsrc files have been around since Rails 3.x, but somehow I'm just finding this out now. Learn from my ignorance and simplify setting up all your future rails projects.
Technical debt is costing your projects and company more than you realize. Like fiscal debt, technical debt can be paid down, and it's imperative that you do. There's more at stake than a little bit of low quality code.
Many naysayers would have you believe Rails is dead. Don't believe the hype. With the coming of Rails 5.1 and its embrace of the JS ecosytem, Rails is solidifying its position as the king of web frameworks.
The easiest thing you can do to support your local user group is to present, so why don't you? More importantly, what are you missing out on by not speaking?
Different frameworks impose different styles on forms, but they all end up requiring more boilerplate. You can either accept the pain boilerpating brings with it, or work around it. Creating your own FormBuilder is a simple way to do just that.
There's a lot to hate about legacy code, but is it possible it's more good than bad? Find out what it is, why it's so hated, and how you can benefit from it.
Cancer in software has many of the same characteristics as those in the human body: it steals resources from the body, grows at an alarming rate, and spreads. Know what symptoms to look for in your software, what damage in can lead to in your project and busienss, and learn how to fight it.
Given a start date, an interval, and a frequency, how can you easily determine if a date is the next occurrence?