Ecosistema Digital y la experiencia usuarioMiguel Gea
Este documento presenta una sesión sobre el ecosistema digital y la experiencia del usuario. Se introducen conceptos clave como la experiencia del usuario, la arquitectura de la información y el diseño centrado en el usuario para plataformas móviles y sociales. También se discuten temas como la evolución de Internet, la Web 2.0, el consumo de tecnología y las redes sociales. Finalmente, se mencionan conceptos como la identidad digital y la construcción de la identidad en entornos digitales.
El documento habla sobre la informática y los sistemas de información. Explica que la informática involucra el tratamiento automático de la información por medio de computadoras usando conocimientos científicos y técnicas. También describe la utilidad de las computadoras, los programas computacionales, el hardware y software, y la jerarquía de computadoras que componen los sistemas de información.
The document provides rules for forming the past simple tense of regular verbs in English. It states that for most regular verbs ending in a consonant, we add "-ed" to form the past tense. For verbs ending in "e", we add "d". For verbs ending in a consonant + "y", we change the "y" to "ied". And for one-syllable verbs ending in a consonant-vowel-consonant, we double the final consonant before adding "-ed". Examples are given for each rule to illustrate how to form the past tense of different types of regular verbs.
El transporte fluvial viene a constituir la navegación que realizan embarcaciones a través de los ríos navegables movilizando carga y/o pasajeros entre dos o más puertos ubicados en las riberas de estos ríos y uniendo puntos geográficos diferentes en el ámbito nacional e internacional
O documento descreve uma propaganda da cerveja Kaiser que retrata mulheres de forma estereotipada e objetificada. A propaganda é criticada por representar as mulheres apenas por seus atributos físicos e reduzi-las a objetos colecionáveis pelos homens. Uma reformulação da campanha é sugerida para enfatizar a diversidade e individualidade femininas.
Guatemala offers many beautiful touristic places, including:
1) Antigua Guatemala, a famous tourist destination known for its architecture like the Arch of Santa Catalina and churches.
2) Tikal, the largest excavated Mayan site featuring fascinating archaeological remains of the ancient Mayan civilization.
3) Semuc Champey, a natural enclave in the jungle containing a 300-meter limestone bridge and turquoise pools.
4) Lake Atitlán, surrounded by volcanoes and offering amazing scenery, it is one of Guatemala's most visited attractions.
Ecosistema Digital y la experiencia usuarioMiguel Gea
Este documento presenta una sesión sobre el ecosistema digital y la experiencia del usuario. Se introducen conceptos clave como la experiencia del usuario, la arquitectura de la información y el diseño centrado en el usuario para plataformas móviles y sociales. También se discuten temas como la evolución de Internet, la Web 2.0, el consumo de tecnología y las redes sociales. Finalmente, se mencionan conceptos como la identidad digital y la construcción de la identidad en entornos digitales.
El documento habla sobre la informática y los sistemas de información. Explica que la informática involucra el tratamiento automático de la información por medio de computadoras usando conocimientos científicos y técnicas. También describe la utilidad de las computadoras, los programas computacionales, el hardware y software, y la jerarquía de computadoras que componen los sistemas de información.
The document provides rules for forming the past simple tense of regular verbs in English. It states that for most regular verbs ending in a consonant, we add "-ed" to form the past tense. For verbs ending in "e", we add "d". For verbs ending in a consonant + "y", we change the "y" to "ied". And for one-syllable verbs ending in a consonant-vowel-consonant, we double the final consonant before adding "-ed". Examples are given for each rule to illustrate how to form the past tense of different types of regular verbs.
El transporte fluvial viene a constituir la navegación que realizan embarcaciones a través de los ríos navegables movilizando carga y/o pasajeros entre dos o más puertos ubicados en las riberas de estos ríos y uniendo puntos geográficos diferentes en el ámbito nacional e internacional
O documento descreve uma propaganda da cerveja Kaiser que retrata mulheres de forma estereotipada e objetificada. A propaganda é criticada por representar as mulheres apenas por seus atributos físicos e reduzi-las a objetos colecionáveis pelos homens. Uma reformulação da campanha é sugerida para enfatizar a diversidade e individualidade femininas.
Guatemala offers many beautiful touristic places, including:
1) Antigua Guatemala, a famous tourist destination known for its architecture like the Arch of Santa Catalina and churches.
2) Tikal, the largest excavated Mayan site featuring fascinating archaeological remains of the ancient Mayan civilization.
3) Semuc Champey, a natural enclave in the jungle containing a 300-meter limestone bridge and turquoise pools.
4) Lake Atitlán, surrounded by volcanoes and offering amazing scenery, it is one of Guatemala's most visited attractions.
Actividad de Teatro La Gallinita de Tamara Chubarovsky, para el aula 2-3 aunque se puede también se adapta al aula 1-2 y aula de bebés, las rimas con dedos son aconsejables desde edades tempranas, Aportan tranquilidad y calma a los niños y niñas. La Creación de los títeres debe realizarse por parte de las educadoras. En cursos de primaria los niños pueden elaborarlos.
Comunicado oficial de la Federación Española de Fútbol Americano (FEFA) con información de los partidos amistosos que disputarán en este año 2017 los equipos nacionales senior masculino y femenino.
Entrega de Premios 10º Concurso de Dibujo Burgos Con Bici (2017)Burgosconbici
Acto de entrega de premios del 10º Concurso de dibujo escolar "Por una ciudad sostenible. Con bici al cole". Organizado por la asociación Burgos Con Bici. 30 de marzo de 2017
Este documento explica las coordenadas geográficas y cómo se usan para localizar un punto en un mapa. Describe que hay dos tipos de líneas: los paralelos que miden la latitud de 0° a 90° norte o sur, y los meridianos que miden la longitud de 0° a 180° este u oeste desde el meridiano de Greenwich. Define la latitud como la distancia angular desde el ecuador y la longitud como la distancia angular desde el meridiano de Greenwich.
Editing and Proofreading: Identify errorsSusan Bolling
This document provides examples of common grammatical and stylistic errors in writing, along with corrections. It covers issues like sentence structure, subject-verb agreement, consistent verb tense, article usage, spelling, punctuation, and more. The examples showcase errors in areas such as fragments, passive voice, pronoun agreement, prepositions, capitalization, pluralization, and possessives. The goal is to help writers identify and avoid frequent mistakes to improve the clarity and correctness of their writing.
The document discusses whether distributed teams can deliver high quality code. It argues that quality can only be achieved through control and enforcement, with programmers being forced to write high-quality code. Quality is defined as maintainability. Some ways to achieve quality include making the master branch read-only, having a fragile build process, and requiring unbiased code reviews. However, co-located teams can be against quality due to chats, social biases, friendship, and monthly salaries interfering. But distributed teams can produce higher quality if managed properly by avoiding those distractions.
This document appears to be a series of prompts assessing how much of a micromanager someone is through their responses. It provides multiple choice answers to hypothetical situations a manager might face regarding underperforming employees, missed deadlines, attending meetings, and prioritizing tasks. The person is told they will be given a score to determine if they are a micromanager based on their selected responses. It concludes by providing an email address to contact for more details.
On Requirements Management (Demotivate Them Right)Yegor Bugayenko
This document contains a discussion between two users, yegor256 and yb191209, about software requirements. It includes requirements such as each requirement must be necessary, unambiguous, etc. per IEEE standards. It also lists specific requirements for an application such as supporting multiple API versions, encrypting credit card numbers, generating PDF reports, and using UUIDs for account numbers. The users discuss options for meeting requirements around performance, the user interface, and data formats.
The document discusses Yegor Bugayenko's experience interviewing thousands of candidates over 288 months. It outlines seven sins of an interviewing manager: arrogance, credulity, self-obsession, vagueness, hostility, emotions, and mystery. Each sin is defined in Russian and examples are given of how they negatively impact interviews. Certification costs and sample interview questions are also listed.
This document appears to be a series of scenarios that test for micromanagement tendencies. It presents multiple choice questions about how to handle various situations with direct reports, such as an employee wanting to work from home, missing deadlines, working on another team's project, and a complaint about salary. The respondent is given an assessment of their score and whether it indicates micromanagement based on their selections. The overall document seems to provide a self-assessment test for micromanagers.
This document discusses the differences between quality assurance (QA) and software testing. It notes that QA is the process of auditing quality requirements and results from quality control measurements to ensure standards are met, while quality control is the process of monitoring and recording results from quality activities to assess performance and recommend changes. Several tools used for QA like affinity diagrams and prioritization matrices are presented. The document argues that software testers have a broader role than just testing and outlines responsibilities like requirements analysis, coding, documentation, and metrics collection that testers take on. It questions why testers are often called QA instead of testers and how testers can improve through activities like code reviewing and measuring results.
The document discusses whether Java is improving. It covers various Java language features such as static, final, extends, default, interface usage, var, String methods like repeat() and strip(), switch expressions, and namespaces. The document also mentions NULL returning by default, getters and setters, and contact information for the author.
Yegor Bugayenko gave a presentation titled "Software Testing Pitfalls" at JPoint 2019 in Moscow, Russia. The presentation discussed 4 common misconceptions about software testing: 1) testers are not second-class citizens, 2) testers don't tell developers when to release software, 3) testing is not finished when enough bugs are found, and 4) testers should not be rewarded solely for the number of bugs found, but rather for getting bugs fixed.
Yegor Bugayenko outlines five trends in software development that people are afraid of: 1) No hackers as the industry becomes more accessible and salaries increase, 2) Slow and expensive hardware becomes a thing of the past as technology advances, 3) No proprietary code as more developers share and contribute to open source projects, 4) No middlemen as developers can work directly with customers, and 5) No servers as cloud computing becomes the norm.
Yegor Bugayenko gave a presentation on experts vs expertise at GeeCON in Prague. He argued that while expertise is needed, organizations should not depend on individual experts. Instead, knowledge should be distributed and tasks broken down into smaller pieces with no code ownership to prevent silos of knowledge. This extreme approach called Zerocracy aims to maintain predictability and prevent job security from clinging to power by distributing knowledge. The presentation outlined eight principles of Zerocracy including smaller tasks, no meetings or chats, paying for results not time, and making artifacts not programmers the target of blame.
This document summarizes a talk given by Yegor Bugayenko at AppsConf 2018 in Moscow, Russia about quality in software development. It discusses how quality is often compromised through technical debt, which leads to frustration among teams and increased employee turnover. It promotes establishing quality gates at each stage of development through practices like static analysis, code reviews, test coverage and read-only master branches to reject changes that do not meet quality standards. This helps prevent issues like neglect and sabotage from decreased morale. It concludes by recommending following Yegor on Twitter, buying his book, and joining the Zerocracy platform for quality-focused development.
This document appears to be a transcript from a presentation by Yegor Bugayenko given at DevOpsConf 2018 in Moscow, Russia. The presentation discusses focusing on quality over quantity in software projects and implementing fear-driven development practices like rigorous testing and code reviews to motivate high-quality work. It also promotes the concepts of making small, isolated changes and experimentation to improve quality.
Yegor Bugayenko gave a presentation at DevOpsDays Boston about experts vs expertise. He discussed trends like the growing variety of DevOps tools, increasing data volume, and higher employee turnover rates. This leads to problems like job insecurity and silos of knowledge within organizations. Bugayenko proposes the solution of Zerocracy, which involves extreme practices like #NoMagic where technology dependencies are eliminated, #NoMeetings where work is demonstrated through artifacts not discussions, and #NoSalaries where compensation is based on results not time spent. The goal is to focus on expertise over experts by making knowledge accessible organization-wide.
This document discusses Zold, a proposed cryptocurrency that does not use blockchain technology. It aims to be faster, more lightweight, and more efficient than blockchains like Bitcoin. Zold uses a novel approach called "dynamic proof-of-work" to achieve consensus without mining. This allows it to process over 1 million transactions per second using lightweight nodes while consuming far less energy than blockchains. The founder seeks feedback on this new approach to distributed trust.
The document discusses centralized payment systems, decentralized payment systems (cryptocurrencies), and the evolution of trust from duplication to encryption to consensus. It addresses topics like the energy consumption and costs of proof-of-work blockchains, as well as alternatives like proof-of-stake and discusses tradeoffs between cost, speed and size for different consensus mechanisms. It concludes by asking the reader's thoughts on these topics.
Actividad de Teatro La Gallinita de Tamara Chubarovsky, para el aula 2-3 aunque se puede también se adapta al aula 1-2 y aula de bebés, las rimas con dedos son aconsejables desde edades tempranas, Aportan tranquilidad y calma a los niños y niñas. La Creación de los títeres debe realizarse por parte de las educadoras. En cursos de primaria los niños pueden elaborarlos.
Comunicado oficial de la Federación Española de Fútbol Americano (FEFA) con información de los partidos amistosos que disputarán en este año 2017 los equipos nacionales senior masculino y femenino.
Entrega de Premios 10º Concurso de Dibujo Burgos Con Bici (2017)Burgosconbici
Acto de entrega de premios del 10º Concurso de dibujo escolar "Por una ciudad sostenible. Con bici al cole". Organizado por la asociación Burgos Con Bici. 30 de marzo de 2017
Este documento explica las coordenadas geográficas y cómo se usan para localizar un punto en un mapa. Describe que hay dos tipos de líneas: los paralelos que miden la latitud de 0° a 90° norte o sur, y los meridianos que miden la longitud de 0° a 180° este u oeste desde el meridiano de Greenwich. Define la latitud como la distancia angular desde el ecuador y la longitud como la distancia angular desde el meridiano de Greenwich.
Editing and Proofreading: Identify errorsSusan Bolling
This document provides examples of common grammatical and stylistic errors in writing, along with corrections. It covers issues like sentence structure, subject-verb agreement, consistent verb tense, article usage, spelling, punctuation, and more. The examples showcase errors in areas such as fragments, passive voice, pronoun agreement, prepositions, capitalization, pluralization, and possessives. The goal is to help writers identify and avoid frequent mistakes to improve the clarity and correctness of their writing.
The document discusses whether distributed teams can deliver high quality code. It argues that quality can only be achieved through control and enforcement, with programmers being forced to write high-quality code. Quality is defined as maintainability. Some ways to achieve quality include making the master branch read-only, having a fragile build process, and requiring unbiased code reviews. However, co-located teams can be against quality due to chats, social biases, friendship, and monthly salaries interfering. But distributed teams can produce higher quality if managed properly by avoiding those distractions.
This document appears to be a series of prompts assessing how much of a micromanager someone is through their responses. It provides multiple choice answers to hypothetical situations a manager might face regarding underperforming employees, missed deadlines, attending meetings, and prioritizing tasks. The person is told they will be given a score to determine if they are a micromanager based on their selected responses. It concludes by providing an email address to contact for more details.
On Requirements Management (Demotivate Them Right)Yegor Bugayenko
This document contains a discussion between two users, yegor256 and yb191209, about software requirements. It includes requirements such as each requirement must be necessary, unambiguous, etc. per IEEE standards. It also lists specific requirements for an application such as supporting multiple API versions, encrypting credit card numbers, generating PDF reports, and using UUIDs for account numbers. The users discuss options for meeting requirements around performance, the user interface, and data formats.
The document discusses Yegor Bugayenko's experience interviewing thousands of candidates over 288 months. It outlines seven sins of an interviewing manager: arrogance, credulity, self-obsession, vagueness, hostility, emotions, and mystery. Each sin is defined in Russian and examples are given of how they negatively impact interviews. Certification costs and sample interview questions are also listed.
This document appears to be a series of scenarios that test for micromanagement tendencies. It presents multiple choice questions about how to handle various situations with direct reports, such as an employee wanting to work from home, missing deadlines, working on another team's project, and a complaint about salary. The respondent is given an assessment of their score and whether it indicates micromanagement based on their selections. The overall document seems to provide a self-assessment test for micromanagers.
This document discusses the differences between quality assurance (QA) and software testing. It notes that QA is the process of auditing quality requirements and results from quality control measurements to ensure standards are met, while quality control is the process of monitoring and recording results from quality activities to assess performance and recommend changes. Several tools used for QA like affinity diagrams and prioritization matrices are presented. The document argues that software testers have a broader role than just testing and outlines responsibilities like requirements analysis, coding, documentation, and metrics collection that testers take on. It questions why testers are often called QA instead of testers and how testers can improve through activities like code reviewing and measuring results.
The document discusses whether Java is improving. It covers various Java language features such as static, final, extends, default, interface usage, var, String methods like repeat() and strip(), switch expressions, and namespaces. The document also mentions NULL returning by default, getters and setters, and contact information for the author.
Yegor Bugayenko gave a presentation titled "Software Testing Pitfalls" at JPoint 2019 in Moscow, Russia. The presentation discussed 4 common misconceptions about software testing: 1) testers are not second-class citizens, 2) testers don't tell developers when to release software, 3) testing is not finished when enough bugs are found, and 4) testers should not be rewarded solely for the number of bugs found, but rather for getting bugs fixed.
Yegor Bugayenko outlines five trends in software development that people are afraid of: 1) No hackers as the industry becomes more accessible and salaries increase, 2) Slow and expensive hardware becomes a thing of the past as technology advances, 3) No proprietary code as more developers share and contribute to open source projects, 4) No middlemen as developers can work directly with customers, and 5) No servers as cloud computing becomes the norm.
Yegor Bugayenko gave a presentation on experts vs expertise at GeeCON in Prague. He argued that while expertise is needed, organizations should not depend on individual experts. Instead, knowledge should be distributed and tasks broken down into smaller pieces with no code ownership to prevent silos of knowledge. This extreme approach called Zerocracy aims to maintain predictability and prevent job security from clinging to power by distributing knowledge. The presentation outlined eight principles of Zerocracy including smaller tasks, no meetings or chats, paying for results not time, and making artifacts not programmers the target of blame.
This document summarizes a talk given by Yegor Bugayenko at AppsConf 2018 in Moscow, Russia about quality in software development. It discusses how quality is often compromised through technical debt, which leads to frustration among teams and increased employee turnover. It promotes establishing quality gates at each stage of development through practices like static analysis, code reviews, test coverage and read-only master branches to reject changes that do not meet quality standards. This helps prevent issues like neglect and sabotage from decreased morale. It concludes by recommending following Yegor on Twitter, buying his book, and joining the Zerocracy platform for quality-focused development.
This document appears to be a transcript from a presentation by Yegor Bugayenko given at DevOpsConf 2018 in Moscow, Russia. The presentation discusses focusing on quality over quantity in software projects and implementing fear-driven development practices like rigorous testing and code reviews to motivate high-quality work. It also promotes the concepts of making small, isolated changes and experimentation to improve quality.
Yegor Bugayenko gave a presentation at DevOpsDays Boston about experts vs expertise. He discussed trends like the growing variety of DevOps tools, increasing data volume, and higher employee turnover rates. This leads to problems like job insecurity and silos of knowledge within organizations. Bugayenko proposes the solution of Zerocracy, which involves extreme practices like #NoMagic where technology dependencies are eliminated, #NoMeetings where work is demonstrated through artifacts not discussions, and #NoSalaries where compensation is based on results not time spent. The goal is to focus on expertise over experts by making knowledge accessible organization-wide.
This document discusses Zold, a proposed cryptocurrency that does not use blockchain technology. It aims to be faster, more lightweight, and more efficient than blockchains like Bitcoin. Zold uses a novel approach called "dynamic proof-of-work" to achieve consensus without mining. This allows it to process over 1 million transactions per second using lightweight nodes while consuming far less energy than blockchains. The founder seeks feedback on this new approach to distributed trust.
The document discusses centralized payment systems, decentralized payment systems (cryptocurrencies), and the evolution of trust from duplication to encryption to consensus. It addresses topics like the energy consumption and costs of proof-of-work blockchains, as well as alternatives like proof-of-stake and discusses tradeoffs between cost, speed and size for different consensus mechanisms. It concludes by asking the reader's thoughts on these topics.
This document contains tweets from Yegor Bugayenko discussing ways to cut corners and stay cool as a developer. Some of the suggestions include creating tickets and waiting for code to be cleaned up before working on issues, reproducing bugs but not fixing them, disabling features that cause bugs, and saying no to taking on work. The overall messages promote writing maintainable code, catching bugs with tests, and avoiding trying to fix problems without the proper documentation, tools, or time.
This document appears to be a series of tweets from Yegor Bugayenko discussing various topics related to programming such as good programmers, tools used by programmers like IDEs and Agile practices, qualities of effective teams, and the importance of socio-technical skills for working with people through code. It also includes some quotes about talented and motivated individuals, and how effective teams are more important than tools or processes alone.
This document discusses the disadvantages of using Java annotations and provides alternatives to annotations for various use cases. It argues that annotations hurt maintainability by embedding logic into code comments rather than classes. It then provides examples of how to implement caching, dependency injection, XML marshalling, HTTP endpoints, and other features without using annotations by moving the logic and configuration into dedicated classes and objects.
5. /17@yegor256 5
When information from below
reaches up high, and the
concerns of up high penetrate
to below, this is the most
ideal situation.
Wei Liao Zi
4th century BCИдеально, когда информация снизу
попадает наверх, а трудности наверху
известны внизу.
9. /17@yegor256 9
We're basically more
productive when we work
individually to achieve
personal goals rather than
being teamed up.
Max Ringelmann
1913Мы более продуктивны, когда работаем
над достижением личных целей, чем
когда в командах.
15. /17@yegor256 15
Lord of Flies (1963)
Новая Земля (2008)
Das Experiment (2001)
The Men Who Stare at Goats (2009)
16. /17@yegor256 16C-players
Слабые сотрудники
Concealed Risks
Скрываемые риски
Cowardly Manager
Трусливый менеджер
Group Responsibility
Коллективная ответственность
Steve Jobs Speeches
Лекции о Стиве Джобсе
Birthdays
Дни рождения
Closed Doors
Закрытые двери