i've mostly gotten interviews because i've been to a fairly well known uni, got a masters qualificaiton and i've worked in top name companies.. that said, there's other ways in -- if a company cant get the people with the 'normal' qualifications then you can get an interview if you can convince someone in the dept you can do the job.. how to convince ? depends what job you want. build up a portfolio of relevant certifications and experience in that area.. so a degree is ideal, if that's not viable, certifications, open source, maintain a network for a local charity organisation, whatever is relevant is good.. people dont want to hire potential, they want to hire someone who has gotten results close to where their current problem or pain is. So you need to talk the talk and have a number of concrete elements that demonstrate you've done it rather than thought about it

it's cool that I no longer need to drag cables across a room just to use a projector, but it would be even nicer if i could play back any media on my pc and have the images and sound on my tv.. does anyone know if this includes the sound? i owuld expect not as I dont see how it could capture and correclty sync the sound without being part of media framework and that would necessitate a particular playback applicatio. it seems from the article this is application independent. shame as that youtube video and sound redirected from pc to tv would have been cool

if you want to become strong, as a start out developer you need to be an environment where you learn from your peers. If you are motivated to learn and produce things it will be difficult if your peers are unproductive and management weak. The risk is that your peers are happy with the status quo and that management are not motivated to improve the engineering dept. You may find yourself getting frustrated as you grow, but your colleagues stay the same. There are some great companies out there who care about engineering, the trick is to identify them when interviewing. Asking questions such as 'how do you guys measure engineering quality' or 'what software lifecycle is predominant' are inoffensive, but tell you important things about how the engineering department operates I've 10 years experience as an engineer now. In your position, I would ask myself question 'what can i learn from my colleagues' and if after 6 or 9 months in a company, the answer is not good then you may have made a mistake joining that company. While job hopping is not good, it may be the best thing to do. Just be careful not to repeat the mnistake,I know some companies that will not hire someone with a history of changing job more frequently than once every two years.

I think its pretty innovative, and contributes something positive. A lot of the comments are on the lines of pgp / whatever respected cryptographic tool will do a decent job on signing / encypting / decrypting - we can all agree on this However where we need to evaluate systems is on how easy it is to sign a message, get a key pair, to get the certificate of your correspondent, renew their certificate etc The email proxy server architecture seems a really neat way to handle the cryptographic functions and the client side of certificate management - the central certificate repository seems a good way to distribute certs and handle cert status I dont think there's anything about the system that is fundamentally insecure but I would be interested in the trust relationship between the email client and proxy server is implemented. Also will the centralised repository scale if the system becomes popular? Imagine how many certificate issuing & status requests that thing would need to cope with if it got popular