Fourteenth Meetup: With the use of great patterns comes great responsibility
I am very excited to announce that Kim Martin will be the guest speaker of the Meetup of October with central theme patterns.
According to Merriam-Webster, the definition of a pattern is as follows: a repeated form or design especially that is used to decorate something, the regular and repeated way in which something happens or is done, something that happens in a regular and repeated way. As software developers we are continuously trying to introduce and follow patterns to excel in our work. As a mathematician or data scientist we aim to crack the patterns that were introduced by others to be able to predict the future.
Talk of the month: A software performance primer: Theory to practice By Kim Martin
Questions to be answered: what is Software Performance Engineering; what are its foundations; what are its guiding principles/patterns; why is Software Performance Engineering necessary; when can it be used effectively; how do we recognize performance issues; how do we solve performance problems?
Abstract Software performance is one of the intangibles of the art of software program/system design. Traditionally the nuts and bolts of software programming have been the functional aspects of design and implementation of features. However, it has become blatantly apparent that core elements are missing for the proper operation of the software, which falls into categories far outside functional considerations: performance, maintain-ability, service-ability, use-ability and modularity to name but a few.
This presentation will focus on the core mathematical elements used in Software Performance Engineering (SPE) that allow quick modeling of system operation. A quick review of Theta notation and its power in performance models will be illustrated. SPE design principles will be presented along with performance patterns and anti-patterns to whet the appetite. Recognition of the plethora of patterns and anti-patterns is daunting, and to add to the difficulty, the number is constantly increasing as we find new ways to either improve, or hinder the software development process.
Paper of the month: The Promises and Perils of Mining Github By Kalliamvakou et al. (http://dl.acm.org/citation.cfm?id=2597074) and an extended version (http://leif.me/papers/Kalliamvakou2015a.pdf) (presented by Mary Loubele)
Have you ever dreamt of mining all the public repos of github? Before diving into this interesting challenge you should read this paper. This paper discusses the issues that researches might encounter when they want to use the data that can be derived from Github for software research.
As usual, we ask people to adhere to our Code of Conduct (http://www.amotlpaa.org/kcapw/anti-harassment-policy.html) so that everyone may commute, replicate, and achieve communal consistency.