Had my hips resurfaced at 50, ruptured disk repaired at 57, carpal and cubital tunnel repaired this year at 61, and now my A1C is in pre-diabetic range! Not telling my wife until after the Holidays since everyone enjoys the cookies she makes (hoping she doesn't notice me avoiding them). I'll be picking back up the HIIT training sessions and avoiding the snack drawers at work, but yah, things degrade! I blame slacking on exercise and over indulging for my A1C decline but there's no avoiding time!

When my wife was pregnant with our last child (daughter) her blood tests came back indicating a high likelihood of a Down syndrome. The technicians were so sad and apologetic to us and seemed so sure of their diagnosis. We decided not to do a test of the amniotic fluid because it increased risk to the baby and if it already had problems, why add more. Well, long story short, she was born normal (well, she has Tourette syndrome, like two of our other children) but is, among other things, a musical prodigy, good student, highly intelligent, and most of all, very kind.

So? I consume enough coffee during a day of coding to drown approximately 27 people in my own urine!

I've had many male bosses and two female bosses. The male bosses have ranged from excellent to OK, but no one really bad, just a bit flakey. The two female bosses are night and day though.

My worst boss was my first female boss; she was an overbearing bulldozer who seemed more concerned with building her empire than anything else. She actually drove one of her suboridinates crazy and almost got herself killed by him; he's in prison now.

My current boss, a female, is the best I've ever had. She is a former engineer, so she knows technology, and how to manage projects. She builds strong working relationships with partnering groups. She actually listens to me and acts on many of my suggestions. She knows her subordinates well and figures out how to motivate and reward us for our efforts, especially when we go beyond the call of duty.

She's the kind of boss that I would switch jobs in order to continue working for.

I too am a C programmer (embedded) who is learning web programming. I liken C programming to weaving fabric (a program) out of a single type of yarn (c language). Web programming is like making your own yarn out of HTML, CSS, JavaScript/PHP/whatever, then weaving it into the fabric. It's taking some getting used to. I've been searching online for free tutorials and getting books at my local library, which has some recent good additions. I have the luxury of a wife who knows nothing about internet technology and doing her own blog; I get to provide technical support so along with my bookwork I'm getting some practical hands-on experience too. I also have taken up the hobby of writing web based video games which gives me more hands on experience. I think that basically it takes some project(s) to pursue in the area you want to learn and then making the time to pursue them.

Just write it on a sticky note and put it under your keyboard; this is a time honored practice of millions of users, and that many people CAN'T be wrong!

Perhaps if fixed bugs periodically re-appear in the product then the revision control system is broken? Software testing is important (regression testing seems especially needed in this case) but so is revision conrol.

I suggest doing castings of both of her hands.

While somewhat humorous, that is a pretty uninformed statement. I would hazard to say that a majority of people coming out of HS these days do not know how to learn at a college level (I didn't) but there are classes as college that do teach you how to learn (effective reading, how to study for various tests, how to think critically, etc.). After taking a study class my sophomore year in college I went from being a 2.0 student to a 3.5+ student (I'm now back in college going for my MS degree and am at 3.95 for my grad classes). Lots of this is due to knowing how to study, which I was taught when in college.

I used to be a cop and I did a LOT of traffic stops. In training and certification to use a radar gun they train you to look at the vehicle whose speed you're going to measure and make an estimate of their speed before using the radar, then compare the results. This was a practice in Washington state but I would not be surprised if it is common everywhere. After a while you get very good at estimating speeds and find yourself generally guessing the correct speed +/- 1 MPH. When you write your subsequent traffic stop summary you include a sentence stating that your observed a vehicle that appeared to be speeding and your visual estimation followed by the radar measured speed. This gets the officer trained to look at what's being measured rather than just sitting there with the radar pointed back over his shoulder waiting for something fast to come through which then builds credible speed estimation and descrimination into his testimony and also gets past the problem of accidentally radaring the Cesna 150 that flew overhead at 80 mph while erroneously attaching that speed to grandma who was doing the speed limit. In short, anybody who does a lot of anything reasonably well gets good at it - cops do a lot of speed estimation and get good at it.

Hehe! I know of it too because I'M THAT KID!!! HAHA 10023R!!! send mail go out post dammit! send dammit! TEACHER, CAN YOU HELP ME SEND THIS EMAIL!?