I quit my company a week ago because as a company of 13 people the communication at all levels was so poor compared to my previous job working with over 20 and several departments. I’m not usually one to judge people’s degrees, but our boss has a biosciences and GIS degree and somehow wandered their way into software management and has the biggest superiority complex I’ve ever seen. These people plague the software development landscape so, my condolences for your CEO who is probably too busy looking at golf clubs and scheduling tee times while writing up an email about how hard executive management works to get back to you.

Likely not, but I’m happy and sad that this seems to be a common scenario.

Sharpening the résumé as we speak

Dump it into ec2-type lol. It’s not a product that can or should be cloud native without becoming a security nest of hornets for customer cybersecurity departments.

Our solutions architect is like this. Not because we’re working on anything important at the moment, but because we keep pushing back important upgrades further and further, making each day a more challenging operation to keep our rickety-ass distributed monolith alive.

We were supposed to upgrade from Java 8 on Springboot 2.1 to 17 on Springboot 3. That got wiped off the table because the bosses think shoving our inefficient solution into a cloud product is what will attract customers.

Exactly. We’re not inventing an iPhone or anything. Extremely niche software that is losing market space every month while the PM’s sit around and prioritize the wrong things, there’s no strategy.

“Add support for another vendor”

“Okay I understood what you wanted perfectly without any context, I’ve also compiled, pushed, and upgraded your customers”

Some people think it will really be that easy. Maybe 50 years from now, but not with these generative models lmao.

Someone tell my boss this, they don’t understand agile. They think we can “start the process” of developing a solution before we’ve understood a single thing about what the customer needs.

And it’s not that we don’t have 100% of the requirements either. It’s basically a we don’t talk to the customer or perform market research to know where we should take the product, so I’m going to make up features at an absurdly abstract level and no you don’t need to meet to talk about it, just start working. “The requirements will come later”, they say. From whom exactly? 🤔