Monday, October 19, 2009
Monday, October 5, 2009
Monday, September 28, 2009
People sure are a funny bunch.
Fascinating story about a researcher's conclusions and the negative reaction it caused.
Friday, September 18, 2009
Monday, September 7, 2009
This is fascinating. 67 petabytes (that's 1,000 terabytes) for under $8K! A knowledgeable engineer responds - Sun engineer responds to the Backblaze "Petabytes on a budget" design
Lots of little articles that have something important to say.
Sunday, August 23, 2009
I have always hated precision mistakes. Now to use verisimiltude in casual conversation :-)
It's easy to see why the stock market was due for a crash.
Saturday, August 15, 2009
Sunday, August 9, 2009
The world in 1789 stood on the edge of a unique transformation. At the end of an unprecedented century of progress, the fates of three nations—France; the nascent United States; and their common enemy, Britain—lay interlocked...David Andress reveals how these events unfolded and how the men who led them, such as Benjamin Franklin, Thomas Paine, Emmanuel-Joseph Sieyès, and George Washington, stood at the threshold of the modern world.
Quite long but full of good information. If you still believe markets are efficient then please read this. If not then just browse it for some cool graphs.
This first one links to the second one. They both cover roughly the same subject but slightly different and they are short. Basically is you use an Exception to handle a predictable case (like divide by zero) you should consider a different career.
I never heard of Content Delivery Network before this post. The concept isn't new, but the fact that Amazon cloud supports this so cheaply is shocking. I guess there is more out there than I have time to learn.
Another DB I have never heard of as well as a list of non-relational DBs with details on MongoDB.
Lean Primer [PDF]
A good, long paper on Lean that covers the subject well.
Wednesday, July 29, 2009
Great list for anybody who is or wants to be a manager of developers.
A graphical view of where the average consumer spends their money.
Good wish list. I hope VS 12 does it :-)
Good article and a better practice.
Friday, July 24, 2009
Quite long, but the author makes some good points. I agree that often Scrum can miss the boat by leaving too many things up to the team. Many I have worked with would be lost in such a situation. I believe process is what you do. If everyone on the team follows a completely different process then improvement will be limited if not impossible. Like the author, I think good management is essential to improvement and much of Scrum seems to be to limit management. I think this inherently places limits on the Scrum team to improve. I think it is due to the history of so much mismanagement in software, but 180 degrees from wrong is still wrong.
Thursday, July 23, 2009
This is brilliant! Kids writing excuses notes as part of class!
- "To my mind, the question that’s much more important than how to control a software project is, why on earth are we doing so many projects that deliver such marginal value?"
- "Software development is and always will be somewhat experimental."
- Lesson 1. All software is flawed.
- Lesson 2. Check-in often.
- Lesson 3. Tests, gotta love them.
- Lesson 4. Refactor, check-in and repeat.
- Lesson 5. Coding is easy, humans are tough.
- Lesson 6. The more eyes on your code the better.
- Lesson 7. Keep learning and improving.
- Lesson 8. Simple is beautiful.
- Lesson 9. Learn software development not coding.
- Lesson 10. Think about your audience.
Tuesday, July 21, 2009
Thursday, July 16, 2009
I liked the summary of Gerald Nadler’s book from the mid 1990’s, Breakthrough Thinking: The Seven Principles of Creative Problem Solving. Nadler's seven principles:
5. Limited Information Collection
6. People Design
7. Betterment Timeline
Covers the architecture of Stackoverflow.com and gives it fairly high marks.
Wednesday, July 15, 2009
The first one is precious!
A good short read that will help most people. In summary here are his 12 things (for detail read the PDF):
1. Measure, measure, measure
2. Increase quality
3. Reduce rework
4. Frequent releases
5. Stop working in parallel
6. Shorter stories
7. Visualize and manage flow
8. Rigorously cancel meetings
9. Continuous deployment
10. Shorten product management
11. No single point of failure or bottleneck
12. Leveling work
Long, but thorough article that shows how easy it is to misunderstand statistics. In conclusion "Careful analysis shows that the incomes of most types of middle American households have increased substantially over the past three decades." The richest 25% have gotten richer, but the middle class hasn't done as bad as many politcal people might lead you to believe.
Tuesday, July 14, 2009
Does a good job of explaining what Kanban is and is not. I love the quote:
“the kanban is an organized system of inventory buffers and, according to Ohno, inventory is waste, whether it is in a push system or a pull system. So kanban is something you strive to get rid of, not to be proud of”
- Jeffrey K. Liker, “The Toyota Way”, p. 110.
Monday, July 13, 2009
Jurgen does a good job in this one. He defines three types of change in a complex system (closed, contained, open-ended) and gives examples plus a personal story to boot.
Good explanation of Discreet Fourier Transform with code to boot.
Saturday, July 11, 2009
I fascinating look into code solubility (I had to look this up). Gem "One of the worst mistakes that programmers make in writing code is in failing to recognize that more productivity will be spent over the life time of code navigating through the code than will be spent writing the code"
This is so true! I have done this too many times to count.
A seven minute interview/overview of "Brain Rules" that covers roughly half of the book.
Friday, July 10, 2009
Kent makes a good point that I did not see.
I didn't get it at first, just as he said, but the ability to delegate functions inline is powerful and the syntax is clean.
A cute story with a good point. I wonder why we programmers feel that bad code is faster when experience has taught us that it isn't.
Thursday, July 9, 2009
This post starts with calligraphy then factory floor setup then change management then personal change. Next is my favorite part "The four stages of competence" then a high level review of a book Theory U: Leading from the Future as it Emerges. It ends with a picture of a horseshoe. He deserves credit for tying so many things to a single vowel.
A long article that brings up many scary points. The one the sticks with me is "The magnitude of recent growth in the monetary base is literally moving off the charts, having increased from about $870 billion to almost $1.7 trillion in the last nine months." I see double digit inflation in our near future.
Wednesday, July 8, 2009
A good write up on estimation in a Lean (no iteration) software process.
A review of a new book by Barry Ritholtz, Bailout Nation: How Greed and Easy Money Corrupted Wall Street and Shook the World Economy. In the review are some interesting tidbits, like 1971 was a watershed moment as it was the first time the US government bailed out a private company (Lockheed) and the bailout of Chrysler in 1980 stopped the market from correcting the US automotive sector. I might have to read this book.
I'm glad I have NO plans of selling my houser anytime soon. This graph also shows how out of bounds the housing prices are compared to GDP.
I didn't think they would go there, but they went there. It is a crowded marketplace, but they do have good name. Now can they live up to it?
You have to respect a developer when they post their code and let others shred it, then repost it and shred it themselves. It is a good lesson and I look forward to his journey to clean code.
Tuesday, July 7, 2009
I have worked in both types of places and find most fall into area #2.
A fascinating 5-page story on how AIG was involved in the gobal financial meltdown. It just goes to show that bad management is bad business.
Monday, July 6, 2009
4 out of the top 10 cars with the most domestic content are made by Toyota (with #1 being the Camry).
A sensible top 10 list (for detail follow the link):
Quite a list for those who have the time.
Sunday, July 5, 2009
Friday, July 3, 2009
Thursday, July 2, 2009
A message on the Lean Software Development yahoo group by Tom Poppendieck that has a great email from Jim Womack on leadership.
Funny stuff from Codinghorror.
Wednesday, July 1, 2009
A great post with a new term "Canalizing" - as in like a canal.
Seth Godin on the future of writers and editors and how magazines and papers are dead. I think it is obvious, but I have been known to be wrong before.
I never plan on being a commuter from NJ to NY, but this short film was extremely well done!
I have had the same thoughts as Alistair. This response from David Anderson basically says we need limits because that's how we do it. I think WIP limits can help when you are learning (prevents you from sliding down the path of large amounts of WIP), but I think your goal would be to not need them as your process becomes more mature. A lean practitioner blogged a similar idea as The Fifth Primary Practice of Kanban, but kinda wimped out on his original idea of "Eliminate Kanban".
Interesting idea: work a fairly simple problem many times so the variations will be the techniques used. Now to make the time to do this!
Tuesday, June 30, 2009
Kent Beck on economics and other things. Most interestingly is that he is selling a 2 hour pair programming session on eBay! Started at$50 yesterday and after 12 hours has gone up above $200. I wonder what the final price will be?
This is just plain weird: "Some say that a major cause of the U.S. housing bubble was a surge in savings overseas, particularly in China, where the personal savings rate soared to 30 percent of disposable income...China’s “one child” policy, which created a huge surplus of men in the country, has driven up the cost of getting married...could account for as much as half of the increase in the country’s household savings since 1990."
Takes the popular MVC pattern and shows you their approach.
Details on the CLI that make sense.
Monday, June 29, 2009
This is neat!
I like the term fabricated complexity and I believe it is a major component in most systems.The post has some good points but it does go quite deep on metrics so beware.
Some decent code that the author refactors and makes even better.
Saturday, June 27, 2009
A great way to describe a Kanban software process. I'm not sure why there is a person who only does deploy, but it's still a good story.
Starts off with his most negative people series Greg the secretive, Jon the incompetent, Gary the not invented here, and Roger the refactorer. This is followed by good advice summarized here (the details are worth reading):
1. It pays to share everything you know.
2. Give people credit, even if they don't deserve it.
3. Don't play any blame games.
4. When the code is good enough, stop working on it.
5. Work hard.
6. Lighten up.
7. Take time for yourself and your family.
8. Keep studying.
9. Keep regular hours.
10. Don't fool with fools who'll turn away.
Good ideas to try.
Friday, June 26, 2009
I never knew that the Sumerians used a "...sexagesimal (base 60) number system" by using the parts of the fingers (minus the thumb) to count to 12 on one hand. Sometimes, history is more fascinating than fiction.