Dealing with technical configuration of your apps may be tricky. In a simple case you just slap a text file or two and there's no harm done, but once your solution gets more & more complex, all those pesky files get really cumbersone: * keeping the content of them...
All the considerations below are based on DevOps <-> Dev scenario, but IMHO vast majority of them applies well to any supplier <-> buyer scenario. DevOps' reality is somehow simple: * they work for other developers (their "clients") * their goal is to make other...
This is part III of coupling consideration topic. If you want to check my past coupling-related posts, you can find them here: * Part I [http://gebski.tumblr.com/post/76150235763/the-silent-assassin-that-knows-no-mercy-how] - the theory of coupling * Part II [http://gebski.tumblr.com/post/77632428220/the-silent-assassin-that-knows-no-mercy-how] - practical examples of coupling...
Another day, another interesting discussion, another topic for a blog post: the operations procedures (aka handbooks) in agile environment - should we bother writing anything down? If so, what for? The Context Imagine a DevOps team that works on operations for several actively developed, interconnected applications: * work happens in several...
Some people are quite messy by nature - in many cases it’s because they don’t give a … care. In some because they’re overconfident (they believe they are more organized than they actually are) and sometimes it’s a nothing more than an old, crude lack of time...