Vaguery + practice   11

Gojko Adzic » Let’s change the tune
"Until I started using Specification Workshops as the name for a collaborative meeting about acceptance tests, it was very hard to convince business users to participate. But a simple change in naming made the problem go away."
agility  agile-management  communities-of-practice  what-you-call-things-really-matters  practice  craftsmanship 
august 2010 by Vaguery
Informative Build | bigvisible.com
"An Informative Build is a build that tells us what the state of our development is so that we can make an informed decision. We need an informative build, because otherwise Continuous Integration is just a waste of our time.

That’s right, I said Continuous Integration is a waste of time. It is a waste of time, because simply running a build doesn’t help us unless that build can also tell us what we need to do. An Informative Build:

Fails when something is wrong, letting us know that our system is broken and we must fix it.
When it fails it tells us precisely why it failed so that we know what we have to do to fix it.
When nothing is wrong it doesn’t fail. We shouldn’t be wasting cycles chasing down errors due to brittle tests or external dependencies."
continuous-integration  extreme-programming  agility  practice  test-driven-development  test-driven-design  productivity  software-development  mythology 
november 2009 by Vaguery
How Quentin Tarantino realized Plan A (acting) wasn't his best path - (37signals)
"And so as the acting class is going on I just realized I just knew more about cinema than the other people in the class. I cared about cinema and they cared about themselves. But two, was actually at a certain point I just realized that I loved movies too much to simply appear in them. I wanted the movies to be my movies."
having-a-calling  worklife  work  practice  learning-by-doing  career  accidents 
september 2009 by Vaguery
Hot Needle of Inquiry » Blog Archive » Context, My Foot!
"Well, my dear little children, I’ve got bad news for you. It is your precious context that is holding you back. It is your C-level Exeuctives and high-level managers who can’t delegate real responsibility and authority to their people. It is your product people who are too busy to explain what really needs to be done. It is your facilities people who can’t make a workspace fit to work in. It is your programmers who won’t learn the techniques necessary to succeed. It is your managers and product owners who keep increasing pressure until any focus on quality is driven out of the project."
agility  management  change  worklife  practice  rigor 
february 2009 by Vaguery
Only Collect « a historian’s craft
"What this all takes is patience — more patience, sometimes, than I am good at. I am impatient to know things, and impatient for things to make sense more quickly; and the discipline (ah, that apt term) just doesn’t work that way. A colleague of mine told me that he’s been Only Collecting for over ten years, and can now knock out a 3000 word paper in under two days, simply because all his material is already at hand; it exists in the stuff he’s picked up in his intellectual infancy and adolescence, which at the time he didn’t know how to use, and perhaps didn’t even know was important."
generalism  advice  research  education  sense-of-self  inspiration  collecting  practice  context  I-do-this 
december 2008 by Vaguery
Alan’s Kiloblog » GitHub and Git: Sharing Your Code, for What It’s Worth, Without a Begging Entry into Open Source Communities
"With these people, there is nothing more offensive than the fork. You are going to split the community, take away committers. It is heresy. It is a schism.

The nature of open source on the SourceForge model is academia at it’s most petty, because the stakes could not be lower. It is not about the source code, it is about the source code repository and control to access thereof.

GitHub puts an end to this nonsense. I can develop my software and I can use GitHub to publish my software. I don’t have to work within an arbitrary community, but grow support for my software through my own social and professional network."
open-source  collaboration  control  cultural-norms  software  practice  project-management  sensibility  Mercurial  GitHub 
november 2008 by Vaguery

Copy this bookmark:



description:


tags: