| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| courses:cs397:winter2017:buzzword_bingo [2017/05/02 20:40] – admin | courses:cs397:winter2017:buzzword_bingo [2017/05/05 16:13] – [Triage] admin |
|---|
| ===== Full-stack Development ===== | ===== Full-stack Development ===== |
| |
| development which involves both front end and back end development, working with PHP, HTML, CSS, JavaScript, etc. Full-stack development combines working with systems infrastructures, manipulating databases, API/back-end code, front-end, and project management (Agile, SCRUM, Kanban) | Development which involves both front end and back end development, working with PHP, HTML, CSS, JavaScript, etc. Full-stack development combines working with systems infrastructures, manipulating databases, API/back-end code, front-end, and project management (Agile, SCRUM, Kanban) |
| |
| * System admin - Linux, shell scripting | * System admin - Linux, shell scripting |
| * Search - Elasticsearch; | * Search - Elasticsearch; |
| * Caching - Varnish | * Caching - Varnish |
| * Version Control - Git, Mercurial SVN | * Version Control - Git, Mercurial SVN |
| * Back-end: Apache, PHP, MongoDB, SQL, MySQL | * Back-end: Apache, PHP, MongoDB, SQL, MySQL |
| * Front-end: HTML, CSS, JavaScript, jQuery, AJAX, XML, WebSocket | * Front-end: HTML, CSS, JavaScript, jQuery, AJAX, XML, WebSocket |
| |
| https://www.sitepoint.com/full-stack-developer/ | Resources: |
| https://www.quora.com/What-does-the-term-full-stack-programmer-mean | |
| http://www.pearltrees.com/t/company-picks/at-t/id5539108/item50626959 | * https://www.sitepoint.com/full-stack-developer/ |
| | * https://www.quora.com/What-does-the-term-full-stack-programmer-mean |
| | * http://www.pearltrees.com/t/company-picks/at-t/id5539108/item50626959 |
| |
| ===== Data-driven development ===== | ===== Data-driven development ===== |
| ==== Flux ==== | ==== Flux ==== |
| |
| used by Facebook | * used by Facebook |
| | * application architecture for client side apps |
| application architecture for client side apps | |
| |
| |
| |
| Sources: | Sources: |
| https://branch-blog.qlik.com/tools-and-platforms-for-data-driven-development-bb25d9c1e6ae#.oxtbihl5z | * https://branch-blog.qlik.com/tools-and-platforms-for-data-driven-development-bb25d9c1e6ae#.oxtbihl5z |
| https://facebook.github.io/flux/docs/in-depth-overview.html#content | * https://facebook.github.io/flux/docs/in-depth-overview.html#content |
| |
| ===== DevOps (software DEVelopment and Information Technology OPerationS) ===== | ===== DevOps (software DEVelopment and Information Technology OPerationS) ===== |
| |
| ===== Triage ===== | ===== Triage ===== |
| Triage is the act of analyzing, understanding, and categorizing a specific set of defects, in preparation for making a repair scheduling decision. For a given set of defects, you need to determine how to act on them and proceed with repairs. The more serious defects, those with the highest priorities, receive action first, usually because of their import or because they are blocking further project activity. Source: http://www.informit.com/articles/article.aspx?p=2123715&seqNum=3 | Triage is the act of analyzing, understanding, and categorizing a specific set of defects, in preparation for making a repair scheduling decision. For a given set of defects, you need to determine how to act on them and proceed with repairs. The more serious defects, those with the highest priorities, receive action first, usually because of their import or because they are blocking further project activity. |
| | |
| | Source: http://www.informit.com/articles/article.aspx?p=2123715&seqNum=3 |
| |
| =====Monitoring===== | =====Monitoring===== |
| Project managers monitor the progress of a project. Three levels of monitoring include: activity levels, status reports, and milestone analysis. | Project managers monitor the progress of a project. Three levels of monitoring include: activity levels, status reports, and milestone analysis. |
| Triage | |
| |
| Allows threads to temporarily stop being mutually exclusive as they wait for a condition to be met. | |
| |
| |
| ===== Branch Deploy ===== | ===== Branch Deploy ===== |
| Uses: SVN and GitHub (and other VCS) | Uses: SVN and GitHub (and other VCS) |
| |
| Sources: http://guides.beanstalkapp.com/version-control/branching-best-practices.html | Sources: |
| https://confluence.atlassian.com/bamboo/deployments-from-branches-407724097.html | * http://guides.beanstalkapp.com/version-control/branching-best-practices.html |
| | * https://confluence.atlassian.com/bamboo/deployments-from-branches-407724097.html |
| |
| |
| |
