Bounded Chocolate Contexts
What does chocolate sauce have to do with bounded contexts and software design? Enquiring minds want to know.
What does chocolate sauce have to do with bounded contexts and software design? Enquiring minds want to know.
For today, a link full of other links, including preparing for high-load days and why people got into programming.
It's a thing and we should care about it, but how does the Triangle Shirtwaist Factory Fire relate to SRE?
I mentioned Conway's law last week, and that got me to doing some semi-random link following. I ran across a couple of articles on structuring the development of large systems so as to create bounded contexts and limit cognitive load and organizational refactoring to reducing organizational debt.
Not as much fun as the Steel Curtain, but a fairly light read with some deeper context. Who does Software Architecture?
Learning from your mistakes is important and key to building stable efficient systems, As good as that is, learning from others mistakes is even better. With that in mind, here's a list of Kubernetes mistake stories we can all learn from.
Not to kick off a religious war, but I like vi/vim since it's what my fingers learned lo those many moons ago, but I ran across this list of vim tip and tricks and I learned something new. Enjoy/discuss at leisure.
Here's a topic for discussion. Conway's Law says that organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations.
There's lots of evidence, anecdotal and structured, that this is in fact the case. Knowing that, how might we approach our infrastructure design, both the internal interfaces and the customer facing ones?
Getting a good night's sleep is important to health and wellness, but our customers expect things to work 24/7. What's an engineer to do to get a good night's sleep?
Helping my Friendgineers whenever possible