Agile
Get flash to fully experience Pearltrees
Deploy ALL the Things - Deployment Myths Part 2 | Agile Zone
This post was authored by John E. Vincent (aka. lusis ). Creator of Noah —a lightweight node/service registry inspired by Apache Zookeeper . For more deployment patterns and anti-patterns, chec, out DZone's Continuous Delivery Refcard . My previous post covered some of the annoying excuses and complaints that people like to use when discussing deployments.
I came across an interesting post today via HN. I’m surprised (only moderately) that I missed it the first time around since this is right up my alley: Why are you still deploying overnight? I thought this post was particularly apropos for several reasons. I just got back from DevOpsDays EU AND I’m currently in the process of refactoring our deploy process.
Rollbacks and Other Deployment Myths | Agile Zone
Thanks to the Lean Startup movement, Iterationless Development and Continuous Deployment have become the New New Thing in software development methods. Apparently this has gone so far that “there are venture firms in Silicon Valley that won’t even fund a company unless they employ Lean startup methodologies”. Although most of us don’t work in a Web 2.0 social media startup, or anything like one, it’s important to cut through the hype and see what we can learn from these ideas. One of the most comprehensive descriptions I’ve seen so far of Iterationless Development is a (good, but buzzword-heavy) presentation by Erik Huddleston that explains how development is done at Dachis Group, which builds online social communities.
Iterationless Development – the latest New New Thing | Agile Zone
The latest new new connerie ? Ptet bien pour une startup vraiment early stage... by Nov 30
Shipping first time code is like going into debt. A little debt speeds development so long as it is paid back promptly with a rewrite… I thought that rushing software out the door to get some experience with it was a good idea, but that of course, you would eventually go back and as you learned things about that software you would repay that loan by refactoring the program to reflect your experience as you acquired it. As is often the case with financial debt, technical debt accrues with compound interest. Once it reaches a certain level (e.g. $1 per line of code) you stare at a difficult question:
Should You Ship This Code Before Reducing Technical Debt?! | Agile Zone
10 Mistakes That Software Team Leads Make | Agile Zone
“Ten Mistakes” (as I shall now call it because I’m too lazy to keep typing the whole title), was a talk by Roy Osherove which I went to at Skills Matter. He basically takes us through ten common mistakes he sees team leaders make, and offers some solutions to them. He also looks like Adam Sandler, I kid you not.
Pizza Teams and Terabytes Amazon's headquarters look much more prosperous and mature than they did in the late 1990s, when Bezos was fighting the "dot-toast" prediction. Back then the company was on Seattle's skid row. Its old brick building shared a dismal block with a needle exchange and a defunct pawnshop. Bezos flaunted his frugality. He got plenty of flattering press for living in a small downtown apartment and driving a Honda even though his startup had already gone public and he was worth $500 million on paper.
Inside the Mind of Jeff Bezos | Fast Company
As aspiring Software Craftsmen we are raising the bar of professional software development by practicing it and helping others learn the craft. Through this work we have come to value:
Manifesto for Software Craftsmanship
I'm a big fan of agile development. One of the key concepts that I like the most is story point estimation. The best suggestion I ever heard was to estimate the size of your stories in terms of gummy bears (at which point you can come up with possibly one of the best units of progress measurement, gummy bears / iteration), thereby making sure that nobody gets the impression that you're actually quoting any sort of real unit of time. The exact opposite of this is trying to estimate stories in an agile project in terms of hours.
Punishment driven development
It's our own damn fault | Agile Zone
Over the course of my more than twenty years in the software development industry, I've worked with hundreds if not thousands of developers. Many of the projects I've been involved with have suffered from the same malady; a disconnect between expectations and realistic possibility. The Agile Manifesto attempts to address many of the root causes of this malady. It encourages individuals to interact, collaborate, communicate, and respond to change. These are not easy things to do. Nor do they necessarily ensure quality software.Agile Ruined My Life
I read the reply to my comment on a popular hacker board with sadness: (disclaimer: Agile consultants ruined the software group I work in.) Making good software is hard, and anyone claiming to have a magical process that guarantees good software is selling snake oil. I can appreciate your wanting to make a buck, but would also seriously appreciate it if you could find some other industry besides software development to go screw up