4

I got hired in as a senior engineer and, after getting adjusted to the new job, I suggested some pretty big process changes for a big year long project we're working on.

I convinced the manager and team to not continue our practice of dozens of independent project repos where we repeat a lot of the same .NET code, and instead have all our services in one big monolithic repo specific to this domain. I build out the docker compose infrastructure so we could build everything using local Kafka and Mongo (previously devs always relied on the cloud dev environments for both).

It's streamlined, and still a bit clunky because I didn't want to change too much, but I think it will be a significant gain with a project that's this big.

We're already seeing a lot of issues that could have been swept under with the old process of tons of independent services.

Still, I struggle to care. We had layoffs in November, the logistics industry is still struggling, my manager is still using LLMs for stories and coding .. and although he did fix a bug in our Kakfa libraries pretty quickly using copilot, elsewhere it just seems like we're getting big messes of stuff. Even I'm auto-generating all the unit tests and not bothering to even look at them anymore.

I've been here six months. I bet I'll see this go into production. I hope it's not a disaster. I'm struggling to care.

Comments
  • 2
    Ahh. You should be a consultant. Initiate a lot of change. Get a good reference and move onto the next thing.
  • 2
    Lol... Too real.

    What do you have against microservices?
  • 4
    Look at the bright side. You suggested an improvement in their processes && they _listened_. Doesn't happen that often... at least in my experience.
  • 2
    @iSwimInTheC It's still microservices. All the code is just in one repo that is used to create all the individual services, so we're not repeating all the same shit over and over; fixing it in 20 places instead of one.

    I've written a whole thing on Microservices:

    https://battlepenguin.com/tech/...
  • 1
    @djsumdog of course you wrote an article about it :p Great read again.
  • 1
    Microservices are in fantasy great. Small isolated independent projects that can be tested fully and documented completely and thus can be finished. But in reality it's overhead in several areas.
Add Comment