If only code was poetry, I’d be the most prolific jibaro on the block right now with my acclimation to the WordPress interface and adding new bells and whistles to the website.
Some of the changes, messing with text layouts and adding the right amount of sidebar content, is a lot easier to do than others, like messing with the widget codes to appear exactly as I would like. Sometimes I hunger for the days of coding out the HTML also entirely by hand and knowing the purpose behind all the lines of code. I think that was my inner 12-year-old talking and remembering what it was like to put together a graphic display with BASIC on his shiny new Commodore VIC-20. Yeah, those were the good old days of block text.
Today, all I need to do is drag-and-drop a widget here, mess with some settings there, and Poof! instant layout. Clean, simple and leaving me no smarter than when I started. So that’s what I really miss about knowing my website inside-and-out, even when there is a tiny mistake, one that I’m sure no one else can see, I know it can be fixed if I plug away at it hard enough. With all this “easy” code, I have to wait for an upgrade to come along or just suck it.
I’m guessing I have the same mentality when it comes to some of the more difficult aspects of my writing life. I’d rather tough out writing a review or putting together a deep lesson plan in favor of making things easier by looking at some pre-established models. Same with manuscript revision, I’ve been stuck on a chronological layout of poems instead of seeing what makes the most sense thematically.  This is usually around the time I think I’ll go back to the drawing board and start all over but maybe the wiser move might be to just stop where I’m at and be honest about what is and isn’t working in the manuscript. It would sure be quicker than going all the way back to square one.
Continue reading “Code is Poetry”