What is this blog about?
First and foremost, it'll be about the software architecture and strategy that underlies Eye Closely systems as it is developed.
Why? The pragmatic answer would be "for SEO" (1), and it would be an outright lie to deny that it is not a concern when starting a new product. Is it the only reason? No. If indiscriminate pollution of the internet namespace in service of mammon was the sole reason behind Eye Closely and this blog, it would be generated by the latest and greatest AI models.
No, this blog is also intended as material for thought for those who need to make decisions on "how" to build their next product. To encourage one to stop and wonder about the reasons somebody writing on the internet may have for their words. To wonder about why one architecture might be chosen over another. To question "the right way to do something" and whether a modern framework or database helps or hinders the development to that end.
What to expect from the following posts?
The first topics presented will be about the overall architectural strategy of Eye Closely to give an avid reader an idea about what goes into architecting an application with little or no resources. What matters when trying to keep a project moving fast and equally so, what can be ignored.
As a forewarning, what is done in Eye Closely might not align with the favourite architecture of the reader. Even though what is discussed in the blog may seem counter-intuitive. Maybe even ridiculous, in particular for those who are invested in some particular type of architecture and feel very much at home with it. If that is so, it may be a good time to read the introduction again.
The next posts will be about the high level principles followed by Eye Closely, the reasoning around "why" they are being followed, and at times, why it may be a bad idea to follow them.
The plain-text list of the reasonably soon following posts
- Architectural strategy of Eye Closely
- Choosing or not choosing an architecture
- Vertical slice architecture and why it works under some circumstances
- Building for building speed
- High speed database integration tests
- Performance monitoring
The architectural strategy lays out the principles followed when building Eye Closely with the later posts diving in depth into near-implementation level approaches taken. At times it may touch on the organizational structure, what it should look like to work with a specific architecture, and the costs borne as a result of using the chosen architecture.
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.
(1) For those still pure of heart, SEO means "Search Engine Optimization"