Ten Years and Counting: My Affair with Microservices
blog.allegro.tech
Ten Years and Counting: My Affair with Microservices
1–10 of 52 posts
Re: Ten Years and Counting: My Affair with Microservices
#2As a side note, the management of this company a while go announced they would cancel WFH. A standard story - they built a huge office nobody wanted to use. So whoever could, tried to find a new job. The rest have to go to the office 3 days a week by default. Which is plain stupid because they could get much more talent if they weren't that inflexible.
Re: Ten Years and Counting: My Affair with Microservices
#3As a side note, the management of this company a while go announced they would cancel WFH. A standard story - they built a huge office nobody wanted to use. So whoever could, tried to find a new job. The rest have to go to the office 3 days a week by default. Which is plain stupid because they could get much more talent if they weren't that inflexible.
Perhaps they like working together in a physical space. It's not all about attracting sociopathic talent.
Re: Ten Years and Counting: My Affair with Microservices
#4The developer's vanity and ego is a really big mountain to tear down in devspace, really.
Re: Ten Years and Counting: My Affair with Microservices
#5I assume Hacker News has a bot that automatically posts this skit for every microservice article, but it case it doesn't https://www.youtube.com/watch?v=y8OnoxKotPQ. We should all know Galactus' pain.
Re: Ten Years and Counting: My Affair with Microservices
#6As a side note, the management of this company a while go announced they would cancel WFH. A standard story - they built a huge office nobody wanted to use. So whoever could, tried to find a new job. The rest have to go to the office 3 days a week by default. Which is plain stupid because they could get much more talent if they weren't that inflexible.
Perhaps they like working together in a physical space. It's not all about attracting sociopathic talent.
What about demanding WFH makes the talent sociopathic?
Re: Ten Years and Counting: My Affair with Microservices
#7As a side note, the management of this company a while go announced they would cancel WFH. A standard story - they built a huge office nobody wanted to use. So whoever could, tried to find a new job. The rest have to go to the office 3 days a week by default. Which is plain stupid because they could get much more talent if they weren't that inflexible.
Break the office monolith up in to micro offices. Do one thing well.
Re: Ten Years and Counting: My Affair with Microservices
#8As a side note, the management of this company a while go announced they would cancel WFH. A standard story - they built a huge office nobody wanted to use. So whoever could, tried to find a new job. The rest have to go to the office 3 days a week by default. Which is plain stupid because they could get much more talent if they weren't that inflexible.
Break the office monolith up in to micro offices. Do one thing well.
You win the Internet today. At least for this morning, it's early yet here.
Re: Ten Years and Counting: My Affair with Microservices
#9I missed the part where the person describes that they have a very large development team which justified a non-monolithic architecture. True microservices (with independent development and inter-service contracts) are a reflection of the makeup and scale of the development team. Using true microservices for performance reasons is a misnomer these days: A modular monolith (one codebase that can be deployed into multiple independently scalable services) makes much more sense when the dev team is not big enough to justify the added overhead, but some aspects of the application require independent horizontal scaling.