Cool Code
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Peter Cooper on Aug 18, 2006
Ruby Reports (a.k.a. Ruport) is a free library and toolset for Ruby that makes building reporting applications easy developed by Gregory Brown. It's available under the Ruby and GNU GPL 2 licenses.
Ruport can acquire data from databases and files and provides tools to manipulate the data as necessary for the required reports which it can output in HTML, PDF, CSV and plain-text formats (also to e-mail). Ruport is undergoing constant development and also has an IRC channel at #ruport on irc.freenode.net if you want to speak to the developers directly. As an ongoing project, Ruport is looking for more contributors and developers, especially those with experience of reporting and data manipulation.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Fair Trade Software Licensing - A Guide to Neo4j Licensing Options
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
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.
No comments
Watch Thread Reply