I would like to share some observations and my knowledge in this article with umumble readers.
Let’s do it!
1. Write as you say it aloud
Your task is to show other programmers that you do it with a little twist.
Before you write the next piece of code, think and say it out loud what you are going to do. For example, I need to clear little bit this item. Many people will write without any hesitation:
Perhaps, this article may not present any new or fresh ideas, besides, I'm sure you have often read something like this somewhere else. This post even does not claim the fact to be true. Its content is the fruit of my own experience, mistakes, and the knowledge that I have gotten from my colleagues. I'm sure that many people will be able to find themselves in my article. Probably, the first stage is not very typical for the programmers who are not involved in the Olympic programming, but the following stages do not independent from this factor at all.
A few days ago, the earliest Half-Life 2 version was released in the network for the media. Obviously, this version has not been finished yet, as the main game’s character is not known to the whole world of players a theorist physicist, who wears glasses and a protective suit and holds in his hand a crowbar, but bearded dwarf Ivan, a space biker, who is opposing against the staff of the research center. 15 years ago, the disk contents was reserved exclusively for members of the regular publishers.
This morning I found a letter in my mail:
In fact, this letter does not have any files attached, it just has 6 links (View, Download...), and they lead to the same address: http://184.108.40.206/~ru1/account.googlemail.com/viewer/13083e7f5f2c0890&
First I got to fake Google Docs with the message "document cannot be displayed", and then I was redirected to fake Google Account, where I was asked to enter a password. I guess for my own safety :). After I entered “screw you”, I got to the third fake page of docs with a list of some components.
This article is not a panacea for all security lacks, and it does not reveal any new attack vectors. I just saw a serious implementation of the fake for Google mail and decided to warn all UMumble users.
Recently, I have received an interesting letter, supposedly to confirm / cancel automatic forwarding to my mailbox.
Have you ever wonder what are different letters / numbers mean in the titles of video files?
I have taken all the information from Google and I hope this cheat sheet will be useful for somebody.
CAMRip (CAM, deriving from camera)
Sometimes, it is mistakenly labeled as Screen (SCR). Video and audio are recorded on camera in a movie theatre. At times the shaken image can be taken at an angle to the screen, and in some movies could be seen heads of moviegoers, etc. The sound quality might be different such as laughing audience. Usually, it is the worst and the very first quality of movie, which could be found after the official release.
Hello, UMumble users!
Recently, Dr. Web’s researchers have discovered a botnet of more than 550 thousands infected Mac’s machines. Probably, you may say "it is started all over again”. Presently, more than 670 thousands the infected computers were found around the world (see map):
Once again, we will try to debunk the myth about the platform impregnability and to help some people to understand this process.
The picture shows a fragment of perfect cheat sheet that has the basic electronic components, including their appearance and the symbol on the schematic circuits.
Many people probably know that the latest stable version of Firefox got its own web inspector. Its release was a matter of time, it is potentially very interesting, but now it's not specifically about it. In the 11th version of the browser this inspector will receive an interesting upgrade 3D DOM Inspector. This mode previously could be seen by installing Tilt 3D add-ons. In brief, this thing can visualize the components of the website and view them from different angles, it looks like this:
I have recently gotten a web application from a nasty contractor who claimed to be a good expert in programming. Unfortunately, we believed him. Functional of the web application seemed to work okay at first glance. However, once the client started using application in the real conditions the things went bad. The contractor has gone after a payment, and I have gotten his errors to fix for a client.
I decided to document a few errors that I found along the way. These are errors that every good programmer should already know to avoid… but obviously some people need to be reminded about them.