Skip to main content

7 posts tagged with "non-technical founder"

View All Tags

· 7 min read
Iain Cambridge

NoCode has arrived and it's everywhere. It’s popular with entrepreneurs who are creating their own apps without developers, and with developers who can now quickly build apps faster than when they were using code. As it’s so in demand, you might think that there’s no question as to whether you’d use code or NoCode; but in reality, that question is there and it’s valid.

To help you understand NoCode a bit more, this article will address the benefits (reduced time to market and building without a developer) and the future of NoCode.

· 10 min read
Iain Cambridge

While I consider Parthenon a Business Application framework, lots of people just consider it a SaaS bootstrap. But the thing is, I also think that most people should be using SaaS bootstraps to start their SaaS/Business software both on side projects and in day jobs. I've seen quite a few objections or people not really understanding the value they bring, so I thought I would explain fully. There are different reasons depending on if you're technical or non-technical, so I'll go through the reasoning for both separately.

And I understand there are 100% cases where you shouldn't use these. But for a lot of super early startups or side projects, I really think they would benefit from not reinventing the wheel.

For the purpose of this blog post, I will talk in the context of the three major SaaS bootstraps, which I'll list out at the bottom.

· 8 min read
Iain Cambridge

So, you’ve heard of this mythical thing - technical debt. Has IT told you that technical debt is the reason for all your major problems? Have they tried to convince you that it’s real and that you need to deal with it? Maybe you’ve read articles and are wondering: is technical debt really as bad as everyone says it is? If you want answers - you’ve come to the right place. In this blog post, we’re going to give you a few stories of what technical debt causes in the real world, not just stories about longer hours or more bugs; but estimates of company loss due to technical debt.

· 9 min read
Iain Cambridge

Hiring developers can be tricky: they’re a long term investment, they take 6 months to onboard, and in order to get the best out of them you need to employ them for several years. In today’s market everyone wants the best developers, so to ensure that you don’t have Facebook, Amazon, Apple, Netflix, or Google (FAANG) knocking on your developers’ doors, you need to make sure that you don’t hire the best that there is. To help you do that, we’ve got some tips on how to weed out the crème de la crème of the developer world, so you can hire developers who have nowhere else to go.

To skim look for the TL;DR in bold

· 4 min read
Iain Cambridge

In software development, free open-source software (FOSS) has always been important and without FOSS, IT would not be the same as it is today. It is hard to think of a company in this world today that isn’t relying on FOSS for part of its tech stack. For many developers, FOSS is a major part of being a developer and they feel like contributing to FOSS is something they, as a good developers, must do. Some loath the idea of commercial software. So it’s with this in mind, we feel like we should explain why we choose not to use the FOSS model. Instead, we have gone for commercial licensing.