In free software, patches are considerably more useful than complaints.
It's easy to forget.
Welcome to End Point’s blog
Ongoing observations by End Point people.
Friday, January 16, 2009
Subscribe to:
Post Comments (Atom)
Archive
-
►
2012
(17)
-
►
January
(14)
- Protecting and auditing your secure PostgreSQL dat...
- Linux unshare -m for per-process private filesyste...
- Our SoftLayer API tools
- MySQL replication monitoring on Ubuntu 10.04 with ...
- Importing Data with RailsAdmin
- Using Disqus and Ruby on Rails
- Interchange loops using DBI Slice
- ActiveRecord Callbacks for Order Processing in Eco...
- Take a snapshot in Cucumber and sync it with Dropb...
- Introducing Piggybak: A Mountable Ruby on Rails Ec...
- Some great press for College District
- Ruby on Rails: Attributes Management through Right...
- Automating removal of SSH key patterns
- Interchange Search Caching with "Permanent More"
-
►
January
(14)
-
►
2011
(144)
-
►
December
(17)
- Importing Comments into Disqus using Rails
- Labeling input boxes including passwords
- Converting CentOS 6 to RHEL 6
- Rails Request-Based Routing Constraints in Spree
- Modifying Models in Rails Migrations
- Nifty In-Button Confirmation
- Sanitizing supposed UTF-8 data
- Hurray for tracking configuration files in source ...
- Preventing Global Variables in JavaScript
- Using Gmail at Work
- Liquid Galaxy at Le Pavillon de l'Arsenal in Paris...
- Sunspot, Solr, Rails: Working with Results
- Christmas Tree Commerce in 2011
- Running Integration Tests in Webkit Without a Brow...
- Semaphore limits and many Apache instances on Linu...
- Working with constants in Ruby
- Performing Bulk Edits in Rails: Part 2
-
►
November
(8)
- Kamelopard Release
- Book Recommendation: Ghost in the Wires
- Global Variables in Interchange Jobs
- Appending one PDF to another using PDF Toolkit
- Performing Bulk Edits in Rails: Part 1
- Advanced Rights and Roles Management in Rails
- Finding PostgreSQL temporary_file problems with ta...
- Double habtm Relationship Between Models
-
►
October
(7)
- RPM building: Fedora's _sharedstatedir
- A comparison of JasperSoft iReport and Pentaho Rep...
- Using the new version of imapfilter with mutt
- Rails Controllers and Transactions
- PG West 2011 Re-cap
- Viewing schema changes over time with check_postgr...
- CRUD, RESTful, and JSON for Address Management in ...
-
►
December
(17)
Contributors
- Kiel
- Mike Farmer
- Josh Williams
- Brian Buchalter
- Brian Gadoury
- Ron Phipps
- Nick Alexander
- Jeff Boes
- Joshua Tolley
- Marina Lohova
- David Christensen
- Mark Johnson
- Steph Skardal
- Brian J. Miller
- Zed Jensen
- Ben Goldstein
- Greg Sabino Mullane
- Brian Buchalter
- Szymon Guz
- Carl Bailey
- Evan Tann
- Jon Jensen
- Greg
- Adam Vollrath
- Richard Templet
2 comments:
Useful, yes. Practical, no. Not for those who can't code. In my opinion, a developer who gives away or sells his software, should brace himself for feedback that it's not always sugar coated. It's part of the job I am afraid. Free/free software or not.
Hi, Eugenia. Since it was a note to self by a programmer, I'm going to say that in that context it stands and is very practical.
Hearing what you said I'd simply rephrase it thus: "For a programmer who knows the implementation language of a project to complain about some bug or lack of documentation is less productive all around than to actually contribute a fix."
Of course we can't always contribute patches, and in those cases commenting may still draw attention to something that might otherwise be overlooked or thought unimportant. But sometimes we're just lazy and don't do the extra bit of work to make a patch.
Post a Comment