One of the things that makes Ruby great is that we can customize almost anything to our needs. This is both useful and dangerous. It’s easy to shoot ourselves in the foot, but when used carefully, this can result in pretty powerful solutions.
The start of a new year is a great time to reflect and think about the previous one. Two years ago, I started publishing my thoughts about my personal year. With 2018 just starting off, it’s time for me to look back at 2017.
Integrating with other services is on the roadmap of almost any SaaS application. There’s only so much your application can do itself. Sometimes it’s best to leave tasks up to others who specialize on them.
Building a SaaS (or any software product, really) takes a lot of time and money. It’s hard to stay focused on the things that actually produce value for your customers. In the following, I’ll show you a few things that you can easily skip until after launching. This way, you’ll launch earlier, and maybe even learn that you don’t need some of the features you thought everyone wants.
A year ago, I published my first Year in Review post. I did not publish anything since that review and therefore was a little hesitant about writing one for 2016. It was a tweet by Jamie Lawrence that convinced me to write this review:
“Year in review” posts are great way of rewriting history, and a terrible way to compare yourself with others – Jamie Lawrence
However, my intention isn’t to rewrite history. Instead, I want to preserve the things (both good and bad) that happened this year.