Multiple computers, the benefit

Multiple computers can help you find more bugs in your Apps

I have a few computers that I use, most people would say too many, for me though, it works. Having multiple computers gives me the freedom to work in more than one location. I have my main desktop in my office, my old still usable desktop in my wife’s office space and two laptops, a Surface Book and a Macbook Pro. Both the Macbook Pro and Surface Book are a little long in the tooth, but they still work well enough for when I need to take a machine onsite for freelance or contract work.

Why am I mentioning I have a use multiple PCs, well, there are a whole host of development problems that you solve because you use multiple machines. Additionally, because I use multiple machines, I tend to make fewer changes to my setup than I used to. Other than my IDE of choice and Docker, my setup is simple, this makes it easier to replicate across my computers.

What is the gain?

So, what is the gain? Well, you can only use multiple PCs if your Apps are setup on each of them, this is the benefit, because you have to setup each App more than once you quickly get to spot any issues, if you added an extension when you developed a feature, boom, you’ll notice, if it isn’t easy to get your tests to run, boom you’ll notice. It also gives you the opportunity to test the first install process for your Apps, you’ll quickly notice the necessary data you added outside of a migration or the path that isn’t mapped.

Yes, having multiple computers is a luxury, the thing is though, keep your old stuff, it is more functional than you realise.

If you don’t have multiple machines, you can always use someone else’s, add an account to your partner, child’s, siblings, or parents’ computer, with their permission of course. Even if you only rarely setup one of your projects on another machine, you are bound to spot an issue you didn’t know existed.

Simpler than years ago

These days tools like Docker have solved a lot of the problems we used to experience but I still think you will find an issue or two when you setup an App fresh on another computer, especially if that App has been in development for a while or moved beyond basic functionality.

Budget – Official Release

Budget - The Official Release

Late last year, I released Budget, a free open-source App powered by the Costs to Expect API, with a beta tag. After bringing the Wife on board to help, we started to respond to feedback and polish the App. We wanted as much feedback as possible before the official release which is now ready.

Beta Release

We spent quite a while testing the App before releasing it with the beta label. However it is always amazing just how many issues appear when the public at large start using your stuff.

We ended up pushing seven small updates, each improving the UX and UI of the App that extra little bit. All these improvements will make it into Budget Pro (the subscription version of Budget) and eventually all my other Apps. After 25 years of web development, I still admit I have a lot to learn and am always happy when I do learn something new.

I’ve released several Apps over the last two years. However none have been as polished as Budget and I have to say I am proud of what I’ve created and keen to start focusing on Budget Pro, the commercial offering of Budget.

I have a blog post coming soon explaining why there are going to be two versions of Budget and why they are going to be created in the way they are. The short story is, I’ve always intended for the Apps to be separate, and I think the approach I’m taking will ensure that they can each shine in their own way.

The Next Chapter

This is the start of a new chapter and I’m keen to see where it goes, only time will tell.

We learned so much during the last two months, hopefully we can benefit from the new knowledge as we approach the beta release of Budget Pro. Budget Pro is much more complicated than Budget so I’m sure we will discover an entire new set of issues which hopefully our beta users will be able to help us resolve.