monotony in development

| 1 Comment
As I keep working on the same types of problems in my $job, I don't have much to say in my posts here. I have been working on the same problems for a few weeks, and I have run out of neat things to talk about.

Here is hoping that I have something interesting to talk about tomorrow.

1 Comment

That's unfortunate. I've always held that code development should be fairly free of monotony. That once you've solved a given problem, you need never solve it again; you can just reuse what you did last time. Reuse of previous solutions is the key to moving on to more interesting things. See CPAN. :)

About this Entry

This page contains a single entry by leonard published on May 30, 2010 9:18 PM.

code quality vs. economics (aka, the bottom line matters in your code) was the previous entry in this blog.

code quality vs. economics part II is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.