Transactions without Transactions
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Deborah Hartmann Preuss on Sep 15, 2006
Transforming Software Delivery: An IBM Rational Case Study
Agile Development: A Manager's Roadmap for Success
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
The problem, of course, is how to tell whether the advice being given is good; whether the person giving the advice is good at agile or not, whether the person understands the situation or not.
I do not favour certification. It's expensive and penalises those who can do a great job but don't have a certificate. What would I put in its place? Well, there must be about 100 people who I'd be prepared to say have some level of competence at agility. Of course, some of these are better than others. But why should anyone value my opinion on who I think understands 'agile'? Well, if enough other people rated my ability high enough, other people might have confidence in my ability and my opinions of other folks' ability. Of course, I might value some people's opinions higher than others - perhaps 1 vote from Ron Jeffries would be worth 5 from Deb Hartmann or equivalent; 10 from me or equivalent.
Do people use references any more?
I find that big businesses don't make much so of them (more of a formality) but smaller companies take them more seriously.
Would they really accept a certificate without also asking to speak with former colleagues? Can we help those doing the hiring ask the right questions, so they can spot hacks? Maybe this is another solution to the problem of accreditation, as Paul notes in talking about "votes" of confidence.
Would you be certified based on how much you value individuals and interactions over process and tools? How much I welcome changing requirements?
Menlo Innovations description of Extreme Interviewing sounds like a better approach than a certificate.
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
3 comments
Watch Thread Reply