The long way through Software Craftsmanship

Category: Poodr

Jun 1, 2015 - 1 minute read - Comments - poodrbookcategorymetasandi-metz

This category is mainly dedicated to anything related or included in the book ‘Practical Object-Oriented Design in Ruby’, by Sandi Metz Note: This has been created a posteriori with a previous date

Internal training: QA & how to test

May 18, 2015 - 2 minute read - Comments - traininginternalinternal-trainingquality-assuranceqabrown-bag-session

At a client, we’ve done today an internal training on “QA & how to test”. In it, the most skilled person with the QA role in the dev team has explained to us some techniques and concepts for testing My notes Verification vs validation: building the product right vs building the right product. Principles Extracted from ISTQB: testing shows presence of defects exhaustive testing is impossible early testing is better than later testing defect clustering: areas with bigger defect ratio or more critical, etc should be tested more thoroughly pesticide paradox testing is context-dependent absence of errors fallacy: the absence of defects does not imply perfect software.

Paper: TDD in industrial teams

May 12, 2015 - 1 minute read - Comments - paperinvestigationspringertddnachiappan-nagappanmichael-maximilienthirumalesh-bhatlaurie-williams2008quote

I’ve read this paper by Nagappan, Maximilien, Bhat and Williams on the cost, advantages, pitfalls of doing TDD in industrial teams (private companies who create software). My notes Abstract: little empirical evidence supports or refutes the utility of this practice in an industrial context they seem to be talking about inside-out tdd as in chapter 2 (page 291), they talk about small units and then integrating them in a bigger context Benefits taken from chapter 2 (page 292)

Talk: Software is eating the world

May 10, 2015 - 2 minute read - Comments - erik-meijertalkagiletddreaktor-dev-day2014analogy

I’ve watched this talk by Erik Meijer My notes Agile!: The Good, the Hype and the Ugly The hacker way code always wins vs manager always wins source: http://www.wired.com/2012/02/zuck-letter/ we’re doing maths => we’re building a proof reinforcement learning agent is the company related to “build, measure, learn” by Eric Ries (the lean startup) Feedback systems Open (no) feedback system, such as timed sprinklers Closed feedback system Output only system Why everything is software Examples of everything is software Software is eating the world Even hardware is modeled as software Modeling as a Finite State Machine (FSM) There’s memory in the feedback loop.