Back to blog

Update and support pet projects

About the problems of supporting non-commercial pet projects.

#job

For some time now, I've been facing the problem of supporting my own or joint pet projects (non-commercial).

Initial problems were related to renewing subscriptions for hosting services — these are not so difficult to solve. Some applications used third-party APIs, as well as separate services for databases.

At one point, when I updated my website with my projects, I ran into difficulties demonstrating working versions of some of them. Certain services had stopped working, such as Redis, Postgres, Heroku, Firebase.

In basic usage, there were no issues, but due to exceeding free-tier limits, complications started to appear. Additionally, working with Heroku has become more complicated — more details can be found here.


This post is more about why similar projects may stop working.

Some of these applications were created to improve skills or try new technologies. By the time development was finished, the core functionality was still working, but it was hard to predict whether external services would remain available in the future.

I see the value of maintaining such projects like this:
if a project becomes more than just a "trying new technology" exercise, then it makes sense to refine it or keep it maintained.

At the moment, my pet projects mainly carry value in the form of experience and code.

Thanks for your understanding.