Rocky Bernstein has been working a new Perl debugger called Devel::Trepan. I came across some discussion in a git pull request for this project a while back and I’ve been thinking of this blog post since that time. Rocky has his own unique coding style. It’s not too out there. There are some truly oddball styles on CPAN. But there a few oddities that stand out. First, he puts various use lines before the package declaration.
Back in November of 2010, I wrote an entry on this blog titled My Programming-Related Todo List. The title is a bit misleading since it was really more of a todo ‘wish’ list than a realistic list of things I could get done. I figured I’d revisit it (and depress myself in the process) to see everything I hadn’t done. CPAN Search $NEXT Well, I didn’t do it, but a bunch of other people did, so at least I can take it off my list.
I read about tofu misozuke on the vegan subreddit recently and I was intrigued. The description compared it to cheese, particularly blue cheese, and I was sold. I love pungent, strong-tasting foods. I just got my order today. Holy crap, it’s intense! The blue cheese comparison is quite apt. It’s also similar to Tofu ru (or dou fu ru in the proper Chinese pronunciation). I had mine on a slice of toast and it was perfect.
(Oops, I accidentally deleted this entry and had to restore it so all the comments are gone. Sorry, commenters.) I’ve often heard it said in the Perl community that hiring Perl developers is hard. This comes from both developers as well as people relaying information from managers and recruiters. At MaxMind, where I work, we recently posted a job opening. We only posted it to the Perl jobs site to start, and I mentioned it in a blog posting.
The company I work at has posted a new job opening for a senior developer. So if you’ve always wanted to work at a job with me (for some bizarre reason) now’s your chance. Alternatively, consider yourself warned. Ok, here’s some real info about the position. You’d be a senior developer on a small tech team (me as team lead, two other devs, one sysadmin/dev, one CEO who needs to code less).
In discussions on Hacker News I’ve said several times that I think copyright should be abolished. Some people agree, but I often get a reply asking how I expect programmers, musicians, or authors to make a living in such a world. Before I address that question, I’ll take a brief digression. While I’m all for abolishing copyright, that doesn’t mean I’m against all property rights. Physical property rights are a good thing.
I’ve removed the per-category Atom feeds from the sidebar, and I’m going to stop categorizing new entries. There are a couple reasons. First, the three categories are somewhat limiting. My next entry will not fall strictly into the AR-Veg, Personal, or Programming categories. Second, the vast majority of my entries are about programming, and that will probably continue to be true. I realized that most anything I’d categorize as Personal is either trivial or something I don’t want to share on a blog.
I recently uploaded a new distro to CPAN recently called Type. The concepts are largely on Moose’s built-in type system, but it’s a standalone distribution. Right now this is all very alpha, and the current release is not intended for use by anyone. I’ve released so people can take a look at critique the design. I’ve tried to remedy some of the problems that Moose’s type system has. MooseX::Types fixes some of these problems but then introduces its own.
For that coworker who won’t stop “optimizing” his or her code, I give you my rules of optimization: Don’t optimize Don’t optimize, I’m serious Don’t optimize without benchmarking first Don’t benchmark without profiling first See rule #1 Edit: A co-worker suggested a step 4.5 of “Take a coffee break”. I don’t like coffee, but I like the spirit of the suggestion. Comments Chas. Owens, on 2012-04-26 07:43, said:
At work we have some git repos that were converted from CVS originally created back in 2002 or so. A lot of the things in these repos is cruft and could be deleted. I wrote a little git command to report the most recent commit date for each thing in the current directory. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 #!