A few years ago I had some health issues and now I can't have caffeine. A year ago I developed a lactose intolerance as well, go me!!!. As a result I have to have decaf and milk alternatives. My wife still laughs every time we are out and I order a "Decaf Soy Latte". Then she calls me an inner city toffee nose wanker (Aussie slang).

Statistically speaking, you are the youngest in your team then.

I just calculated the average age for my team and it turns out we are old. We have an average age of 54 which seems high in the grand scheme of things. We are still holding our own very well though. so I was just wondering if anyone else had an older team and how they are handling grey beardedness.

In my previous role it would have been a 100% yes I would keep working. Now that I've moved into management it now a resounding 100% no. I would be out of here in a heart beat. However, I am still at the same company so I might give them 2 weeks notice to find my replacement. Then I would start a brewery!!!

I absolutely love my coffee (as any good programmer should). But when I had heart problems and diagnosed with 2 separate types of palpitations, large doses of caffeine are a no go anymore. Decaf has been a blessing as I can continue to enjoy a cup of coffee with colleagues but not affect my condition.

I bet they are ageist as well. Probably want someone in their 20's to come work at the company.

Thanks for the advice. For future reference I'm just letting everyone know that I'm awesome :-D

I cant wait for Windows 95 to come around. Based on the current release cycle of every 2 years it should be out in 2184. Give or take depending on how many version numbers they skip.

I might have to start a bacon exporting business. My bacon at the local costs $7.99AUD per kg. Translated for you that is $3.30USD per lb. Got to love living in an agricultural country.

Interesting. As a non US citizen how do I take advantage of this. Preferably without leaving my living room? :)

Rob, I used the Yagarto toolchain with Eclipse IDE. I did have to wipe the flash everytime before doing an upload and because there was no built in JTAG interface is was difficult to debug programs but I did manage to control a Ninco slot car race track with it which couldn't be done using the .NET microframework. There is a good SDK you can download from ATMEL that will help with controlling the GPIO ports. Check out this page to download http://www.atmel.com/devices/SAM7X512.aspx?tab=overview[^]

I programmed a bit on a Netduino as well but came across the same problem. Too slow. I just did away with the .net microframework and ran native on bare metal. It ran sooooo much faster running on bare metal and was still quite usable.

With some coercion I convinced the boss to employee another person to help lighten my load a little bit. We employed a kid straight out of high school with a little bit of knowledge in coding practices. He is learning on the job while studying at Uni. I think there should be more of this because it has really helped me as much as him. My code is cleaner and easier to read so that he will understand it better. Explaining network architecture, what the computer actually does to execute the code he writes, mathematics behind algorithms has helped to reinforce my knowledge. Win-Win I think.

This is the only Top Shelf I use http://stillspirits.com/collections/top-shelf-spirits-1[^] very yummy

I got 100%, while having a catch up with the boss :-D

Kids

Wish the public holiday was the next Monday. Then I could watch the Superbowl live instead of having to record it and watch when I get home. Somehow I always manage to find out the result before I get to watch the game.

I have two solutions for you. First be partially honest. Email them and inform them that you have found a hole in their website that allows free downloads of their material. DO NOT tell them that you have already done this. Tell them you can point this out for them but you want indemnity. Then once they agree point out the flaw and what you did. If that sounds a bit too complex and time consuming my next suggestion is to take the Darwinism approach. Post the vulnerability on some less that reputable sites and let nature take its course. Either they will find the hole themselves and fix it, or lose so much revenue that they will have to shut up shop.

I'm assuming no one cares how hard this was for you or how much overtime/lack of sleep was required to get it implemented. They are also probably wondering why it took you so long.

I like this idea. Very much so.