Overlord Systems

Thought it was kind of cool to see this comparison. Game vs. how it looks in the editor. #indiegames #WishListWednesday #indiedev

Given that AGI has been achieved, I am happy to report that every copy of the Overlord Engine by @theoverlordcorp comes with OSAGI. Introducing OSAGI™, our very own Overlord Systems AGI. Thank you for your attention to this matter.

I think @theoverlordcorp is looking good insha Allah for a CLOSED ALPHA by April! It will NOT have all features, but it will be enough to test the core engine, local dev, and AI agent features with few users. Beta coming later. Crazy month ahead to get this ready but excited!

Thoughts on business, product, and strategy: In Overlord's (@theoverlordcorp) first investor update I noted the 3 core things we need for beta launch: - An embedded code editor - A production-ready core engine (local dev env, DBs, collaboration, logic, etc.) - Cloud infra for deployments and other features For a typical startup/SaaS, this is *way* too much. You should build the minimal useful thing, launch, and iterate. For example, me and 2 engineers built and released a VOD platform with many features and a large admin panel in 1.5 months. Problem is, due to the nature of our product, the Overlord Engine, this approach doesn't work. I have recently come to think about products as being of two major types: "composite" and "monolithic". Monolithic products need significant upfront time/effort/money. Cars, planes, space rockets, and video games are all monolithic. Most hardware products are monolithic. You can't sell just the car engine, tires, or chassis. The parts alone aren't useful and customers don't care about them. Monolithic products can be iterated as a whole but not in part. You can make rocket v2 or update your game, but you can't ship your game's physics engine and promise the rest later! In comparison, composite products have small minimal-useful-parts and are easy to extend. Most software products are composite. v1 of a SaaS can be an API to send emails, then you add analytics, then cron jobs, then team features, and so on. Low upfront investment and quick revenue. Monolithic/composite is a spectrum. Composite is hugely advantageous, but be careful of ending up in a local maxima. Many such! Note that deep tech is parallel to the above discussion. Gas cars are monolithic but *not* deep tech, while ChatGPT is composite but built on a (at the time) deep tech core. Overlord? monolithic. This is something I internalized when I finished the proof of concept and saw how much effort that required. The "wow" point required more parts coming together than any product I ever worked on before. The short term goal of Overlord is to become the default way to do web dev by rethinking and improving how we develop web software. For this to happen, we have to figure out the atoms of web dev and to use them better than the status quo. The magic of Overlord is when all the atoms come together such that the experience is greater than the sum of its parts. This is what happened in the PoC and it's what enabled our pre-seed round, but this is also the main challenge because it means individual features aren't enough (i.e., it's monolithic). Releasing an individual feature doesn't work (the pieces are intertwined), doesn't provide 10x value, and will confuse people about what @theoverlordcorp is. All this to say, it's taking a while, sorry, I wish we were live yesterday! Although, I am seeing so much depth in the core engine that perhaps core engine and code editor alone can be a meaningful beta, with the infra soon after...👀 If you read this far, wow, thank you, and put your email here (and share with friends!): overlordsystems.com

Speed is good cc @theoverlordcorp

@mackron The editor inside @theoverlordcorp is an infant still (and no C syntax highlighting YET), but look at this bad boy go!

No one told me when I embed the postgresql parser I have to support the whole parser 😂(at least it's sane, unlike LSP). On the other hand, people using @theoverlordcorp will have a great time working with migrations!

This article is something close to my heart that's been simmering for a few years. It's finally written in a way I am happy with, and I am glad to share it at a time when I get to apply this philosophy via @theoverlordcorp Hope you find it interesting: bloeys.com/blog/beyond-ab…