About 10 years ago I was part of a meeting where the CEO of the company was trying to convey his vision of the company and it's core service to customers. I asked the room what the objective was and someone jokingly answered, "to make money" and the meeting continued ... and finished.
It's easy to fall into the trap of thinking that you could copy the Spotify model presented in Henrik's Spotify Engineering Culture Videos as a way to Scale Agile. Well of course it's easy. They're organization continued to be agile as they grew. Henrik really makes it look easy and amazing! It's really very aspiring, so it totally makes sense.
A dialogue about using Kubernetes, Cloud Foundry and PaaS.
agile adj. - Characterized by quickness, lightness, and ease of movement; nimble.
Routine enables us to move fast in a sustainable velocity. So we have 6 meetings during our iterations. It's simple, focuses on solving the "mis alignment" problem, and periodical (repeats every iteration).
I've been working with my team to practice Test Driven Design (TDD) for about 2 years. They just started REALLY doing it about 4 weeks ago after I finally gave them the permission they needed to do it. And even now, they don't feel comfortable because it takes them longer to finish development. Below is my story of how I kick started the team practicing TDD and my observations of what I think are keeping the majority of Software Engineers from following the practice.
Tony likes to push my buttons sometimes. He knows what my opinion is about how and why teams should estimate stories. So I get a text from him today, asking me what I think about Do Story Points Relate to Complexity or Time?. I'm compelled to bite. I can help it, but meh, it's easy to post things to the internets.
Has your boss ever asked you to increase your code quality? How did you do that?
I thought it would be interesting to post a version of Amber's article that changes the context from school to work.
I want to capture and share my journey about how I increase my work output as a software engineer by multiples of 10, 100, 1000.
I want to work on a team who's culture has these characteristics.
I started out writing a verbose post about how to create a DevOps culture in an enterprise. After sleeping on it, I realized that people really need tactical suggestions on how to create a DevOps culture, not just a description. So here's a DevOps Culture todo list.
Or rather, you think there's going to be a conflict about a particular subject and so you don't even broach it. You don't even know if all the subsequent decisions and problems could've been avoided had you just asked.
tldr; Building websites with content negotiation in mind gives you flexibility.
In order to reuse code, it must pass the teams measurement of readability and discoverability.
This has been a long time coming. I've preached about blogging for years and yet, have never done it myself. Well, I have but that was back in 1997 and I didn't keep it up and I don't have proof. Not only that, but I'm a big believer that programmers should write code and if you're a programmer AND gonna write a blog, that you should write the blog engine yourself. It shows off your talents, or lack there of, and you'll learn something along the way.