The Hacker's Guide to Python

Total Page:16

File Type:pdf, Size:1020Kb

The Hacker's Guide to Python Contents Starting your project . P⁴thon versions ................................. . Project la⁴out ................................... . Version numbering ............................... . Coding st⁴le & automated checks ...................... Modules and libraries . The import s⁴stem ................................ . Standard libraries ................................ . External libraries ................................. . Frameworks .................................... . Interview with Doug Hellmann ........................ . Managing API changes ............................. . Interview with Christophe de Vienne .................... Documentation . Getting started with Sphinx and reST .................... CONTENTS ii . Sphinx modules ................................. . Extending Sphinx ................................ Distribution . A bit of histor⁴ .................................. . Packaging with pbr ............................... . The Wheel format ................................ . Package installation ............................... . Sharing ⁴our work with the world ...................... . Interview with Nick Coghlan .......................... . Entr⁴ points .................................... .. Visualising entr⁴ points ........................ .. Using console scripts ......................... .. Using plugins and drivers ....................... Virtual environments Unit testing . The basics ..................................... . Fixtures ....................................... . Mocking ...................................... . Scenarios ..................................... . Test streaming and parallelism . . Coverage ...................................... Using virtualenv with tox ............................ CONTENTS iii . Testing polic⁴ ................................... Interview with Robert Collins . Methods and decorators . Creating decorators ............................... How methods work in P⁴thon . . Static methods .................................. Class method ................................... Abstract methods ................................ Mixing static, class, and abstract methods . . The truth about super ............................. Functional programming . Generators ..................................... List comprehensions .............................. Functional functions functioning . The AST . H⁴ .......................................... Interview with Paul Tagliamonte . Performances and optimizations . Data structures .................................. Profiling ...................................... Ordered list and bisect ............................. CONTENTS iv . Namedtuple and slots ............................. Memoi⁵ation ................................... P⁴P⁴ ........................................ Achieving ⁵ero cop⁴ with the buffer protocol . . Interview with Victor Stinner . Scaling and architecture . A note on multi-threading . . Multiprocessing vs multithreading . . As⁴nchronous and event-driven architecture . . Service-oriented architecture . RDBMS and ORM . Streaming data with Flask and PostgreSQL . . Interview with Dimitri Fontaine . Python support strategies . Language and standard librar⁴ . . External libraries ................................. Using six ...................................... Write less, code more . Single dispatcher ................................. Context managers ................................ List of Figures . Standard package director⁴ .......................... . Coverage of ceilometer.publisher . . KCacheGrind example ............................. Using slice on memoryview objects . . P⁴thon base classes .............................. P⁴thon base classes .............................. List of Examples . A pep run ..................................... . Running pep with --ignore .......................... . Hy module importer ............................... . A documented API change ........................... . A documented API change with warning . . Running python -W error ........................... . Code from sphinxcontrib.pecanwsme.rest.setup . . setup.py using distutils ............................. . setup.py using setuptools ........................... . Using setup.py sdist ............................. . Result of epi group list .............................. . Result of epi group show console_scripts . . Result of epi ep show console_scripts coverage . . A console script generated b⁴ setuptools . . Running p⁴timed ................................. . Automatic virtual environment creation . . Boostraping a venv environment ....................... . A reall⁴ simple test in test_true.py ..................... . Failing a test .................................... . Skipping tests ................................... LIST OF EXAMPLES vii . Using setUp with unittest ........................... . Using fixtures.EnvironmentVariable ................... . Basic mock usage ................................ . Checking method calls ............................. . Using mock.patch ................................ . Using mock.patch to test a set of behaviour . . testscenarios basic usage .......................... . Using testscenarios to test drivers . . Using subunit2pyunit ............................. A .testr.conf file ................................ Running testr run --parallel . . Using nosetests --with-coverage . . Using coverage with testrepository . . A .travis.yml example file . . A registering decorator ............................. Source code of functools.update_wrapper in P⁴thon . . Using functools.wraps ............................. Retrieving function arguments using inspect . . A P⁴thon method ............................... A P⁴thon method ............................... Calling unbound get_si⁵e in P⁴thon . . Calling unbound get_si⁵e in P⁴thon . . Calling bound get_size ............................ @staticmethod usage .............................. Implementing an abstract method . . Implementing an abstract method using abc . . Mixing @classmethod and @abstractmethod . . Using super() with abstract methods . LIST OF EXAMPLES viii . yield returning a value ............................. filter usage in P⁴thon ............................. Using first .................................... Using the operator module with itertools.groupby . . Parsing P⁴thon code to AST . . Hello world using P⁴thon AST . . Changing all binar⁴ operation to addition . . Using the cProfile module . . Using KCacheGrind to visuali⁵e P⁴thon profiling data . . A function defined in a function, disassembled . . Disassembling a closure ............................ Usage of bisect ................................. Usage of bisect.insort ............................ A SortedList implementation . . A class declaration using __slots__ . . Memor⁴ usage of objects using __slots__ . .Declaring a class using namedtuple . .Memor⁴ usage of a class built from collections.namedtuple . .A basic memoi⁵ation technique . .Using functools.lru_cache . . Result of time python worker.py . . Worker using multiprocessing . . Result of time python worker.py . . Basic example of using select . . Example with pyev ................................ Creating the message table . . The notify_on_insert function . . The trigger for notify_on_insert . LIST OF EXAMPLES ix . Receiving notifications in P⁴thon . . Flask streamer application . . Simple implementation of a context object . . Simplest usage of contextlib.contextmanager . . Using a context manager on a pipeline object . . Opening two files at the same time . . Opening two files at the same time with one with statement . About this book Version . released in March . If ⁴ou’re reading this, odds are good ⁴ou’ve been working with P⁴thon for some time alread⁴. Ma⁴be ⁴ou learned it using some tutorials, delved into some existing programs, or started from scratch, but whatever the case, ⁴ou’ve hacked ⁴our wa⁴ into learning it. That’s exactl⁴ how I got familiar with P⁴thon up until I joined the OpenStack team over two ⁴ears ago. Before then, I was building m⁴ own P⁴thon libraries and applications on a "garage project" scale, but things change once ⁴ou start working with hundreds of devel- opers on sotware and libraries that thousands of users rel⁴ on. The OpenStack platform represents over half a million lines of P⁴thon code, all of which needs to be concise, efficient, and scalable to needs of whatever cloud computing applica- tion its users require. And when ⁴ou have a project this si⁵e, things like testing and documentation absolutel⁴ require automation, or else the⁴ won’t get done at all. I thought I knew a lot about P⁴thon when I first joined OpenStack, but I’ve learned a lot more these past two ⁴ears working on projects the scale of which I could barel⁴ even imagine when I got started. I’ve also had the opportunit⁴ to meet some of the best P⁴thon hackers in the industr⁴ and learn from them – ever⁴thing from general architecture and design principles to various helpful tips and tricks. Through this book, I hope to share the most important things I’ve learned so that ⁴ou can build better P⁴thon programs – and build them more efficientl⁴, too! Starting your project 1.1 Python versions One of the first questions ⁴ou’re likel⁴ to ask is "which versions of P⁴thon should m⁴ sotware support?". It’s well worth asking, since each new version of P⁴thon introduces new features
Recommended publications
  • Learning React Functional Web Development with React and Redux
    Learning React Functional Web Development with React and Redux Alex Banks and Eve Porcello Beijing Boston Farnham Sebastopol Tokyo Learning React by Alex Banks and Eve Porcello Copyright © 2017 Alex Banks and Eve Porcello. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://oreilly.com/safari). For more information, contact our corporate/insti‐ tutional sales department: 800-998-9938 or [email protected]. Editor: Allyson MacDonald Indexer: WordCo Indexing Services Production Editor: Melanie Yarbrough Interior Designer: David Futato Copyeditor: Colleen Toporek Cover Designer: Karen Montgomery Proofreader: Rachel Head Illustrator: Rebecca Demarest May 2017: First Edition Revision History for the First Edition 2017-04-26: First Release See http://oreilly.com/catalog/errata.csp?isbn=9781491954621 for release details. The O’Reilly logo is a registered trademark of O’Reilly Media, Inc. Learning React, the cover image, and related trade dress are trademarks of O’Reilly Media, Inc. While the publisher and the authors have used good faith efforts to ensure that the information and instructions contained in this work are accurate, the publisher and the authors disclaim all responsibility for errors or omissions, including without limitation responsibility for damages resulting from the use of or reliance on this work. Use of the information and instructions contained in this work is at your own risk. If any code samples or other technology this work contains or describes is subject to open source licenses or the intellectual property rights of others, it is your responsibility to ensure that your use thereof complies with such licenses and/or rights.
    [Show full text]
  • UNIVERSITY of CALIFORNIA SAN DIEGO Simplifying Datacenter Fault
    UNIVERSITY OF CALIFORNIA SAN DIEGO Simplifying datacenter fault detection and localization A dissertation submitted in partial satisfaction of the requirements for the degree of Doctor of Philosophy in Computer Science by Arjun Roy Committee in charge: Alex C. Snoeren, Co-Chair Ken Yocum, Co-Chair George Papen George Porter Stefan Savage Geoff Voelker 2018 Copyright Arjun Roy, 2018 All rights reserved. The Dissertation of Arjun Roy is approved and is acceptable in quality and form for publication on microfilm and electronically: Co-Chair Co-Chair University of California San Diego 2018 iii DEDICATION Dedicated to my grandmother, Bela Sarkar. iv TABLE OF CONTENTS Signature Page . iii Dedication . iv Table of Contents . v List of Figures . viii List of Tables . x Acknowledgements . xi Vita........................................................................ xiii Abstract of the Dissertation . xiv Chapter 1 Introduction . 1 Chapter 2 Datacenters, applications, and failures . 6 2.1 Datacenter applications, networks and faults . 7 2.1.1 Datacenter application patterns . 7 2.1.2 Datacenter networks . 10 2.1.3 Datacenter partial faults . 14 2.2 Partial faults require passive impact monitoring . 17 2.2.1 Multipath hampers server-centric monitoring . 18 2.2.2 Partial faults confuse network-centric monitoring . 19 2.3 Unifying network and server centric monitoring . 21 2.3.1 Load-balanced links mean outliers correspond with partial faults . 22 2.3.2 Centralized network control enables collating viewpoints . 23 Chapter 3 Related work, challenges and a solution . 24 3.1 Fault localization effectiveness criteria . 24 3.2 Existing fault management techniques . 28 3.2.1 Server-centric fault detection . 28 3.2.2 Network-centric fault detection .
    [Show full text]
  • Crawling Code Review Data from Phabricator
    Friedrich-Alexander-Universit¨atErlangen-N¨urnberg Technische Fakult¨at,Department Informatik DUMITRU COTET MASTER THESIS CRAWLING CODE REVIEW DATA FROM PHABRICATOR Submitted on 4 June 2019 Supervisors: Michael Dorner, M. Sc. Prof. Dr. Dirk Riehle, M.B.A. Professur f¨urOpen-Source-Software Department Informatik, Technische Fakult¨at Friedrich-Alexander-Universit¨atErlangen-N¨urnberg Versicherung Ich versichere, dass ich die Arbeit ohne fremde Hilfe und ohne Benutzung anderer als der angegebenen Quellen angefertigt habe und dass die Arbeit in gleicher oder ¨ahnlicherForm noch keiner anderen Pr¨ufungsbeh¨ordevorgelegen hat und von dieser als Teil einer Pr¨ufungsleistung angenommen wurde. Alle Ausf¨uhrungen,die w¨ortlich oder sinngem¨aߨubernommenwurden, sind als solche gekennzeichnet. Nuremberg, 4 June 2019 License This work is licensed under the Creative Commons Attribution 4.0 International license (CC BY 4.0), see https://creativecommons.org/licenses/by/4.0/ Nuremberg, 4 June 2019 i Abstract Modern code review is typically supported by software tools. Researchers use data tracked by these tools to study code review practices. A popular tool in open-source and closed-source projects is Phabricator. However, there is no tool to crawl all the available code review data from Phabricator hosts. In this thesis, we develop a Python crawler named Phabry, for crawling code review data from Phabricator instances using its REST API. The tool produces minimal server and client load, reproducible crawling runs, and stores complete and genuine review data. The new tool is used to crawl the Phabricator instances of the open source projects FreeBSD, KDE and LLVM. The resulting data sets can be used by researchers.
    [Show full text]
  • Artificial Intelligence for Understanding Large and Complex
    Artificial Intelligence for Understanding Large and Complex Datacenters by Pengfei Zheng Department of Computer Science Duke University Date: Approved: Benjamin C. Lee, Advisor Bruce M. Maggs Jeffrey S. Chase Jun Yang Dissertation submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in the Department of Computer Science in the Graduate School of Duke University 2020 Abstract Artificial Intelligence for Understanding Large and Complex Datacenters by Pengfei Zheng Department of Computer Science Duke University Date: Approved: Benjamin C. Lee, Advisor Bruce M. Maggs Jeffrey S. Chase Jun Yang An abstract of a dissertation submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in the Department of Computer Science in the Graduate School of Duke University 2020 Copyright © 2020 by Pengfei Zheng All rights reserved except the rights granted by the Creative Commons Attribution-Noncommercial Licence Abstract As the democratization of global-scale web applications and cloud computing, under- standing the performance of a live production datacenter becomes a prerequisite for making strategic decisions related to datacenter design and optimization. Advances in monitoring, tracing, and profiling large, complex systems provide rich datasets and establish a rigorous foundation for performance understanding and reasoning. But the sheer volume and complexity of collected data challenges existing techniques, which rely heavily on human intervention, expert knowledge, and simple statistics. In this dissertation, we address this challenge using artificial intelligence and make the case for two important problems, datacenter performance diagnosis and datacenter workload characterization. The first thrust of this dissertation is the use of statistical causal inference and Bayesian probabilistic model for datacenter straggler diagnosis.
    [Show full text]
  • Unicorn: a System for Searching the Social Graph
    Unicorn: A System for Searching the Social Graph Michael Curtiss, Iain Becker, Tudor Bosman, Sergey Doroshenko, Lucian Grijincu, Tom Jackson, Sandhya Kunnatur, Soren Lassen, Philip Pronin, Sriram Sankar, Guanghao Shen, Gintaras Woss, Chao Yang, Ning Zhang Facebook, Inc. ABSTRACT rative of the evolution of Unicorn's architecture, as well as Unicorn is an online, in-memory social graph-aware index- documentation for the major features and components of ing system designed to search trillions of edges between tens the system. of billions of users and entities on thousands of commodity To the best of our knowledge, no other online graph re- servers. Unicorn is based on standard concepts in informa- trieval system has ever been built with the scale of Unicorn tion retrieval, but it includes features to promote results in terms of both data volume and query volume. The sys- with good social proximity. It also supports queries that re- tem serves tens of billions of nodes and trillions of edges quire multiple round-trips to leaves in order to retrieve ob- at scale while accounting for per-edge privacy, and it must jects that are more than one edge away from source nodes. also support realtime updates for all edges and nodes while Unicorn is designed to answer billions of queries per day at serving billions of daily queries at low latencies. latencies in the hundreds of milliseconds, and it serves as an This paper includes three main contributions: infrastructural building block for Facebook's Graph Search • We describe how we applied common information re- product. In this paper, we describe the data model and trieval architectural concepts to the domain of the so- query language supported by Unicorn.
    [Show full text]
  • 2.3 Apache Chemistry
    UNIVERSITY OF DUBLIN TRINITY COLLEGE DISSERTATION PRESENTED TO THE UNIVERSITY OF DUBLIN,TRINITY COLLEGE IN PARTIAL FULFILMENT OF THE REQUIREMENTS FOR THE DEGREE OF MAGISTER IN ARTE INGENIARIA Content Interoperability and Open Source Content Management Systems An implementation of the CMIS standard as a PHP library Author: Supervisor: MATTHEW NICHOLSON DAVE LEWIS Submitted to the University of Dublin, Trinity College, May, 2015 Declaration I, Matthew Nicholson, declare that the following dissertation, except where otherwise stated, is entirely my own work; that it has not previously been submitted as an exercise for a degree, either in Trinity College Dublin, or in any other University; and that the library may lend or copy it or any part thereof on request. May 21, 2015 Matthew Nicholson i Summary This paper covers the design, implementation and evaluation of PHP li- brary to aid in use of the Content Management Interoperability Services (CMIS) standard. The standard attempts to provide a language indepen- dent and platform specific mechanisms to better allow content manage- ment systems (CM systems) work together. There is currently no PHP implementation of CMIS server framework available, at least not widely. The name given to the library is Elaphus CMIS. The implementation should remove a barrier for making PHP CM sys- tems CMIS compliant. Aswell testing how language independent the stan- dard is and look into the features of PHP programming language. The technologies that are the focus of this report are: CMIS A standard that attempts to structure the data within a wide range of CM systems and provide standardised API for interacting with this data.
    [Show full text]
  • Learning React Modern Patterns for Developing React Apps
    Second Edition Learning React Modern Patterns for Developing React Apps Alex Banks & Eve Porcello SECOND EDITION Learning React Modern Patterns for Developing React Apps Alex Banks and Eve Porcello Beijing Boston Farnham Sebastopol Tokyo Learning React by Alex Banks and Eve Porcello Copyright © 2020 Alex Banks and Eve Porcello. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://oreilly.com). For more information, contact our corporate/institutional sales department: 800-998-9938 or [email protected]. Acquisitions Editor: Jennifer Pollock Indexer: Judith McConville Development Editor: Angela Rufino Interior Designer: David Futato Production Editor: Kristen Brown Cover Designer: Karen Montgomery Copyeditor: Holly Bauer Forsyth Illustrator: Rebecca Demarest Proofreader: Abby Wheeler May 2017: First Edition June 2020: Second Edition Revision History for the Second Edition 2020-06-12: First Release See http://oreilly.com/catalog/errata.csp?isbn=9781492051725 for release details. The O’Reilly logo is a registered trademark of O’Reilly Media, Inc. Learning React, the cover image, and related trade dress are trademarks of O’Reilly Media, Inc. The views expressed in this work are those of the authors, and do not represent the publisher’s views. While the publisher and the authors have used good faith efforts to ensure that the information and instructions contained in this work are accurate, the publisher and the authors disclaim all responsibility for errors or omissions, including without limitation responsibility for damages resulting from the use of or reliance on this work.
    [Show full text]
  • Elmulating Javascript
    Linköping University | Department of Computer science Master thesis | Computer science Spring term 2016-07-01 | LIU-IDA/LITH-EX-A—16/042--SE Elmulating JavaScript Nils Eriksson & Christofer Ärleryd Tutor, Anders Fröberg Examinator, Erik Berglund Linköpings universitet SE–581 83 Linköping +46 13 28 10 00 , www.liu.se Abstract Functional programming has long been used in academia, but has historically seen little light in industry, where imperative programming languages have been dominating. This is quickly changing in web development, where the functional paradigm is increas- ingly being adopted. While programming languages on other platforms than the web are constantly compet- ing, in a sort of survival of the fittest environment, on the web the platform is determined by the browsers which today only support JavaScript. JavaScript which was made in 10 days is not well suited for building large applications. A popular approach to cope with this is to write the application in another language and then compile the code to JavaScript. Today this is possible to do in a number of established languages such as Java, Clojure, Ruby etc. but also a number of special purpose language has been created. These are lan- guages that are made for building front-end web applications. One such language is Elm which embraces the principles of functional programming. In many real life situation Elm might not be possible to use, so in this report we are going to look at how to bring the benefits seen in Elm to JavaScript. Acknowledgments We would like to thank Jörgen Svensson for the amazing support thru this journey.
    [Show full text]
  • Ecological Momentary Assessments from a Cross-Platform, Native Application
    Bachelor’s Thesis Ecological Momentary Assessments from a Cross-Platform, Native Application Jake Davison July, 2018 supervised by: Dr. Frank Blaauw Dr. Ando Emerencia Contents 1 Introduction 3 1.1 Ecological Momentary Assessments . 3 1.2 u-can-act . 4 1.3 Project . 4 2 Related Work and Background 5 2.1 Mobile EMA Applications . 5 2.1.1 RealLife Exp . 5 2.1.2 mEMA . 5 2.1.3 PIEL Survey . 6 2.1.4 Need for New Application . 6 2.2 Native Mobile Applications From a Single Code Base . 6 2.2.1 React Native . 7 2.2.2 Ionic / Apache Cordova . 8 2.2.3 Choice of Technology . 10 2.3 Domain Specific Languages . 10 2.4 Service Oriented Architectures . 11 3 System Overview 12 3.1 Project Requirements . 12 3.2 System Architecture . 13 3.3 Display of Questions . 14 3.3.1 Range . 14 3.3.2 Checkbox . 15 3.3.3 Radio . 15 3.3.4 Textfield . 15 3.3.5 Time . 15 3.3.6 Raw . 15 3.3.7 Unsubscribe . 15 3.4 Required and Supported Functionalities . 15 4 Implementation 17 4.1 Receiving, Parsing and Displaying Question Data . 17 4.2 Logging In to Receive Questionnaires . 19 4.3 Sending User Input . 20 5 Conclusions 22 5.1 Resulting Software . 22 5.1.1 Single Code Base . 22 5.1.2 Pull in, Parse and Display Questions . 22 5.1.3 Submitting User Input . 23 5.1.4 User Login . 23 5.1.5 Push Notification . 24 1 5.1.6 Applications Running on Device for iOS and Android .
    [Show full text]
  • “They Keep Coming Back Like Zombies”: Improving Software
    “They Keep Coming Back Like Zombies”: Improving Software Updating Interfaces Arunesh Mathur, Josefine Engel, Sonam Sobti, Victoria Chang, and Marshini Chetty, University of Maryland, College Park https://www.usenix.org/conference/soups2016/technical-sessions/presentation/mathur This paper is included in the Proceedings of the Twelfth Symposium on Usable Privacy and Security (SOUPS 2016). June 22–24, 2016 • Denver, CO, USA ISBN 978-1-931971-31-7 Open access to the Proceedings of the Twelfth Symposium on Usable Privacy and Security (SOUPS 2016) is sponsored by USENIX. “They Keep Coming Back Like Zombies”: Improving Software Updating Interfaces Arunesh Mathur Josefine Engel Sonam Sobti [email protected] [email protected] [email protected] Victoria Chang Marshini Chetty [email protected] [email protected] Human–Computer Interaction Lab, College of Information Studies University of Maryland, College Park College Park, MD 20742 ABSTRACT ers”, and “security analysts” only install updates about half Users often do not install security-related software updates, the time more than non-experts [34]. Despite this evidence leaving their devices open to exploitation by attackers. We that there are factors influencing updating behaviors, the are beginning to understand what factors affect this soft- majority of research on software updates focuses on the net- ware updating behavior but the question of how to improve work and systems aspect of delivering updates to end users current software updating interfaces however remains unan- [17, 47, 24, 13, 23]. swered. In this paper, we begin tackling this question by However, a growing number of studies have begun to explore studying software updating behaviors, designing alternative the human side of software updates for Microsoft (MS) Win- updating interfaces, and evaluating these designs.
    [Show full text]
  • Realtime Data Processing at Facebook
    Realtime Data Processing at Facebook Guoqiang Jerry Chen, Janet L. Wiener, Shridhar Iyer, Anshul Jaiswal, Ran Lei Nikhil Simha, Wei Wang, Kevin Wilfong, Tim Williamson, and Serhat Yilmaz Facebook, Inc. ABSTRACT dural language (such as C++ or Java) essential? How Realtime data processing powers many use cases at Face- fast can a user write, test, and deploy a new applica- book, including realtime reporting of the aggregated, anon- tion? ymized voice of Facebook users, analytics for mobile applica- • Performance: How much latency is ok? Milliseconds? tions, and insights for Facebook page administrators. Many Seconds? Or minutes? How much throughput is re- companies have developed their own systems; we have a re- quired, per machine and in aggregate? altime data processing ecosystem at Facebook that handles hundreds of Gigabytes per second across hundreds of data • Fault-tolerance: what kinds of failures are tolerated? pipelines. What semantics are guaranteed for the number of times Many decisions must be made while designing a realtime that data is processed or output? How does the system stream processing system. In this paper, we identify five store and recover in-memory state? important design decisions that affect their ease of use, per- formance, fault tolerance, scalability, and correctness. We • Scalability: Can data be sharded and resharded to pro- compare the alternative choices for each decision and con- cess partitions of it in parallel? How easily can the sys- trast what we built at Facebook to other published systems. tem adapt to changes in volume, both up and down? Our main decision was targeting seconds of latency, not Can it reprocess weeks worth of old data? milliseconds.
    [Show full text]
  • The Compassion Project
    The Compassion Project Mitchell Black, Kyle Melton, and Amelia Getty 25 April 2019 Abstract The Compassion Project is a public, collaborative art installation sourced from approximately 6,500 artists around Bozeman. Each participating artist painted an 8”x8” wooden block with their own interpretation of compassion. To accompany their art, each artist wrote an artist statement defining compassion or explaining how their block relates to compassion. We created a mobile app as a companion to the installation. The primary usage of this app is to allow visitors to lookup the artist statement on their phone from the unique ID number assigned to each block. Additional app functionality includes favoriting pictures, personal user viewing history, and usage statistics. We also performed a comparative analysis of image descriptors for the blocks. We were interested in the idea using an picture to search for that block artist’s statement. We have images of each block to be used as a thumbnail when users look up a block. To evaluate which image descriptors are most effective at grouping the blocks, we took secondary photos of a subset of the blocks and tested whether the descriptors can pair the thumbnail of a block to our photo of a block. 1 Qualifications See attached resumes. 2 Bozeman, MT 59718 ⋄ 406-580-3154⋄ [email protected] ⋄ linkedin.com/in/ameliagetty Amelia Getty ​ ​ Computer Science senior with diverse experience poised to transition to software development or engineering. Organized and dependable. Aptitude to learn quickly and work independently and with a team. PROGRAMMING EXPERIENCE Java ⋄ PHP (Laravel) ⋄ C ⋄ Python ⋄ C++ ⋄ SQL Linux Systems Admin ⋄ Databases ⋄ Graphics ⋄ Networks ⋄ Security (2019) EDUCATION ♢ Computer Science​.​ ​Montana State University​, 2017 - 2019 ♢ BA Modern Languages and Literatures, German​.
    [Show full text]