Consejos de diseño para tablas de información.
http://designshack.co.uk/articles/css/15-tips-for-designing-terrific-tables
Descubrimientos de una inteligencia artificial que supera el test de Turing
On the Internet, everybody knows you're a chatbot.
"My goal was to prepare them for that project by communicating two key things:
1. Make things for people.
2. Those people aren’t you.
Before the class, Ben warned me about the attention span of his students, and boy was he right. The thing about high school kids is they won’t pretend to be interested if you’ve lost them. Adults at a conference will gaze forward in your general direction, but high school kids will just put their head on the table and go to sleep. If you ever want to get a real gauge of how interesting a speaker you are (or how well you’re really communicating), I highly recommend it, humbling as it is. "
"Features are good. They set Firefox apart from others, and attract users. What bothers users is features that don’t have a mature user interface. The solution should be to fix the interface, not drop the feature."
“Implicit human-computer interaction is an action, performed by the user that is not primarily aimed to interact with a computerized system but which such a system understands as input.” [5]. This is opposed to explicit HCI, where “the user tells the computer at a certain level of abstraction (e.g., by command-line, direct manipulation using a GUI, gesture, or speech input) what she expects the computer to do.” [5]. An example of explicit HCI is using a direct-manipulation graphical user interface (GUI) to drag a file from one folder to another, in order to have the file become located in the target folder. Implicit HCI, on the other hand, requires computers to observe and interpret what the user is doing, via sensors, which may be implemented as physical sensors (e.g., GPS) or digital sensors (e.g., file usage monitor)."
http://blog.mozilla.com/faaborg/2010/04/22/dont-talk-about-users/
How can we convert current developers in open source projects to have a skill set equivalent to what academia or a corporation would consider to be formally trained user experience professional? The approach we propose consists of embedding HCI concepts and practices directly into the tools that control an open source community’s work flow.
"La revisión bibliografía permite que centremos nuestra investigación mediante la consideración de trabajos anteriores. Para ello, lo primero que debemos hacer es identificar los términos o “keywords” que van a guiar nuestra investigación, estas palabras clave son las que nos permitan localizar los trabajos previos.
Es importante identificar los trabajos previos publicados para poder focalizar, definir, contrastar o aprovechar la información obtenida, y por que así ayudas a que crezca el cuerpo teórico del HCI."
Part of the Novel Input & Output Project
A menu system often serves as the core interaction workhorse of an application. We have researched and productized a few solutions that enhance the user’s experience. Most notably is the marking-menu which allows a user to perform a menu selection by either popping-up a radial menu or by quickly making a straight mark in the direction of the desired menu without popping-up the menu. Other investigations have focused on providing efficient access to a large number of menu-items (the HotBox), menus for pen computers (tracking menus), for rapid tool switching (pieCursor) and multitouch environments (multitouch marking menus).
"Nunka asetaremo ke potensia etranjera token kabeyo de letra eñe.
Eñe rrepresenta balore ma elebado de tradision ispanika y primero kaeremo mueto ante ke asetar bejasione a simbolo ke a sio korason bibifikante de istoria kastisa epañola unibersa."

Event-driven programming is widely used in [[graphical user interfaces] because it has been adopted by most commercial widget toolkits as the model for interaction. The design of those toolkits has been criticized for promoting an over-simplified model of event-action, leading programmers to create error prone, difficult to extend and excessively complex application code:
Such an approach is fertile ground for bugs for at least three reasons:
1. It always leads to convoluted conditional logic.
2. Each branching point requires evaluation of a complex expression.
3. Switching between different modes requires modifying many variables, which all can easily lead to inconsistencies.
Instead of a low level action-reaction, Miro Samek proposes a better approach using finite State Machines to control the interaction logic necessary to define the state changes to incoming events. Hierarchical State Machines have also been proposed as a high-level model for reactive programs. The UML language in particular provides a complete specification to represent state machines.
Some alternate implementations:
http://accu.org/index.php/journals/252
http://www.eventhelix.com/RealtimeMantra/HierarchicalStateMachine.htm