The Good
- Every project has room for failure. Clever people plan around failure, and have contingencies in place.
- Selenium is an awesome tool for browser/user acceptance testing. I'm embarrassed to say I've known about this tool for years, but have not used it. In my defence, though, all I've been working on lately is web services and other integration type work.
- I really like Atlassian's "10 minutes from checkout to coding" policy. It forces you to keep your builds portable. VMs to deploy test environments means you don't have to step on your team members toes.
- Sharing development environments is like sharing needles.
- Issue Trackers are a lot better at maintaining the paper trail related to a change compared to email. Seems obvious when you think about it, doesn't it?
- Continuous Integration can help you catch problems early, and the value of this grows with the size of the team, and the complexity of the system under test.
- CI + Remote Agents + Selenium = good baseline for automated browser testing.
- Atlassian folks are awesome!
The Bad
- ESB/SOA is a lot of snake oil
- SOAP is expensive.
- Benchmarks are extremely hard to get right. Platform, OS, Servers, phase of moon can lead to wildly varying results.
The Ugly
- There are people who check in their IDEs along with their workspaces. .Net people are excused, because they are sad anyway :), but really, why check in an entire eclipse installation? m2eclipse can set up your project for you from checkout in a matter of seconds. (The whole maven-hate thing needs another post to address).
0 comments:
Post a Comment