« Fiction Interlude: Charlotte Street | Main | A photography book to consider. »

18 June 2013


I read the article and thought "Hey, I can use Ruby on Rails, and DANG, I'm underpaid."

Then I committed the number one mistake on the Internet -- I read the comments.

And now I have learned that all web programmers should be set on fire.

How hard do you think it is to learn some programming? (More for my own use than anything.) And do "web developers" worry about security issues and back-end stuff on their websites? Those are the issues that make me worry...

Sorry you're underpaid. Time to print that article out and demand a raise!

RE: the comments, with the exception of this site (obviously) I make it a point to never ever read comments on anything. They pretty much always make me sad.

Oh, I'm not a web programmer. Just a public librarian, which as you know (Bob) means "jack of all trades" -- plumber, copier repair, triage nurse, and nowadays, part-time IT.

So all of us had to learn to fiddle with the library website, because -- working for the Gummint -- we can't afford a REAL coder. Some are better at it than others; I can fix dead links or change style sheets or plug in survey forms, but I sure wouldn't try anything complicated.

As to how hard it is to learn -- well, I'd say that it's like home repair. It isn't very hard to learn the basics (replace the hinges on the door, ungunk the sink, patch the drywall, etc.) All it takes is patience, and a willingness to follow directions and avoid the temptation to cut corners or get "creative".

If I started getting into the more advanced stuff -- fiddling with the electrical wiring, say, or putting concrete piers in the basement -- I'd prefer to go with someone with more expertise.

And once you start talking about building a house (or a website!) from scratch, it's definitely time to call in the professionals!

You forgot "police officer" and "social worker" as part of your library duties.
Yeah, I can fiddle with HTML and I did know something about style sheets at one time, but I'm always stymied by more behind-the-scenes stuff, like domain setup, DNS tinkering, etc. I just was curious about how long it really takes to become a "web developer." I've always been okay at rustling up some streams of income, but man, sometimes I dream about developing a skill of some kind and pulling down big bucks for even a couple years. Being a librarian has its positives, but making big bucks is not among them.

The comments to this entry are closed.

Support CR: Shop at Powell's

Support CR: Shop at Amazon

Search Citizen Reader

  • WWW
Blog powered by Typepad