#1 - Building a startup in a week.

A quick introduction to 3things, and what we do.

Hi, we're 3things! We're an indie software company comprised of just one backend developer! Well, now that you know that it's just one person, we might as well switch to using I.

I work a full-time dev job with 5 years experience as a backend developer, and am based in Wales.

Ok, that should be enough of an introduction.

So, what's this all about?

I've been meaning to launch some side projects under the 3things name for some time, but always hesitate to actually release what I've been working on to the world. I think it's a fear of criticism and failure. I always switch to new projects just as I'm applying the finishing touches to the code.

Because of this, I've been looking for ways to keep myself motivated to launch a product, and to get over those fears. This blog is the result of my 5-minute brainstorming session.

The goal is to build a SAAS startup within 1 week of publishing this blog post. And along the way, I'll be publishing blog posts each day. No idea what they will contain just yet, but expect something along the lines of ideas, what I've learnt, and what I got done.

"Building a startup in a week" will be a series of blog posts, so keep checking back every day for updates.

The first post

Now that you know what this blog-series is all about, I should probably talk about what I've got done today, right?

Well, today, all I managed to get done was come up with an idea, build and deploy this blog. I've had a busy day at my regular job, and had to squeeze getting this done on my lunch break.

The blog stack

I managed to build this blog in just 5 minutes using Gridsome, I've never used it before today, and I must say, I'm pretty impressed. I'm pretty bad at design, so I just used a starter from gridsome too.

All I had to do, was follow the install instructions and change some css!

The idea

You must be pretty eager to find out what I'm working on now, right? Let me pitch it.

If you're like me, you need to keep tabs on various services' uptime. Sure, you can follow the status twitter accounts, or subscribe to the status pages, but you have to do that for several services that you use.

What am I building? A status page monitoring dashboard. A central dashboard to monitor hundreds of services' status pages and up time, and receive notifications to your delivery channel of choice. Slack? Email? SMS? That's my plan.

So there you have it, you know about us (well, me!), the blog series and the idea! I'll see you in another blog post tomorrow.