Grant Mill Software Limited | Software Architecture, DevOps Engineering About
How many people does it take to build a website?
Typical software answer is: it depends! This site took four people.
Grant Mill (Company Director): Solution Architect, DevOps Engineer, Software Engineer, Quality Assurance, Security Compliance, AI Wrangler, Prompt Engineer, and Product Owner.
Jo Lomax (Company Director): With a background in finance, Jo handled all the photography, electronic digital manipulation, quality assurance, and proofreading.
Our children: They contributed by providing positive feedback on the look and feel, creating bespoke artwork for the website, and motivating us towards a better, healthier work-life balance.
The primary goal for the site is to demonstrate what the company does and showcase competency in some basic skills while continuously learning and improving. The site is hosted in Azure, essentially for free, thanks to Microsoft. However, it doesn't require security roles, electronic payment functionality, high transaction capacity, or inventory tracking. There are no calculations, and it doesn't hold any state or data (not even a cookie). Its primary purpose is to sell our wares.
Where does the time go in making a site like this? In short, design, learning, and more learning. It involves researching job roles, finding art and photos, navigating, collaborating, and implementing what looks good while eliminating what looks bad. Then, doing it all again, but with one-tenth the code.
We didn't use Scrum because there was no one to report to. It doesn't warrant a DevOps pipeline and three separate environments for testing and deployment. But it will likely have all those features in due time.
When you want to go fast, go alone; but if you want to go far, go together.
Division of labor shows that specialization and expertise in certain skills result in a better product, but this always comes at the cost of additional management and effort, requiring good communication on multiple levels.
The optimal team is big enough to share a pizza, but good luck agreeing on the toppings (so we usually buy four, dont sweat the small stuff).
The success of that team will depend on the ideals of the company that nurtures the contributions of all individual efforts in both success and courageous or ambitious failure.
Whatever your problem, we have the skills to analyze and provide sound advice, whether it's technical, managerial, or structural.
Long hours and misery are never the way out; simplify the problem, seek another perspective, and then use technology and the collective expertise of those around you to improve everyone's life.
Long hours of enjoyment? Well, we won't argue against that. Just remember, if that's the case, you're on your own – we are a family with everything that entails.
How many people does it take to build a website?
Typical software answer is: it depends! This site took four people.
Grant Mill (Company Director): Solution Architect, DevOps Engineer, Software Engineer, Quality Assurance, Security Compliance, AI Wrangler, Prompt Engineer, and Product Owner.
Jo Lomax (Company Director): With a background in finance, Jo handled all the photography, electronic digital manipulation, quality assurance, and proofreading.
Our children: They contributed by providing positive feedback on the look and feel, creating bespoke artwork for the website, and motivating us towards a better, healthier work-life balance.
The primary goal for the site is to demonstrate what the company does and showcase competency in some basic skills while continuously learning and improving. The site is hosted in Azure, essentially for free, thanks to Microsoft. However, it doesn't require security roles, electronic payment functionality, high transaction capacity, or inventory tracking. There are no calculations, and it doesn't hold any state or data (not even a cookie). Its primary purpose is to sell our wares.
Where does the time go in making a site like this? In short, design, learning, and more learning. It involves researching job roles, finding art and photos, navigating, collaborating, and implementing what looks good while eliminating what looks bad. Then, doing it all again, but with one-tenth the code.
We didn't use Scrum because there was no one to report to. It doesn't warrant a DevOps pipeline and three separate environments for testing and deployment. But it will likely have all those features in due time.
When you want to go fast, go alone; but if you want to go far, go together.
Division of labor shows that specialization and expertise in certain skills result in a better product, but this always comes at the cost of additional management and effort, requiring good communication on multiple levels.
The optimal team is big enough to share a pizza, but good luck agreeing on the toppings (so we usually buy four, dont sweat the small stuff).
The success of that team will depend on the ideals of the company that nurtures the contributions of all individual efforts in both success and courageous or ambitious failure.
Whatever your problem, we have the skills to analyze and provide sound advice, whether it's technical, managerial, or structural.
Long hours and misery are never the way out; simplify the problem, seek another perspective, and then use technology and the collective expertise of those around you to improve everyone's life.
Long hours of enjoyment? Well, we won't argue against that. Just remember, if that's the case, you're on your own – we are a family with everything that entails.