Team topologies

This book talks about how to design teams inside an organisation. This is a very important topic because of Conways law:

Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization’s communication structure.

— Melvin E. Conway

This means that when you design an architecture of a system or when you design a platform you better take into account the communication flows of the company and people involved. The team structure will be an imprint for your product architecture.

This book will give you options on how to structure teams. There are several ways defined in the book, ranging from a collaborative team to platform teams serving self service products. A must read before attempting to scale any teams or organisation!

More info on the team topologies website

The DevOps Handbook

If you are on a DevOps transformation journey this is not doubt a good a read. It will give you the strength and some material to share with your coworkers.

The book remains quite high level (not too deep in the technologies) so it will give you an overview of DevOps practices and why they’re so powerful.
I would recommend the read to engineers but also to managers that want to understand or rollout DevOps practices to improve organisations.
This is also about creating a better workplace for you and your coworkers.

How to take your knowledge of Azure resource manager to the next level!

I used ARM templates for some time now but probably also in a very unstructured way. Until .. I saw this excellent Pluralsight course on ARM templates called Azure Resource Manager Deep Dive


ARM deep dive by James Bannen


If you got some spare time and you are into Azure infrastructure automation I would highly recommend it to you :)
Thanks to James Bannen for creating this excellent course!

Hello world!

Hi there!

My name is Andrea Maruccia and I’m a software developper for many years now. I started with web development but only after a while I finally I found my way: to improve methods and process delivery in various teams.

Recently I’ve lived an awful experience but it has teached me a big lesson. I now decided to be in contact with people that I like, that appreciate me for what I am and for what I give to them, from which I get something nice in return, a bilateral relationship.

I once saw a talk on the internet about devops and one thing the speaker said blew my mind:

If they do not appreciate you, don’t worry someone else will for sure.

I just now realize how true that was, even if deep down I knew it was.

So that’s why I decided to open myself to the world (hello world fits :)), to reach other people whoever wants some guidance on subjects I can help with.

I’ll start with giving a talk on Octopus deploy in the devops italia 2015 event. I will be talking about how you can improve your deployments though automation, on how Octopus helps you in the intent.

If you’re interested to contact me do not hesitate, If you’ve some colaboration in mind do not hesitate, I will be more than happy to find out if we can do something about it.