Check out this potential implementation of rounded corners with CSS.
http://24ways.org/2006/rounded-corner-boxes-the-css3-way
This is exactly what I'm looking for. If only I could do this right now.
Tuesday, May 27, 2008
Thursday, May 22, 2008
How to write clear instructions, Part 1
Let's say you're in a new contract job, and you're getting a crash course in how to set up and work in their development environment. It's a huge, complicated system. It would be great if there was clear documentation on how to accomplish specific tasks? And what tools are used for what (especially if you're only using each one for a small portion of the project) . But nobody's taken the time to create the docs.
It's all second nature to the regular members of the team. Coming from the outside, it all looks a bit like voodoo. When they show you how to do things, they just rush through it and switch screens without mentioning what the new one is. They just can't help it. They don't think about it in their day to day work.
They don't have step-by-step instructions on how to do it. You'll have to write those for yourself.
While they show you, write it down step by step. If they keep going before you can write it down, ask them to go back to where you lost them. Write down the file paths, and avoid short-hand. You need it as detailed as possible.
Don't assume that you'll remember it all later. Try to reproduce the steps right away, following your own notes. Missed a step? Go back and show them your notes, and where you got stuck. Write down what you missed, and try again to reproduce the steps and accomplish the task.
Eventually, it'll be second nature to you. But don't abandon your notes. See if there is a wiki or other knowledge sharing system that you can post them to, so the next person can use them.
It's all second nature to the regular members of the team. Coming from the outside, it all looks a bit like voodoo. When they show you how to do things, they just rush through it and switch screens without mentioning what the new one is. They just can't help it. They don't think about it in their day to day work.
They don't have step-by-step instructions on how to do it. You'll have to write those for yourself.
While they show you, write it down step by step. If they keep going before you can write it down, ask them to go back to where you lost them. Write down the file paths, and avoid short-hand. You need it as detailed as possible.
Don't assume that you'll remember it all later. Try to reproduce the steps right away, following your own notes. Missed a step? Go back and show them your notes, and where you got stuck. Write down what you missed, and try again to reproduce the steps and accomplish the task.
Eventually, it'll be second nature to you. But don't abandon your notes. See if there is a wiki or other knowledge sharing system that you can post them to, so the next person can use them.
Thursday, May 8, 2008
If I go too long without coding, I start going a little nuts...
Yep. My brain needs a steady diet of challenges to play with.
When the workday requires meetings and reports and a complete absence of programming joy, I rely on my recreational coding in the evening. Actually, even when my workday is full of coding, I still like to play with ideas and code in the evening.
Dear Flash and Flex Recruiters,
While I appreciate that you are looking for developers, the spamming has got to stop. Sending generic email for permanent positions, to a group of contractors is pretty silly if not rude.
Some things about me you should know, as a recruiter:
1. I do contract consulting, and I'm not looking for a permanent job.
2. Relocating to another city is not in the cards...unless it's an absolutely amazing job, and even then it's unlikely. I'm based in San Francisco.
3. Yes, that's my hourly rate. Do remember that I pay for all of my own overhead, equipment, materials, etc.
Please don't bother, if the job doesn't fit this bare minimum.
Some things about me you should know, as a recruiter:
1. I do contract consulting, and I'm not looking for a permanent job.
2. Relocating to another city is not in the cards...unless it's an absolutely amazing job, and even then it's unlikely. I'm based in San Francisco.
3. Yes, that's my hourly rate. Do remember that I pay for all of my own overhead, equipment, materials, etc.
Please don't bother, if the job doesn't fit this bare minimum.
Thursday, May 1, 2008
Cha-Cha-Changes
Life is exceptionally full right now, with both work and real life.
On the work front: I'm starting a new contract job next week, with a very large company. The people are really great, and I'm really looking forward to the work. I'll be doing mostly User Interface, in HTML and CSS...with some AJAX (perhaps). It's not in the most technically challenging segment of my skill set, but their devotion to user experience closed the deal for me.
On the GalaxyGoo front: We're taking the Cell Project to the Maker Faire this weekend! For two and a half days I'll be playing with clay all day and building 3-D models of cells...and conducting workshops for students and teachers. We've got our helpers all lined up, and we're ready to have a thoroughly artsy-geeky wonderful weekend.
On the work front: I'm starting a new contract job next week, with a very large company. The people are really great, and I'm really looking forward to the work. I'll be doing mostly User Interface, in HTML and CSS...with some AJAX (perhaps). It's not in the most technically challenging segment of my skill set, but their devotion to user experience closed the deal for me.
On the GalaxyGoo front: We're taking the Cell Project to the Maker Faire this weekend! For two and a half days I'll be playing with clay all day and building 3-D models of cells...and conducting workshops for students and teachers. We've got our helpers all lined up, and we're ready to have a thoroughly artsy-geeky wonderful weekend.
Subscribe to:
Posts (Atom)
