Check out the latest posts
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 in sync...
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 developers focus solely on the business
functionality, without caring->->...
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
- the theory of coupling
* Part II
- 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?
Imagine a DevOps team that works on operations for several actively developed,
* 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...
You’ve successfully subscribed to No Kill Switch
Welcome back! You’ve successfully signed in.
Great! You’ve successfully signed up.
Success! Your email is updated.
Your link has expired
Success! Check your email for magic link to sign-in.