Group items tagged

"When I first began teaching, I assumed my anxiety in each of these domains would eventually dissipate. I was certain that there had to be an approach to grading that was simultaneously meaningful, moral, and manageable, and that, with enough time and experimentation, I would eventually discover it. Yet the more I tried to get a handle on anxiety in one domain, the more I seemed to increase my anxiety in another. [1] I came to believe that the system was stacked against us. It had trapped us into a corner where, at best, we could maximize two goals at the expense of the third. Mirroring the "fast, good, cheap" meme that designers love so much, my pessimistic grading meme might look something like this:"

"We all benefit from the free and open exchange of ideas, and I'm just glad this image has been part of that exchange."

"People are caught up in a focus on STEM"-science, technology, engineering and math-"but the piece they don't understand is that all of those fields rely on clear, good writing, and we're not getting that," says Elyse Eidman-Aadahl, executive director of the National Writing Project, a nonprofit think tank at the University of California, Berkeley.

So here's an idea for a fresh meme: #GoodWritingIsSexy.

I/we need to consider this with our team and education more broadly. "Theory 1: Nothing we "know" about software development should be assumed to be true. Most of our tools, our mental models, and our practices are remnants of an era (possibly fictional) where software was written by solo practitioners, but modern software is a team sport. Theory 2: Technology is the product of the culture that builds it. Great technology is the product of a great culture. Culture gives us the ability to act in a loosely coupled way; it allows us to pursue a diversity of tactics. Uncertainty is the mind-killer and culture creates certainty in the face of the yawning shapeless void of possible solutions that is software engineering. Culture is what you do, not what you say. It starts at the top. It affects everything. You have a choice about the culture you promote, not about the culture you have. Theory 3: Software development should be thought of as a cycle of continual learning and improvement rather a progression from start to finish, or a search for correctness. If you aren't shipping, you aren't learning. If it slows down shipping, it probably isn't worth it. Maturity is knowing when to make the trade off and when not to. I had some experience with this at Flickr, and I wanted to see how far you could scale it. My private bet was that we'd make it to 50 engineers before things broke down. Theory 4: You build a culture of learning by optimizing globally not locally. Your improvement, over time, as a team, with shared tools, practices and beliefs is more important than individual pockets of brilliance. And more satisfying. Theory 5: If you want to build for the long term, the only guarantee is change. Invest in your people and your ability to ask questions, not your current answers. Your current answers are wrong, or they will be soon. "