Sachin Natu

Explorer, Vipassana Student

[Sachin Natu @natusachin]

Joining information for Anapana for Children
Event : 6.00 PM India Time (+5.30 GMT)
Joining Link: https://t.co/CBK0gJxiUC...
Event Password: 1234

[Sachin Natu @natusachin]

Introduction to Anapana Meditation for Children

Joining information for Anapana for Children
Event : 6.00 PM India Time (+5.30 GMT)
Joining Link: https://t.co/CBK0gJxiUC...
Event Password: 1234

[Sachin Natu @natusachin]

@MadhuriDixit 18 August

[Michael Bolton @developsense.bsky.social @michaelbolton]

We all encounter bugs like this every day. Why? Well, I have a theory: many testers are in some form of single focus–on test cases, test scripts, APIs, given/when/then... Many of those forms drive testers away from something really important: interacting with the damned product.

[Jessica Kerr @jessitron]

When we rush development, skip tests and refactoring, we get “Escalating Risk.” Please give up the “technical debt” description; it gives businesspeople a very wrong impression of the tradeoffs.
From @Janellekz #deliverAgile

[Michael Bolton @developsense.bsky.social @michaelbolton]

Check out Rapid Software Testing (https://t.co/8ZW8ELHSeG) for yourself (https://t.co/HPzcTNBZPv) to find out why you want to register for RST Explored (https://t.co/V7VpiNkIZP) in Zurich, May 15-17 (https://t.co/fE4IEKf3RS). And please tell friends!

[Michael Bolton @developsense.bsky.social @michaelbolton]

As part of the process of relaunching @jamesmarcusbach’s Web site (https://t.co/N1n129gOjp), we’ve also revised https://t.co/pNTOhPtpFz. That includes some new writing on why we test, and what we mean by “Rapid”. https://t.co/8ZW8ELHSeG

[Agile Connection @agileconn]

In this interview, @michaelbolton discusses the absurdity of #projectmanagers requiring #testers to sign off on a product. Testers cannot assure the quality of the product, so Bolton makes suggestions for how to handle this request https://t.co/rJSuWL5V02

[Michael Bolton @developsense.bsky.social @michaelbolton]

As Harry Collins notes in /Tacit and Explicit Knowledge/, no one paid much attention to tacit knowledge until long after knowledge became explicit. Similarly, few noticed ET until @DrCemKaner named it and with others (prominently @jamesmarcusbach) contrasted it with scripting.

[Michael Larsen @mkltesthead]

Looking out for coding bad habits can help testers too :). new TESTHEAD: Write it on Your Hand: a #30DaysOfTesting Testability #t9y ... https://t.co/38AmgfZOtC

[Michael Bolton @developsense.bsky.social @michaelbolton]

"No user would ever do that." Pretty much every tester has heard someone say it at some point. How do you reply? From the Vault, here are some ideas. https://t.co/VBcwfnP9eZ

[Michael Bolton @developsense.bsky.social @michaelbolton]

The product probably *can* work, and your testing can probably show that fairly easily.

If your testing isn't oriented towards finding out how the product *isn’t* working, or *might not* work, then your testing isn’t working.

[Michael Bolton @developsense.bsky.social @michaelbolton]

4) Good strategy for deep testing includes variation and diversification. Beware of obsessive focus or compulsive repetition. Revisit parts of the product when risk is high and/or when you haven’t looked at them lately. Explore around to reveal unanticipated risk.

[Michael Bolton @developsense.bsky.social @michaelbolton]

3) This does not mean you must repeat your deep testing all the time, on every build, prompted by every change to the product. But do consider some deep testing focused on some important elements of coverage or risk now, and on other elements next time. Revisit them occasionally.

[Michael Bolton @developsense.bsky.social @michaelbolton]

2) This does not mean that fast, cheap, shallow, repeated tests—and checks—aren’t valuable. They often are. But by definition, they aren’t targeted towards rare, subtle, hidden, intermittent, emergent bugs. To find those (before your customers do), you’ll need deeper testing.

[Michael Bolton @developsense.bsky.social @michaelbolton]

1) There’s a common misconception about testing: that whatever we’ve tested, we must always test it again, every time, and forever. This misconception creates a bias in favour of fast, cheap, shallow, repeated tests. Yet variation is essential to broader and deeper coverage.

[Michael Bolton @developsense.bsky.social @michaelbolton]

When managers tell you to automate all the testing, try telling them you can’t do it, because they’ve just told you the machines are supposed to be doing that.

[nasscom deeptech @nasscomdeeptech]

When it comes to #SaaS you need to see at this quadrant.
@sureshsambandam, CEO - @KiSSFLOW, Founder - @OrangeScape at #NPC2018

[nasscom deeptech @nasscomdeeptech]

How can we make India a Global #SaaS hub? Chennai alone cannot do it. We need to bring all the ecosystems together to make India a Global #SaaS hub. @sureshsambandam, CEO - @KiSSFLOW, Founder - @OrangeScape at #NPC2018

[Shekhar Kirani @skirani]

It was a great spur of the moment interview (@chandrarsrikant style). The trust b/w founder and investor takes effort to build, but, when it is aligned to get the best out of each other for the company, magic happens. A proud day for me to be standing next to @mrgirish