Software bugs can lead not only to material losses, but also can damage human's health. For example, actors on the stage of a theatre can get injured if suddenly one of the scenery begins to go down on the stage at the wrong time. However, the connection between the errors in code and the health damage of medical software is more obvious. Let's talk about this topic.
This article focuses on the teams of developers who create the programs for a medical equipment. I hope they will not stay indifferent and will check their code. Let's recall two famous cases where errors in programs, related to medicine, became the reason for bad news.
Firstly, it is a series of tragic events caused by the errors in the Therac-25 device of radiation therapy. This device has caused at least six overdoses of radiation within the period from June 1985 to January 1987, some patients received doses of tens of thousands of rad. At least two people died directly from the radiation overdoses. Software bugs of the device were the reason of the tragedies and the main problem was the incorrect security strategy.
One of the most important factors affecting the speed of development and the success of the project launch is the correct decomposition of the product manager idea into tasks for programming directly. How to do it right? Take the script of the new feature from the product and immediately start coding? First, write the acceptance tests, and then code that will provide their passing? And, maybe, shift everything to the shoulders of developers - and let them decide during the spam poker themselves?
Let's think about it and identify the problems that can arise in the process of separation of tasks, and the ways to solve them. In this post, we will discuss the basic principles of decomposition of tasks when working in a team. My name is Ilya Ageyev, I'm the head of QA in Badoo. Today I'll tell you how workflow affects decomposition, how different are testing and laying out tasks that arise as a result of decomposition, and what rules should be followed to ensure that the development process goes smoothly for all participants.
After I had worked for years in small web agencies, I decided to try something new and got a job in a rather big (3500 employees) IT-company 5 months ago. What I have seen at my new working place, turned out to be far from my expectations. At numerous requests of my friends, I want to share some observations about the differences between big and small IT-companies. As it is known, tastes differ. This article is not the ultimate truth; this is what I have faced and what was important for me.
Many people believe that software testing is the search for the bugs. Sometimes, I say to testers, "Do not try to find as many errors as possible, try to miss as less as possible!” and they do not understand me. What's the difference?
There is a huge difference! In this article I want to tell you about that difference, and what tools you need to use for a useful troubleshooting.
What is troubleshooting?
What if someone copies your brilliant business idea?
About twenty people asked this question on Answers OnStartups:
When I meet with an investor, he may ask me: What if a big company copies your idea and develops the same website as you did?
How can I answer this question?
No, the question is: What are you doing now, knowing that a big company will copy your idea?
No, wait, the real question is: What are you going to do when another smart and quick startup will copy it and gets $10 million financing?