http://search.cpan.org/~sargie/Data-Google-Visualization-Dat...
This made me more conscientious about what I release ;-)
11–20 of 93 posts
http://search.cpan.org/~sargie/Data-Google-Visualization-Dat...
This made me more conscientious about what I release ;-)
The article suggest reading code, which I agree is a good way to improve programming skills. But I'm a bit unsure what to do with the advice to read the linux source code. Where would you start? I find the only way to actually get to reading code, is if you have a need to understand some part of it (e.g. to fix a bug or add a feature). So perhaps a more actionable proposal is to try to fix a bug, preferably one you c…
Also, randomly: I started putting bug bounties on my code on CPAN: http://search.cpan.org/~sargie/Data-Google-Visualization-Dat... This made me more conscientious about what I release ;-)
(No, doesn't count as a bug, really)
Learning Javascript changed my Perl for the ... more fun to write. Possibly better, too. I've started passing around coderefs as arguments to functions a lot more recently, and allowing people who use my APIs to do just that... I've been writing code that allows you to describe a website in data and at a high level recently, and builds you up all the methods you need to interact with it. In general, when people need…
It essentially teaches you functional programming in Perl.
So many times I've encountered something and thought, "I can't believe that people are actually expected to use this software."
It was bad from a user perspective: difficult to use, slow, tedious to do what you actually needed to do, unable to "get there from here".
Then once I looked under the hood, it was often worse: built upon a horribly designed data structure, inflexible with constants where there should have been parameters, no apparent thought put into its use, too many violations of acceptable practice to mention, looking as if it evolved haphazardly (which it probably did).
It's easy to bitch about stuff like this, but you often have to go to the next level to do something about it. It's amazing how much rethinking you have to do and how many tools you have to build to turn horrible software into what should have "obviously" been done in the first place.
Easier said than done. And often, some of my best learning experiences.
I got a "Database Connection Error" (I am sure your server got hit hard with being top 5 on HN). :) The irony makes me giddy.
Earlier quoted context omitted.
I've been trying to get better at this myself. Although, you do feel foolish when you bang your head against something for six hours, and then you get your first (correct) answer on stack overflow five minutes after you post. Still, if you're not feeling foolish often, you're not learning. Competence is deadly that way.
Learning to find the answer yourself is -way- more helpful than having it provided to you. Don't regret those 6 hours. It's a process.
StackOverflow isn't a total no-no, just don't make it priority 1.
I got a "Database Connection Error" (I am sure your server got hit hard with being top 5 on HN). :) The irony makes me giddy.