Para los que recién comienzan a utilizar este tipo de red social, les recomiendo que le peguen una mirada al artículo, para aprender cómo aprovecharla mejor y conocer la aplicación al máximo:
Leer Artículo.
En este blog comento experiencias del ámbito laboral y del educativo. Principalmente temas o situaciones de las cuales aprendí y me gustaría compartir. También recomendare libros, herramientas, software y buenas prácticas.
A chicken and a pig are together when the chicken says, "Let's start a restaurant!".
The pig thinks it over and says, "What would we call this restaurant?".
The chicken says, "Ham n' Eggs!".
The pig says, "No thanks, I'd be committed, but you'd only be involved!".
Institute a rule where only the “committed” participate and the “involved” are only allowed to observe.¿De qué hablamos en la reunión diaria?
A special consideration which may include financial compensation will be awarded to a limited number of authorize licensee to read this section of the license agreement and contact PC Pitstop at consideration@pcpitstop.com . This offer may be withdrawn at any time.Luego de cuatro meses y mas de 3000 descargas del programa, alguien mando el mail y se le pago U$S 1000. Esto prueba que la gente lee las licencias. El objetivo de esa empresa es que la gente lea las licencias, ya que muchos de los programas que traen spyware te dicen eso en la licencia y te dan la opción de cancelar y no instalar el software.
1. Usted sabe que la planificación no es más que un buen deseo que no se cumplirá. ¿Para que perder tiempo planificando entonces?, comience a trabajar de inmediato, y no pierda su tiempo en papeles.
2. Nunca pida definiciones al sponsor o al cliente, lo verán como a un molesto. Si algo no queda como el sponsor o el cliente lo necesitaba siempre hay tiempo para un cambio de alcance, y por otro lado no se lo avisaron.
3. No se moleste en perfeccionar la definición del alcance del proyecto en el inicio del mismo, y mucho menos acordarla por escrito con el cliente. Esto es una pérdida de tiempo y le quita “flexibilidad” a la gestión, además es mucho mas aburrido que ir definiéndolo sobre la marcha.
4. Acepte proyectos con cronogramas incumplibles, y no los re-planifique. De todos modos los proyectos siempre se atrasan, entonces para qué incomodar a sus superiores ya desde el inicio. (Este consejo es tan bueno que también es válido para costos).
5. No establezca responsables en el equipo, luego pretenderán que les reconozcan sus logros. Eso sí, tenga siempre a mano a uno o dos culpables por entregable (este punto es muy importante para asegurarse futuros fracasos).
6. Documente lo menos posible, la documentación lo compromete y hasta puede que quede en evidencia el estado de su proyecto.
7. Cambie a los miembros del equipo una o dos veces por proyecto. Así podrá culpar a los que no están por los problemas que aparecen o a los nuevos por no entender el proyecto. Si se llegase a quedar sin más opciones, es el momento de que usted cambie de proyecto.
8. Si te estás comunicando no estás haciendo cosas, por lo tanto, comunicarse es perder el tiempo. Por otro lado usted no tiene nada que escuchar ni del cliente ni del equipo, si fuesen tan listos ya serían PMs.
9. Otro punto clave: jamás pida capacitación para el equipo, un individuo capacitado es un recurso que genera más valor y apreciado por el mercado, por lo tanto le exigirá un mejor sueldo, o peor aún, se irá a otro proyecto.
10. No pierda tiempo revisando los términos y condiciones de los contratos, y tampoco se moleste en generar una buena relación con abastecimiento. Los proveedores solo quieren sacarle el dinero de su proyecto y abastecimiento solo dificulta las compras.
You also agree that you will not use these products for any purposes prohibited by United States law, including, without limitation, the development, design, manufacture or production of nuclear, missiles, or chemical or biological weapons.
User must keep User's Access Code confidential and must ensure that it is not disclosed to any other person.
¿Descubrieron mi error? Nunca tendría que haberle comentado al cliente que usaba las credenciales de un compañero ya que podría haberle creado problemas a el y a la empresa. En esa situación tendría que haber dicho que mi compañero subía los archivos por mi. Nunca se puede ser demasiado cuidadoso.
Proprietary software developers have the advantage of money; free software developers need to make advantages for each other. Using the ordinary GPL for a library gives free software developers an advantage over proprietary developers: a library that they can use, while proprietary developers cannot use it.
Using the ordinary GPL is not advantageous for every library. There are reasons that can make it better to use the Lesser GPL in certain cases. The most common case is when a free library's features are readily available for proprietary software through other alternative libraries. In that case, the library cannot give free software any particular advantage, so it is better to use the Lesser GPL for that library.
However, when a library provides a significant unique capability, like GNU Readline, that's a horse of a different color. The Readline library implements input editing and history for interactive programs, and that's a facility not generally available elsewhere. Releasing it under the GPL and limiting its use to free programs gives our community a real boost. At least one application program is free software today specifically because that was necessary for using Readline.
Proprietary software developers, seeking to deny the free competition an important advantage, will try to convince authors not to contribute libraries to the GPL-covered collection. For example, they may appeal to the ego, promising “more users for this library” if we let them use the code in proprietary software products. Popularity is tempting, and it is easy for a library developer to rationalize the idea that boosting the popularity of that one library is what the community needs above all.
But we should not listen to these temptations, because we can achieve much more if we stand together. We free software developers should support one another. By releasing libraries that are limited to free software only, we can help each other's free software packages outdo the proprietary alternatives. The whole free software movement will have more popularity, because free software as a whole will stack up better against the competition.
Nearly all open source software is free software; the two terms describe almost the same category of software. But they stand for views based on fundamentally different values. Open source is a development methodology; free software is a social movement. For the free software movement, free software is an ethical imperative, because only free software respects the users' freedom. By contrast, the philosophy of open source considers issues in terms of how to make software “better”—in a practical sense only. It says that non-free software is a suboptimal solution. For the free software movement, however, non-free software is a social problem, and moving to free software is the solution.
Free software. Open source. If it's the same software, does it matter which name you use? Yes, because different words convey different ideas. While a free program by any other name would give you the same freedom today, establishing freedom in a lasting way depends above all on teaching people to value freedom. If you want to help do this, it is essential to speak about “free software.”
We in the free software movement don't think of the open source camp as an enemy; the enemy is proprietary (non-free) software. But we want people to know we stand for freedom, so we do not accept being misidentified as open source supporters.
Copyleft is a general method for making a program or other work free, and requiring all modified and extended versions of the program to be free as well.
The simplest way to make a program free software is to put it in the public domain, uncopyrighted. This allows people to share the program and their improvements, if they are so minded. But it also allows uncooperative people to convert the program into propietary software. They can make changes, many or few, and distribute the result as a proprietary product. People who receive the program in that modified form do not have the freedom that the original author gave them; the middleman has stripped it away.
Copyleft says that anyone who redistributes the software, with or without changes, must pass along the freedom to further copy and change it. Copyleft guarantees that every user has freedom.Proprietary software developers use copyright to take away the users' freedom; we use copyright to guarantee their freedom. That's why we reverse the name, changing “copyright” into “copyleft.”
Copyleft is a way of using of the copyright on the program. It doesn't mean abandoning the copyright; in fact, doing so would make copyleft impossible. The word “left” in “copyleft” is not a reference to the verb “to leave” — only to the direction which is the inverse of “right”.
Many people believe that the spirit of the GNU project is that you should not charge money for distributing copies of software, or that you should charge as little as possible — just enough to cover the cost.
Actually we encourage people who redistribute free software to charge as much as they wish or can. If this seems surprising to you, please read on.
The word “free” has two legitimate general meanings; it can refer either to freedom or to price. When we speak of “free software”, we're talking about freedom, not price. (Think of “free speech”, not “free beer”.) Specifically, it means that a user is free to run the program, change the program, and redistribute the program with or without changes.
Free programs are sometimes distributed gratis, and sometimes for a substantial price. Often the same program is available in both ways from different places. The program is free regardless of the price, because users have freedom in using it.
Free software is a matter of the users' freedom to run, copy, distribute, study, change and improve the software. More precisely, it refers to four kinds of freedom, for the users of the software:
- The freedom to run the program, for any purpose (freedom 0).
- The freedom to study how the program works, and adapt it to your needs (freedom 1). Access to the source code is a precondition for this.
- The freedom to redistribute copies so you can help your neighbor (freedom 2).
- The freedom to improve the program, and release your improvements to the public, so that the whole community benefits (freedom 3). Access to the source code is a precondition for this.
La pagina Answers.com, (la cual comente en un post anterior) tiene un servicio que se llama “Word of the day” que te envía por RSS o por mail la palabra del día, con el significado, ejemplos de utilización, la pronunciación, sinónimos y todo lo que provee Answers.com
Es una buena forma para mejorar el inglés día a día y lleva solo 1 minuto!
Triage is a process of prioritizing patients based on the severity of their condition so as to treat as many as possible when resources are insufficient for all to be treated immediately.En la ingeniería del software el termino tiene el siguiente significado:
Triage is now also applied in system development. Requirements and design options are triagedto avoid wasting effort on ideas that will obviously never succeed. At some point in the software development lifecycle, regardless of which model you use, we have to make some tough decisions. What defects do we fix? Which should we let go? How do we decide? Triage is one way!Descubrí este termino hace poco en la lista de hitos de la pagina oficial de Trac. Resulta que tienen un hito en el cual asignan todas las tareas o defectos (de ahora en mas tickets) que no están planeadas, o no se sabe todavía para que hito deben ser hechas, o si vale la pena completarlas o deben ser canceladas. Ellos documentaron el proceso para aplicar 'triage' sobre los tickets.
Quality control activities are focused on the deliverable itself. Quality assurance activities are focused on the process used to create the deliverable. They are both powerful techniques and both must be performed to ensure that the deliverables meet your customers quality requirements.
Good writing requires focus.Estas son diez pautas que sugiere el escritor:
1. Do your research first.Les recomiendo que lean el articulo completo acá.
2. Turn off the Internet.
3. Use Writeroom (program for writing text, and nothing else. They block out the rest of your computer with a black background).
4. Shut down everything else.
5. Turn off the TV.
6. Clear your desk.
7. Shut off all phones and notifications.
8. Let people know you’re in DND mode.
9. Just write.
10. Take breaks.