Got any tips for a newly minted Solutions Architect? Coming from a senior software engineer background but want to know some things to think about as I switch to a more hands off architecture role. Looking to take the next month soaking in some inspiration and advice.

Laid the foundation and got a patent application for a custom Enterprise PHP framework that interacts with all of the big chat AI api's and can communicate with the outside world as IVR, SMS, Webchat, etc. Had corporate guidance but a lot of leeway and was the sole developer for a full year of the project. I've since left the company and they expanded the team and are soon to go to production with it.

Starting a new job tomorrow, old job was a software engineer working on mostly PHP with some mild Java stuff, tomorrow it is Java Spring Boot backend work. Should be an exciting change of pace

Preaching TDD/TFA without having gotten there quite yet. I have unit tests, but only half are actually TFA :(

Org is doing a major conversion to containerized solutions and modern technology. Most of which I can wholly support, only 1 catch. everything will need to be ported to Java. we are a mixed shop of largely PHP and Javascript devs with only a handful of devs who actively use Java regularly, this change throws away tons of previously built battle tested code in order to swap to putting all new code on an all new platform. I thought the point of containers was to be able to isolate and run whatever you want within the container and have it highly portable...

That feeling when you spend a week evaluating IDE software, providing lots of critical evidence as to a clear winner, and the company refuses to spend any money to improve the tools.

Built my first MVC application today. Building proof of concepts to hopefully modernize my workplace!

Being a modern day sorcerer, capable of building exotic creations through sheer force of will, constantly learning and advancing the craft