Though I enjoy writing these short-attenion-span notes, I certainly haven't published 1000 posts. Here's what's going on:
The greacen zone runs on the netscrap.com publishing system. Netscrap has a few hundred posts already, thus the high numbers.
The fruit blog also runs on this jalopey.
What's the publishing system? If you've been reading, you already know that it's heart and soul is zombie technology. The netcrap.com publishing system is buggy, but it's super- efficient. Check out this month's netscrap.com comscore numbers if you doubt.
Where's this going? No idea. Isn't that exciting? Just like several of the startups I've worked for. At this point I'm considering tossing the publishing platform's core onto google code under the MSL just like I did with bashWebTest.
some thoughts:
Thanks for reading!
A few years ago I wrote (in my spare time) a little test harness around some simple command-line utilities. I wanted something to help me answer some simple questions about what was going on some large clusters of servers. Rather than clicking through a bunch of nicely formatted pages, I wanted something to make a bunch of http requests and give me a 'yes' or 'no' about the response. The trick (for me) was to try to run it on some server in the cluster which was running a really lean installation of Linux. No frills.
I could have probably compiled a jar & dropped it onto the server... but I couldn't edit & recompile a class on the server. I could probably have run a perl script, (geeze why didn't I just write it in perl?) but I think the WWW-Mechanize module wasn't installed. Who knows... anyway, I ended up stumbling upon curl and decided to write a wrapper around it using simple bash scripts.
Guess what? It worked. It was handy. Guess what? I used it at a few jobs since I wrote it. Guess what? It's still (somewhat) handy. So today (or yesterday) I give something back to the internets and interwebs that haz given me so much. I offer:
Tests are pretty simple. I'll toss a few test examples on this blizzog and onto the wiki on code.goog over the next few weeks. If you have any interest at all in using something klunky, and somewhat functional, please contact me and I'll help you get started.
Code.goog doesn't have a way to select it, but I planned on distributing the source under the 'MSL' license.
Anyway, enjoy!
I think back to our problem at kodak: we needed to hire super-geniuses to work on a completely custom-built system. This was before hibernate, before spring/pico, I think it was before the JSP 2.x spec even. We needed to hire people who could 'hit the ground running' and contribute without a hige ramp-up. We needed to perform a thorough search without booking the whole team for all-day interview sessions.
Part of our solution came with a formal phone screen. Once we started applying a standard approach to all candidates we were able to do (something approaching) an apples to apples comparison between the top candidates. We were also able to weed out some bozos who had 10+ years of experience but never encountered an application's error log.
Through these questions you can get an idea about how seasoned a candidate is: have they encountered a metrics program? Have they worked on a performance testing project? Do they understand the challenges with managing software deployments in the testing cycle. The 'what's in a good bug' question can open up discussion in a number of areas: is the candidate aware of the connection between a feature, the server source, the browser's role... You can learn a lot from this one.
The goal here is twofold: first, to see whether the candidate can handle themselves in a 'go get it done' environment. Inevitably, there will come a time (daily in most of the places I've worked) when there's a bug and someone has to do the 'deep dive' to find out details about the problem (one bright QA guy coined the term 'qa forensics') by ssh-ing to the server, finding and watching all available logs while reproducing the problem. Can they search google to get themselves unstuck?
Second, if they mention LINUX or UNIX on their resume, they better damn well know that ls -l is how to get a timestamp of a file. It's worth having a few easy questions about topics that a QA engineer should encounter on a daily (hourly) basis.
The HTTP method question is something you can use to make sure the candidate fully answered the earlier section about performance testing.
There is another table Address with columns id, street, city, state, zip, person_id
Yes these are pretty lightweight questions. Someone who aces this section should be pretty comfortable getting test results from a database. If you're lucky, you can also find someone willing to own the application of db changes to your test environment. The really good candidates will be able to give you a bunch of ways to complete the second tasks: joins, sub queries, etc.
I would generally only ask these questions when dealing with a team lead candidate or someone going on the manager track.
It's worth noting that I'll usually tell a candidate the answer to a question if they get it wrong or can't answer. It's the interviewer's call about how to deal with this. It doesn't hurt to always sell your company, and a company that supports its team is a company where people want to work.
The interviewer has the option of scoring the candidate as a whole (1-move now, 2-interview after the other 1s, or 3-pass...) or by section. I'll let you come up with your own scoring system.
By the end of this line of questioning, the interviewer should have a pretty decent picture of your candidate, the accuracy of their resume, and most importantly whether it's worth calling them into the office for a face-to-face interview with your team -- which is usually a big investment!
I'll put together notes on the resume-sorting and interview processes for future posts.
What is it? It's dead technology, but it's still walking around your house, making a mess.
While I'm not really a Luddite, I think we could all benefit from spending some quality time with something that's past its time. Part of the problem with software (in general) and especially some of the open source doodads is the bloat and excess that a project tends to accumulate.
You already know the bloat:
Bloat leads to fear, fear to hatred, hatred to the dark side: abandoning the thing that was once useful. I ran across railo the other day and WOW! They've put together an open-source engine that runs cfml spaghetti, and amazingly enough, I got this site to run on first shot (more easily than most of the megabytes of open source crap I've tried). Still, I'm left with more questions than answers:
Which brings me to the REAL point of this post. I'll announce soon the release of two new open-source projects: TestingTesting and bashWebTest. Both are entirely based on zombie technology: Cold Fusion and Bash.
Ok, so maybe Bash isn't zombie technology after all. But is bash your go-to technology when you need to do some web testing? No? Well maybe this tool is born-zombie.
