In this week’s SmartBites, Yuvaraj Thanikachalam outlines as to what Blockchain is, why this is considered a revolutionary technology, what businesses could benefit from this and the challenges to adopting this in the video “Blockchain – the technology“.
In the beEnriched section is a short primer on Blockchain outlining ‘What is blockchain technology’, ‘How does it work’ and ‘Where is it useful’. Checkout the article “Blockchain – What, How & Where“.
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.
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 to rapidly understand an entity is this week’s beEnriched section article. What is Deep dive? It is about going deeper, by reading available spec, by exploring, and using information from past experiences to understand an entity. This is done rapidly with a sharp focus and a 360 vision in eight steps.
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.
The sufficiency of test cases has always been an interesting challenge.The cliched notion of code coverage is sadly insufficient, being an unidimensional measure. “The smart coverage framework” outlines a refreshingly simple picture as a smart coverage framework.
In this edition of SmartBites are four snippets of brilliant advice from Sudhir, Zulfikar, Girish & Jawahar – “Have extreme ownership mindset”, “Focus on the big picture”, “Build with quality, not test after” and “Understand operating conditions & implementation to test well” as SmartAdvice #1.
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.
What does it take to do SmartQA? Smart Thinking, Smart Understanding, Smart Design, Smart Plan, SmartQA Test Organisation and Smart Planning. A pictorial article on this is what this week’s beEnriched article “7 Pictures to Doing SmartQA” is.
In this week’s SmartBites “Lean thinking & Agility“, Tathagat Varma outlines how Agile inspired by lean thinking is accomplishing agility in SW development.
Isn’t it amazing that earth just goes about the job quietly, of revolving around the sun a whopping distance of 940 million kms every year? A joy it is to pause and ponder the amazing cosmic wonder, and celebrate as it commences another revolution around the sun. On this happy occasion of a new beginning, enjoy the poem that I wrote titled “Bless us all”.
A mashup of three articles published as part of SmartQA digest over the last few months that outlines mindsets needed to brilliant code, tips to produce clean code and habits to speed up evaluation
Great code occurs due to a brilliant confluence of clean code mindset, good heuristics/tips and healthy software engineering habits. This week’s beEnriched section article 10 mindsets, 10 tips & 10 habits to clean code connects these using articles that were published earlier.
It is not a great working solution, it is not brilliant technology that makes deployment of an enterprise solution successful, it is ‘operationalising’ that is key to success says Zulfikar in the smartbits video “Operationalising is key“.
Oh, this week’s SmartBites is “10 Thoughts” on Agile mindset, metrics, AI, good vs bad code, “what is technical after all” and others from ten wonderful practitioners.
Hope you have checked out the new SmartQA web site at smartqa.community? Guess you have noticed that all prior digests are also available here !
A mashup of three articles published as part of SmartQA digest over the last few months that outlines mindsets needed to brilliant code, tips to produce clean code and habits to speed up evaluation
Prevention occurs due to good understanding. Detection occurs due to good understanding. Understanding of what is needed, what is stated and what is implemented. The beEnriched section article outlines two tools for doing this – “TWO tools to aid smart understanding“.
Testability impacts deliverability. When it’s easier for testers to locate issues, it gets debugged more quickly, application gets to the user faster and without hidden glitches Listen to the short video “Design for testability” from Girish Elchuri in this week’s smartbits.
T Ashok @ash_thiru Summary Doing SmartQA is about great mental clarity of visualising what is intended, what is present, what-may-be-missing that could-be added to enhance
I had an interesting discussion with an engineering director of a product company on the subject – “dedicated QA or non-dedicated QA”. He was keen on a strong development QA as part of engineering team with an additional dedicated(small) QA team, and was seeking opinions. That triggered the thought for this interesting article “Role of dedicated QA in the new age dev” in the beEnriched section.
Simplification is hard, and can drive innovation. Listen to the 3-minute video “Simplify, Innovation happens” from Raja Nagendra Kumar in this week’s smartbits.
Did you check out the new SmartQA site smartqa.community All the prior digests are also available now here !
beEnriched
Role of dedicated QA in the new age dev
In current times with rapid dev driven by Agile, with testing done by dev folks, is there a need for dedicated QA? What is dedicated QA really? What should be the value adding dedicated QA be in the new age dev? Read more
What does it take to do SmartQA? Thoughtful pause, multidimensional thinking, sensitivity and awareness and designing for robustness/testability. A short crisp article continuing from the prior article outlining five more thoughts on what it takes to do SmartQA. Doing SmartQA is about visualising the act in one’s mind and taking steps to being robust and enabling rapid easy validation, outlined in this crisp article FIVE *more* thoughts on ‘Doing SmartQA’ in the expandMind section.
In this edition of SmartBites, listen to two great pieces of advice from Vivek and Shivaji on ‘reinvent yourself’ and ‘staying in sync’ in today’s rapid dev as “Smart Advice #2“. In the nanoLearning section Jawahar Sabapathy helps us understand containerisation & microservices and its role in today’s architecture.
This article outlines twenty approaches to smart test design based on seven views of user, logic/analysis, construction, test, experience, operational and evolution.
What does it take to do SmartQA? Thoughtful pause, multidimensional thinking, sensitivity and awareness and designing for robustness/testability. A short crisp article continuing from the prior article outlining five more thoughts on what it takes to do SmartQA. Doing SmartQA is about visualising the act in one’s mind and taking steps to being robust and enabling rapid easy validation, outlined in this crisp article FIVE *more* thoughts on ‘Doing SmartQA’ in the expandMind section.
In this edition of SmartBites, listen to two great pieces of advice from Vivek and Shivaji on ‘reinvent yourself’ and ‘staying in sync’ in today’s rapid dev as “Smart Advice #2“. In the nanoLearning section Jawahar Sabapathy helps us understand containerisation & microservices and its role in today’s architecture.
What does it take to do SmartQA? Thoughtful pause, multidimensional thinking, sensitivity and awareness and designing for robustness & testability. A short crisp article continuing from the prior article outlining FIVE MORE thoughts, on what it takes to do SmartQA.