ugh..
Originally shared by Sean McCullough
Skins, Updates, More
1 min read
Just caught up 10 days worth of Neighborhood posts. I now have Vox fatigue combined with Vox guilt. I didn't even read comments, for shame :( After this post I'll need to check on the 'ol LiveJournal Friends page. Don't even ask about the umpteem BlogLines blogs stuck at 200 posts...
Hi5 has a new Skins system that actually can make profile pages look good. I had some input early on and made sure Vox and the SixApart styles were part of the inspiration. It's coming out really well and we've received over 200 submissions. Check out the snazzy new profile page? Designers can check out the specs page.
Embeds are evil. They mess up divs and tables and are often pasted in haphazardly. Amit came up with an amazing solution. Use JTidy to clean up the user submitted content. Tags match and broken html goes bye-bye!
Now back to the super-secret Hi5 Project Funk.
Bay XP Meeting Roundup 8/23/2006
2 min read
BayXP (The Bay Area Extreme Programming Group) had a small meeting at the offices of ThoughtWorks here in San Francisco. The topic was interesting things learned at the Agile 2006 conference.
I found a number of items to add to my reading list, Including Refactoring Databases and Working Effectively with Legacy Code. (See Links below)
Topics of discussion from the meeting included
- Coding Dojo - how to get hang of test-first development and Pair programming.
- A lot of talk about how Rails stacks up against upteen different Java Frameworks.
- The TDD Pair Programming Game is an interesting way of pairing that seems to make sense. It's like a dance. I write a failing test, you implement, then I refactor, then you write a test, etc.
- The best name for a talk that I've seen in a long time was Crushing Fear Under the Iron Heel of Action. It explored how to deal with team dynamics in an Agile environment, mostly by saying "What's the worst thing that can happen".
- Found out about a web site called Developer Testing. Another thing to add to the RSS reader...
- There was a short talk about Code Debt. Some people are surmising that Code Debt should be publicly disclosed in a companies SEC S4 forms via Sarbanes-Oxley. One interesting quote was that code is an asset and you should maintain that asset properly because assets "increase the means of production". If you don't maintain code properly and use correct process your software becomes a liability. (Or course that begs the question of who defines the Generally Acceptable Coding Practices (GACP!)
