leibnizwasright

It does not say if requires potable water or how much of it would be necessary for big batteries. But I imagine potable water would serve for optimal reactions.

Even though this uses Hydrogen, which means small quantity of water, water still a finite resource, it becomes costly every year, specially the one that's drinkable. This seems like a double sword, solving one side, while it makes other worse.

I have the understanding from experience that people will always give a reason for doing something that I could not imagine.

So 1st, make questions, understand what is the objective with that code you see on screen. 2nd, make more questions too see if other use cases were considered.

3rd, there are best practices, literature that provide a common way of working, discuss how to apply this.

There are no ways of understanding without making questions.

On this specific case, besides the lack of OO design knowledge, there were also a misunderstand on the page object pattern , how web apps are build and what is the web app and what is part of the browser.

And this is why I also talk with my team on my ideas to develop something before or while developing it. It should not be a surprise, no matter how nice and commented the code is.

I think that 1st we have to understand that to solve this, every solution is slow. 1st I send some links on OO designs and SOLID principles. 2nd I made a few comments on the code review that tacked more real problem like maintenance, change of URL since we were still in development phase and other pages and dialogs that do not have a URL and how this mixed with the rest that have. 3rd was to have design discussion pior development - which we did not have. For last, some hours during week with the whole team to talk on design and coding, in order to have evryone on a similar level of knowledge.

I agree with you, it is important to let the person fail and learn. But sometimes, this can be costly and fixing it may be hard.

My approach is to ask the person question and understand what is the objective trying to be achieved, and hope with the answers given, the person realize it is doing a mistake.

I also hope that the person respect my experience and is able to learn from my mistakes and do not need to do the same mistakes in order to learn.

But I do not always succeeds in these endeavors. Once a colleague was developing some page objects for Selenium tests and creating classes with only one attribute, which was the full URL of the page. Of course tests would not word when executed in several environments and to have this files were useless. But to fix exactly this, I saw it required more knowledge on OO design than a simple talk could give.

I agree with you, and there is several companies already doing this for whole slides. In addition, people should also understand that more than 1 slide is necessary for a high quality analysis of the cancer. From the top of my head, I remember Definiens (http://definiens.com) that develops software that does whole slide analysis and HalioDX (http://www.haliodx.com/) that does the same and use it as auxiliary for colon cancer treatment.

I also used not to care, because I used to think that "I don't put that much information on it". But it always said data, but not which data, now I know it buys data from other to cross it, don't know which data they buy and don't know what kind of information they are able to get when they do this. This is what we are only now understanding that they are doing and what is possible to do with this. And of course, Facebook say the least minimum necessary to keep profiting with no problems. Hence I don't see how we can expect people to really know what Facebook does.

This won't be the last time they try.

From the bugs described in the article, specially the one a person could withdrawal from another account to its own account, I believe better test libraries could help. Normally people develop tests using the same input data from beginning to end of test execution, since it becomes cumbersome to use different test data for input in the same round of test execution. Mainly because how these data come from fixtures.

In addition to all you said, I would add that some more advanced test frameworks/library a missing. There are only good ones for unit tests and UI test automation like Selenium, for integration tests there is a huge gap of decent test frameworks missing.

Yes, I don't see this a problem, normally releases get delayed, if you get more time to develop better, then why not? I always saw testers talking with product owners and managers about one or other developer that was slower but had delivered less defect.

In many companies I worked that were like this, other developers also wanted to fix these problems. So, talking with them is also a good start I would say, if you get get one more colleague to work kind of right from beginning is a nice start too. Normally, QAs and test automation engineers will be all for improve the situation. Being a bit more vocal on these problems, but it is important to choose what should be the 1st problem to be tackled.