Règles pour l'accessibilité des contenus Web (WCAG) 2.0. Cette publication a été en partie financée par des fonds du gouvernement fédéral des États-Unis du ministère de l'éducation, de l'Institut National pour la recherche sur le handicap et la réadaptation (Institute on Disability and Rehabilitation Research (NIDRR)) sous le numéro de référence ED05CO0039.
Le contenu de cette publication ne reflète pas nécessairement les avis ou politiques du ministère américain de l'éducation, la mention de noms de marques, de produits commerciaux ou d'organismes ne signifie pas non plus qu'ils ont été approuvés par le gouvernement des États-Unis. Des informations supplémentaires à propos de la participation au groupe de travail des règles pour l'accessibilité des contenus Web (WCAG WG) sont consultables sur la page d'accueil du groupe de travail (en anglais). Anciens participants dans le groupe de travail des WCAG et autres contributeurs. The SNOW Home Page. Whitespace steganography The program SNOW is used to conceal messages in ASCII text by appending whitespace to the end of lines.
Because spaces and tabs are generally not visible in text viewers, the message is effectively hidden from casual observers. And if the built-in encryption is used, the message cannot be read even if it is detected. What's in a name? SNOW exploits the Steganographic Nature Of Whitespace. It's free! As of 16 June 2013, SNOW is available under an Apache 2.0 licece. Recent changes Prior to 22 November 1998 the DOS version, contained in snowdos.zip, had a bug affecting encryption. The source version, when compiled under Unix, also had a bug where it could not read data concealed by the DOS version, owing to the carriage return character appended by DOS. Mostly random thoughts » How to secure your USB thumbdrive.
10 Papers Every Programmer Should Read (At Least Twice) I spent most of yesterday afternoon working on a paper I’m co-writing. It was one of those days when the writing came easy. I was moving from topic to topic, but then I realized that I was reaching too far backward – I was explaining things which I shouldn’t have had to explain to the audience I was trying to reach. When I first started writing, one of the pieces of advice that I heard was that you should always imagine that you are writing to a particular person. It gets your juices going – you’re automatically in an explanatory state of mind and you know what you can expect from your audience. I was doing that, but I noticed that I was drifting. The problem I was experiencing is only getting worse. So, I was thinking about this and trying to not to get too glum. We’ve taken an interesting turn in the industry over the past ten years. Here’s the original list.
Most are easy to read but some are rough going – they drop off into math after the first few pages. Managing Software Development: Top 100 Best Software ... How to Write a Killer Resume, for Software Engineers. By Niniane Wang, May 2005 Update March 2013: My company Minted is hiring software engineers!
We are a consumer web startup in San Francisco, and welcome you to apply. Please see the job description and then email your resume to me! In the past few years working as a software engineer for Google (and previously a dev lead at Microsoft), I've screened hundreds of resumes, to make the decision on whether to proceed with the interview process. Some resumes gave off a great impression, and others didn't. Increasingly, friends and relatives ask me for suggestions on improving their resumes, so I've created a a list of the most common pitfalls I've seen, and how to avoid them: 1. . * Worked with a team of 3 on an e-mail plugin. The screener is reading your resume with the mindset of judging 1. how challenging this work was, 2. how relevant it is to their own company, so you need to be specific. . * Implemented in C++ an Outlook e-mail plugin which performs automatic backups. 2. 3.
Java.