I drank the koolaid a few years ago on the usefulness of test-driven development. I have Perl and the Perl community to thank for that. chromatic outlines the history of Perl’s test-infected culture in a recent post.
an eddy in the bitstream
I drank the koolaid a few years ago on the usefulness of test-driven development. I have Perl and the Perl community to thank for that. chromatic outlines the history of Perl’s test-infected culture in a recent post.
Roy resurrected the Swish-e project nearly 10 years ago. There’s a nice interview with him out recently, in which he says “there really isn’t anything I can’t do with Perl and my favorite indexing tool, Swish-e” — which is exactly my experience too.
Thanks, Roy.
My friend Brett is writing a novel. I read the first version some years ago, and the second version after that. This third take is a good read so far.
No, it’s not what I suffer from the lack of (as in sleep). It’s Representational State Transfer. It’s been a buzzword for a few years now. I’m just now reading about it, and thought I would include some highlights here for my own reference.
From the URL above, REST exhibits the following characteristics:
Trying to make my CatalystX::CRUD project more RESTful.
If I needed to explain REST to my wife, I could refer her to this.
The Wikipedia CRUD article maps the RESTful verbs to CRUD and SQL actions like so:
Operation | SQL | HTTP |
---|---|---|
Create | INSERT | POST |
Read (Retrieve) | SELECT | GET |
Update | UPDATE | PUT |
Delete (Destroy) | DELETE | DELETE |
However, important to note that REST != CRUD.
update to original post: Another good REST article.
And REST for my kids.
Long before I was a computer programmer I was an essay writer, a songwriter, a poet. When I discovered Perl, I found the transition to programming very natural. I had always played with computers, back to the IBM PC and Macintosh circa 1984. My first program was in BASIC, in 1985. It was a ‘choose your own adventure’-type program. Even then, I wanted to combine prose with code. It was just Making Stuff with Words. I didn’t differentiate.
chromatic suggests Perl programmers can improve their code by thinking in terms of sentences and paragraphs. Best practices. Makes perfect sense to me. When my friends ask me about my work I tell them I’m a writer, that a good piece of Perl code has the same structure and thought behind it as a well-written essay, and that I practice the art of writing every day. It’s just that the language I write in is Perl, not English. I know my metaphor is lost on most non-programmers. But I trust some people understand.
© 2024 peknet
Theme by Anders Noren — Up ↑