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?
Most people know about the difference between Firefox and Internet Explorer in the Internet industry. We also know what FTW is and what the difference is between ASP, PHP and RoR. At least we know what the difference is.
If you meet a businessman who has not ever heard about Digg, Google Apps or the Freemium, you'll be very surprised. Is not it right?
Now a lot of people write about what would happen if a web-developer decides to become a freelancer. Also, they write about some challenges that the freelancer may encounter, namely, they are hunting for new orders at first, then dealing with the influx of work, and finally overcoming own laziness. However, I still have not seen any article about what would happen if the freelancer decides to stop freelancing work that consists of the orders, prepayments, hunt for new customers, and so on.
Do I have the right to write such an article, perhaps you will decide, but I have an excuse to say that after about a year or more working as the web-developer, I started working as the freelancer on the vast web-market and was working there nearly two and a half years.
I am sick of these topical articles on how to improve performance, motivation, and other nonsense. Why do people write them? To help those who are confused about yourself or for those who cannot concentrate. I do not think so.
The modern life dictates that everything should be done quickly, in order to achieve maximum efficiency. Certainly, you need to be very successful. You need to move to the goal every day, every hour, and every minute. Leaving all the unnecessary things behind and throwing all efforts to achieve a result. Otherwise there is no point in living.
Life is a piece of crap. At least, most people think in that way with whom I had an occasion to talk. They constantly have been complaining about their work, broken relationships, and children who do not want to become as their parents want to see them. The life for these people is an endless carousel of frustrations, anxieties and unfulfilled hopes. They get up early in the morning with a headache, and then they have a couple of cups of coffee and go to work in the zombie mood. They hate their jobs and feel that their wok is meaningless and useless. But, despite this, they continue with the tenacity of lemmings do their job, day after day, year after year. They have their own way through life, hoping that they will have a good life after they retire. Well, it's all garbage. When you are fifty, you are so tired of this life that your only wish will be to lie down and die. Also, your health will not be that good anymore, because you have spent it, doing nonsense. So, when you retire, you do not go to Africa to hunt lions, because the sun is bad for your pressure. You also do not go to the North Pole, because you have arthritis and cold will not be the best cure for it. South Pole will not be good either, because you dislike penguins, which is not surprising, as you worked for 30 years as a system administrator. So what do you do? You get a nice trip to the country house and have the cozy TV company in the evening, that's what you get. After living 30 years in a constant battle with yourself, you simply will not have extra energy to get your ass off the couch.
Today, I am going to talk about how you can hide the “spare" assembler commands in the regular code. This method is useful for complexity of disassembling the code, especially if the generation of "hidden" commands to automate. Tools: debugger - OllyDbg.
How great and wonderful is the world of information technology! Every week I read all kinds of the news that out there is one billion of Web pages that each group of kindergarten has its own website and we run out of IP addresses! Free iPads are given out to the students and all African children have $ 100 laptops. In general, this information is overwhelming! Thanks to Wikipedia we will not look like a fool on the forums and the social networks.
Today we can work and have fun online. Internet allowed a young boy from Siberian village to work on the Large Hadron Collider, and thousands of talented people have opened their gifts thanks to YouTube. Is not it great?
This article opens a series of articles, in case, if it will be found interesting, because the first rule of public speaking says: tell people that, what they are interested in!
If you have never experienced public speaking or are afraid to do it – here is “under the cut”. If you consider yourself an experienced speaker, the second article of this series will be for you.
Today’s article is going to be more dedicated to the speech, and less to its contents. If the future comments show, that the composition of the speech needs to be explained (the problem statement -> the solution -> the selection process -> the chosen solution -> the result), or the basics of public speaking (avoid using “hum and haw”, junk words and finishing phrases with non-normative interjections) – I’ll do it next time.
In 1974, Kodak purchased the small nuclear reactor, which was placed in an underground bunker in the industrial complex of Kodak Park in Rochester, New York. A neutron flux multiplier was used for the experiments in the neutron photography that lasted until 2007.
The neutron source was a californium-252, the flow multipliers were plates with uranium, and the highly enriched uranium was accumulated as the waste in the laboratory. According to the experts, it was a unique device for the U.S. industrial sector. There are about 50 such multipliers with californium in the world, and almost all of them are in Russia. Kodak the only company that had this multiplier in USA.