T Ashok (ash_thiru on Twitter)
Summary
Inspired by how the world is handling Covid19, this article as a SlideShare lists actions taken and criteria met to contain the pandemic and correlate this to how we can deliver clean code for large scale software systems. This article focuses on the process flow and criteria for delivering clean code.
Check out the previous article COVID19 and Clean Code Part 1: Techniques,
that outlines techniques to deliver clean code, inspired by Covid19.
T Ashok @ash_thiru on Twitter
Summary
SmartQA is a beautiful combination of thinking styles, a mindset of brilliance and minimalism, tech prowess, heightened clarity and great design and meaningful pauses, outlined as ten suggestions in this article.
#1 Embrace multiple thinking styles
Inculcate the deductive ability of a mathematician, creativity of an artist, mind of an engineer, value perception of a businessman, technical savviness, empathy, doggedness and nimbleness.
#2 Have a mindset of brilliant engineering
Step into end user’s shoes, architect/design robustly, inject code to aid testability, strive to test minimally, do test related tasks lightweight.
#3 Analyse well, exploit tools for doing
Much like the skill of a doctor to diagnose with exploiting the machines in the process. “Doing SmartQA”s a brilliant combination of “human powered and machine assisted” . The WHAT to-do is human while HOW-to-do is powered by machine/tools.
#4 Do minimally
Strive to prevent issues, embed testability, review code carefully, use smart checklists, write minimally, regress intelligently.
#5 See better, cover more, test less
Continuously see and assess product from multiple views – USERS, ATTRIBUTES, ENVIRONMENT, CODE, ENTITIES
#6 Pause to speed up
Periodically pause and analyse to be sure that you are staying on the right track, reflect on outcomes to ensure you are doing it right and efficiently.
#7 View system from multiple angles
View the system from internal, external, regulatory/compliance, operations, maintenance and release like code structure, architecture, technology, terms of behaviour, end users, environment, usage, standards.
#8 Be sensitive and aware
Be sensitive and aware to issues you encounter and potential causes of issues, after all issues creep in due to untold expectation, accidental omission, quiet assumptions, incorrect implementation,inappropriate modifications,interesting side effects ,deliberate abuse , and innovative usage.
Sharpen your senses to smell better!
#9 Design for robustness
Don’t just test, design system robustly. Codein firewallsto be disaffected by inputs, configuration/settings, resources or dependent code.
#10 Design for testability
Hook in code to be able to inject inputs to stimulate, check status, create traces/logs to debug/check-for-correctness, even embed ‘self-test code’.
You may want to read a detailed version of these in these two articles FIVE thoughts on ‘Doing SmartQA’and FIVE *MORE* thoughts on ‘Doing SmartQA’.
Over the years there are a few things that I do consistently to solve problems technical or business.
Recently I read the book “The Checklist Manifesto” by Atul Gawande. “An essential primer on complexity in medicine” is what New York Times states about
Efficiency is a given now , high productivity aided by intelligent systems will become a norm, so what is our role? In this age of automated & continuous testing, efficiency gains are given and productivity is on the increase. In this era of AI systems, it is time we shift from productivity to creativity.
Siddhartha Mukherjee investigates the most perplexing cases of his career ultimately identifying three principles that govern modern medicine.
In an era where we are obsessed with productivity, it is not about doing more, of being busy that is deemed as high productivity.
Learning from failures .The inside story of how success really happens and how we cannot grow unless we learn from our mistakes.
With machines become more intelligent enabled by AI, it is time we focus on creativity to think differently and exploit machines for its intelligence.
Sketchnotes are purposeful doodling while listening to something interesting. Sketchnotes don’t require high drawing skills, but do require a skill to visually synthesize and summarize via shapes, connectors, and text. Sketchnotes are as much a method of note taking as they are a form of creative expression.
This article is a short primer on Blockchain outlining ‘What is blockchain technology’, ‘How does it work’ and ‘Where is it useful’. Curated from four articles which are nice and easy reads.
Sketchnotes are purposeful doodling while listening to something interesting. Sketchnotes don’t require high drawing skills, but do require a skill to visually synthesize and summarize via shapes, connectors, and text. Sketchnotes are as much a method of note taking as they are a form of creative expression.
“Healthy code is not the outcome of review or testing, it is from doing simple things diligently.” What is healthy and what are habits that we embrace to stay healthy? If we correlate this to code what does this mean, is what this pictorial article “Seven habits to healthy code” is about.
In this week’s SmartBits, Shivaji outlines”Key trends in automation“.
Healthy code is not about just working correctly. It is about future-proofing, maintainability, adaptability, reusability and so on. As in real life where face shines when you are in the pink of health, beautiful code also shines!
I have been a great fan of Dr Goldratt having read all this books, my favourite being his first book “The Goal”. This book “Necessary but not Sufficient” is written as a “business novel” and shows the fictional application of the Theory of Constraints to Enterprise resource planning (ERP) and operations software and organizations using that software.
Deep dive is about going deeper by going through available spec, by exploring it, and using information from past experiences to rapidly understand an entity. This is done rapidly with a sharp focus and a 360 vision in eight steps.
I have been a great fan of Dr Goldratt having read all this books, my favourite being his first book “The Goal”. This book “Necessary but not Sufficient” is written as a “business novel” and shows the fictional application of the Theory of Constraints to Enterprise resource planning (ERP) and operations software and organizations using that software.
Oh, in this week’s SmartBits, Srinivasan Desikan outlines “The evolution of dev” and what it means to testing.
T Ashok @ash_thiru on Twitter Summary Coverage, an indicator of test effectiveness is really multidimensional and has not been dealt with rigour most often(excepting for
I have been a great fan of Dr Goldratt having read all this books, my favourite being his first book “The Goal”. This book “Necessary but not Sufficient” is written as a “business novel” and shows the fictional application of the Theory of Constraints to Enterprise resource planning (ERP) and operations software and organizations using that software.
