Loopin.io
Loopin is finally here! All this effort on the boilerplate and the previous trials have led us here. We re-ignited the idea of alerting. We picked up Fryktos at it's current state and revamped it. This is now the third application that is developed using the Go Boilerplate.
Go boilerplate Docs
The boilerplate had seen 200++ stars on github. It's about time we develop a proper documentaion for this thing. People are using it. We are using it too. it's growing. so it's only logical that we start to think of ways to expand. The phonebook tutorial was introduced and that helped take the boilerplate to the next level.
DexterExplains.com v3.0
It was only natural that the first consumer of the boilerpate is the CMS we've built a long time ago. Dexter Explains was yet re-written from scratch and re-branded for the third time with a more serious and professional look. Response time and every other metric were off the charts becausue of Go and the boilerplate that continues to prove its worth.
Go boilerplate
The boilerplate became a serious project. From simply writing software, to a desire to contribute to the open-source world. The Go Boilerplate was developed out of a personal need to re-use project components as we tend to churn POCs every other month.
Codoworks Go Boilerplate was born. Our first real open-source contribution.
Helix
Helix is a scaffolding tool. It was developed for internal use. The primary use-case for it was to scaffold and automate certain operations with regards to the boilerplate, or in other words to initialise the backend of a project.
Helix was re-branded and made open-source later.
FoxQ.io
Along came the idea of a virtual queue management system. This was the first time we've sold a software. Everything else was abandoned to work on this instead. This was exciting because it was the first real-world application developed using the boilerplate, or at least, what was slowly becoming the boilerplate. FoxQ was sold late 2023! And the idea of a boilerplate proved its worth.
Fryktos
I started building an alerting tool using Go. The idea of monitoring and alerting became a thing. It was at this point that I realised the need for a boilerplate. The goal though was to develop an alerting tool, not a boilerplate! Until the next project came along.
Fryktos was fully developed as a web project. It was comopleted yet unfortuntely, It was abandoned for a cooler project. It was too old by the time it was picked up again, so it was re-written and re-branded.
Loopin
Something wasn't quite right with the blog. We discover a new bug in production every now and then. They were quite annoying to deal with. especially when the site goes down. Monitoring became a need. Alerting to be specific, that was the inception of what is now known as Loopin.io.
DexterExplains.com
Jocelyn rebranded the blog entirely. The brand "Dexter Explains" was born. It was a complete revamp from scratch. The CMS grew and got many more features. This version of the blog took off and became the number 1 result at Google when searching for "raspi-config ubuntu" or anything of such.
Codoworks
The idea behind Codoworks as a software studio began to form. This was during COVID19. It started as a simply idea for a Mom-and-Pop kind of shop. We started taking small steps.
DexterCodo.com
This was Codo-Blog at it's most raw form. I released the first iteration of what is now known as DexterExplains.com. It was a simple content management system (CMS) that I created out of frustration with wordpress. I used Ruby on Rails to make this, nothing fancy, just an MVC app with a simple text area for a wysiwyg.
