I've been building out my ground up fully automated software development platform for ... Over a year now, albeit with a hard pivot around April this year.
And treating the whole stack as part of the same system and enforcing everything to be automated and consequently adding more and more quality gates feels just like unlocking technologies in eg factorio, introducing new archetypes feels just like building new outposts etc
It just keep getting bigger and bigger with more and more features I've ever thought of in my professional life, provided by the platform, built entirely by agents (since the hard pivot).
Like Auto-Generating consumer pacts, providing them in a repository server pinned by service version. Then pull those in from the deployment orchestration to be verified again those as a quality gate on deployment.
And providing the providers response to those pact as software packages themselves, and pulling those in on the consumers for e2e tests across the stack - right down to screenshot tests in the UIs...
And from those dependency trees building optimal release trains for the least amount of releases (bunching up software changes with lib version bumps etc)
> my software engineering factory
Isn't that just the best factory game ever?
I've been building out my ground up fully automated software development platform for ... Over a year now, albeit with a hard pivot around April this year.
And treating the whole stack as part of the same system and enforcing everything to be automated and consequently adding more and more quality gates feels just like unlocking technologies in eg factorio, introducing new archetypes feels just like building new outposts etc
It just keep getting bigger and bigger with more and more features I've ever thought of in my professional life, provided by the platform, built entirely by agents (since the hard pivot).
Like Auto-Generating consumer pacts, providing them in a repository server pinned by service version. Then pull those in from the deployment orchestration to be verified again those as a quality gate on deployment.
And providing the providers response to those pact as software packages themselves, and pulling those in on the consumers for e2e tests across the stack - right down to screenshot tests in the UIs...
And from those dependency trees building optimal release trains for the least amount of releases (bunching up software changes with lib version bumps etc)