DevOps promotes a set of processes and methods for thinking about communication and collaboration – between departments of development, QA (quality assurance), and IT operations. It should be noted that it should not be seen and thus deployed as an independent department / operations team, rather as a mindset across the development and operations teams within the company.
In some organizations, this collaboration involves embedding IT operations specialists within software development teams, thus forming a cross-functional team – this may also be combined with matrix management.
Working medium for DevOps: do it multi-thread but beware the wait flags. Do not wait approval to do great things. Patch even if not perfect, do not wait for approval, failure is good. Work as a reactive intelligent unit, not on automation pilot. Automation pilot is also when you are too organized!
“In response to a message that it receives, an actor can: make local decisions, create more actors, send more messages, and determine how to respond to the next message received. Actors may modify private state, but can only affect each other through messages (avoiding the need for any locks).”
On software development there are laws on design and productivity, one of it is Conway’s law, and others applicable from the natural world, others really counterintuitive.
Organizations which design systems … are constrained to produce designs which are copies of the communication structures of these organizations.
— M. Conway
Corollary: organize your work, your teams, your organisation to work decoupled, decentralised in an unserialized way and feeling happy.