Introduction
Thank you for visiting Forever 200 OK! This blog was meant to be mostly about Forever 200 OK itself, about the its workings and when to use it. However, it turns out there is a lot to be said about software architecture, infrastructure, software business and anything to do with technology overall as it relates to it. So it could be more accurate to describe it as a software engineering blog than something limited to introspection.
What to expect from the following posts?
What I (and possibly "we", if there happen to be others posting in the future) try to cover is to give an avid reader an idea about what goes into architecting an application with few resources. What matters and should be done when trying to keep a project simple and equally so, what can be ignored.
As a forewarning, what is done in Forever 200 OK might not align with the favourite architecture or approach of the reader. Even though what is discussed in the blog may seem counter-intuitive, the choices arise from a long time of trying different variations of building software and they are made specifically for the scenario of a solo software engineer with a long term tenure. For better or worse they are likely to be incompatible with a corporate software building approaches. That is fine.
What is this blog not about?
This blog is never going to give the one and true answer to all problems one may encounter in software engineering. There may be some rants about the way things are, but it acknowledges that all things and beings have history, reasons, and limitations. Perhaps things were done with the best intentions, but they came out as usual. There is no need to place blame at the feet of those who meant no harm.
Summary
Please have a look around and thank you for visiting us! If you are in the business of building web applications, whether as a software engineer, a QA expert or a manager, you may want to take a look at Forever 200 OK monitoring tool and see if it may work for you.
- Heidi (Founder)