‘Scalable system patterns’ links for October 30th, 2010

The BIG Software Blog: “Scalability patterns and an interesting story…”

Lori Mac Vittie, of F5 Networks, comments on the above piece on High Scalability and the need for ‘Devops’ to really pull it off: “Applying Scalability Patterns To Infrastructure Architecture”

Pragmatic Programming Techniques: Ricky Ho: “Scalable System Design Patterns”

Pragmatic Programming Techniques: Ricky Ho: “Scalable System Design”

Pew: Rate of people moving into Philly increasing, rate of people leaving decreasing

“Pew Study Finds an Increase in People Moving Into Philadelphia, Outpacing the Rise in Departures”.

We still have a long way to go, but it is proof positive that Philadelphia’s long march towards being a great place to live and work is starting to get recognized.

Check out these upcoming events: Ignite Philly and TEDXPhilly.

Update: I’ve modified the headline of this post (previously: “Pew: More moving INTO Philly than leaving”) to better reflect the report’s findings. Terrific progress being made nevertheless. Go Philly!

Programming practice links for October 18, 2010

mockyblog: “Programmers: how to make the systems guy love you” – common sense advice that you’d be surprised how many don’t follow.

InfoQ: Abel-Avram: “10 Suggestions for the Architect of an Agile Team” – if you are practicing an agile-lite process, are a senior developer on a team, and have helped usher systems to launch, you will have probably practiced these 10 pieces of advice. I’m not sure if these are applicable practices for architects and am not sure they are applicable for a team that is practicing pure agile.

Artima: Bill Venners: “Tracer Bullets and Prototypes: A Conversation with Andy Hunt and Dave Thomas, Part VIII” – a long rumination on the ‘Start with a vertical slice’ tip from the previous link.

On Visualizing Iterative Waterfall

Go read Jon Moore’s latest piece “The Power of Visualizing Iterative Waterfall”: “the most powerful reason to start visualizing the flow is that it shows you exactly what parts of your process you should change, and when. There’s nothing like being able to show a product manager that their availability is driving overall throughput to encourage spending more time with the team.”