iGoogle. The Joel Test: 12 Steps to Better Code. By Joel Spolsky Wednesday, August 09, 2000 Have you ever heard of SEMA? It's a fairly esoteric system for measuring how good a software team is. No, wait! Don't follow that link! It will take you about six years just to understand that stuff. The neat thing about The Joel Test is that it's easy to get a quick yes or no to each question. A score of 12 is perfect, 11 is tolerable, but 10 or lower and you've got serious problems.
Of course, these are not the only factors that determine success or failure: in particular, if you have a great software team working on a product that nobody wants, well, people aren't going to want it. 1. 2. If the process takes any more than one step, it is prone to errors. For this very reason, the last company I worked at switched from WISE to InstallShield: we required that the installation process be able to run, from a script, automatically, overnight, using the NT scheduler, and WISE couldn't run from the scheduler overnight, so we threw it out. 3. 4. 5. Cross Platform GUI Programming. JIRA- Track bugs, tasks, and projects for software development. Cómo transformar XML sin usar XSLT | Diario de un Dotnetero. Seguridad web 101. O uno de los problemas de contratar programadores baratos que no estén a distancia de coscorrón. Antes que nada, si no sos una persona técnica leyendo esto te voy a dar una recomendación: un técnico/vendedor que te dice que el producto que te esta ofreciendo es inviolable te esta mintiendo.
El único sistema seguro es una PC apagada, sin conexiones externas, encerrada en una caja fuerte y arrojada a las profundidades del océano. No importa que servicios contrates, uses un sistema operativo de renombre o una base de datos carisima SIEMPRE quedan errores y agujeros.El testeo y las auditorias solamente comprueban que existen errores, no la falta de ellos. Una vez dicho esto, la seguridad no es una compra de una vez sino que es un proceso constante de mejora e investigación. Hace un par de años que en lo personal me aleje de la programación para escritorio y me dedique de lleno a la web. Ahora que aclare todo lo que quería, un par de cosas que aprendí a los golpes y leyendo:
Tabla arco iris. Las tablas Rainbow son tablas de consulta que ofrecen un compromiso entre tiempo y espacio para obtener claves en texto simple a partir del resultado de una función de hash. Hash[editar] Hash es una función que se aplica a un archivo de cualquier tipo, ya sea documentos, fotos, música,... y de la cual se obtiene una clave que representa de manera única a ese archivo. Este método se utiliza mucho en las descargas de Internet para comprobar la integridad del archivo, es decir, poder comprobar si en la descarga del fichero ha habido algún tipo de error. Para ello se comprueba a ver si el hash obtenido del fichero es igual tanto al principio de la descarga (normalmente los autores de los archivos suelen indicarlo) como al final.
Las funciones Hash más importantes son: Funcionamiento[editar] A continuación se explica mediante un ejemplo el funcionamiento de las Tablas Rainbow. Aplicaciones[editar] Salts[editar] Enlaces externos[editar] Ophcrack programa para poder utilizar las Tablas Rainbow. MongoDB. Best keygen sound. YamlDotNet. YamlDotNet is a .NET library for YAML. YamlDotNet provides low level parsing and emitting of YAML as well as a high level object model similar to XmlDocument.
A serialization library is also included that allows to read and write objects from and to YAML streams. What is YAML? YAML, which stands for "YAML Ain't Markup Language", is described as "a human friendly data serialization standard for all programming languages". Like XML, it allows to represent about any kind of data in a portable, platform-independent format. The YamlDotNet library The library has now been successfully used in multiple projects and is considered fairly stable. Where to get it? The most up-to-date version can always be found in the following NuGet packages: You can also clone the project on GitHub if you are interested. More information. YARP: Getting Started with YARP Ports. A network of ports Communication in YARP generally follows the Observer design pattern. Special port objects deliver messages to any number of observers (other ports), in any number of processes, distributed across any number of machines, using any of several underlying communication protocols.
Here is a very simple network of ports for a visual tracking application: Images are transmitted from a camera ("/camera") port to a viewer ("/viewer1") port and the input of a visual tracker ("/tracker/image"). The tracker annotates the image, for example by placing a marker on a tracked point, and transmits that to another viewer ("/viewer2"). The tracker also sends just the tracked position from a position output port ("/tracker/position") to a input controlling head position ("/motor/position").
Processes can be on different physical machines without a problem. A worked example [on terminal 1] yarp server [on terminal 2] yarp read /read [on terminal 3] yarp write /write /read [on terminal 4] . What is love 8 bit. Ranking of HCI conferences based on average citations per paper - Human-Computer Interaction by Antti Oulasvirta.