Instead of actually knowing what you are doing, you write a bunch of tests and then mindlessly assume all your code is correct when your tests pass, not knowing full well that you might’ve coded your tests wrong in the first place. What will you do then? Suggest that tests be written for the tests?

So instead of wasting time writing tests to claim that I have “80% code coverage”, how about training software engineers to actually think, code, test, and clean up after themselves. Now all we have instead is a bunch of banshees telling me how to do my job and waste my time writing tests so they can layoff the QA department.

One downside of this technique is that such an image will produce a displeasing flickering effect when dragged over itself. You can try it out yourself in firefox: Load the page, then drag the image somewhere.
So when using this, you should at least disable drag & drop for the elements involved.

Not only is TDD a waste of the client’s time and money, it is a waste of the developer’s time as well.

The software testing religion is silly. This idea that you should spend countless hours writing tests so you can boldly refactor all your code safe in the knowledge that you will never introduce a single bug due to your awesome tests violates every theory of computer science there is.

For one, refactoring the code often means refactoring the tests due to changes in the API or architecture. Changing the test when you change your code is equivalent to having no test at all. Read that again if you don’t understand.

Secondly, due to the halting problem, it is impossible to write tests that will find every single possible bug. If you think otherwise, then you should submit a scientific paper with your findings because you will receive the Nobel Prize and have the distinction of proving the likes of Turing and Djikstra wrong. More likely, unit tests exist solely to give you a false sense of security about your code.

Thirdly, when the project nears completion and you fix a lot of small bugs, you will often find you spend as much time maintaining the unit tests as you do the code! You just don’t have time to do that anymore. More likely, the deadline will force you to throw out all the unit tests because they aren’t adding any value and are slowing you down too much. In which case, you’d have been better off not wasting the time writing them in the first place!

And yes, unit tests can have bugs in them. Why do people assume that developers can write test code that is completely 100% bug free whilst assuming that those same develepers are incompetent enough to include the sort of bugs that unit tests will find in the main code?

It just doesn’t make sense.

In very specific circumstances, such as writing complex scientific or mathematical code, tests make sense ONLY for the purposes of regression testing. It is a complete waste of time in every other circumstance.

Good software development is efficient. Clients expect value for money, and if they knew their developers were squandering thousands of hours of their time writing things which add no value whatsoever they would probably sue.

There’s a good reason the market favours developer groups who don’t waste their time writing tests. They do the job more efficiently.

Also I wasn’t even aware it even had a internal mic.
I bought a headset for use with skype years ago, one that folds in on itself so it can be easily stuffed into a side pocket of my carrying bag.
Also the front head/mic sockets are mighty handy as a side note.

ericd@vaiopro:~$ cat /proc/acpi/button/lid/LID0/state
state: closed

To get the internal mic working (i.e. for Skype), I had to add a line to /etc/modprobe.d/alsa-base.conf:

options snd-hda-intel model=toshiba-s06

Cheers,

Eric

But yes, the laptop has a annoying high pitch hum. Interestingly enough, i don’t think it is a fan problem. I think it might be a condensator.

The sound only appears when the laptop is plugged into power (which is almost always because it won’t last very long without power, a few hours tops)
Also, if you sit directly in front of the laptop you probably won’t hear the sound. At least that is my experience.

I hope this helps.

could you please say something about its noice? How is the fan?

I had another look at your algorithm, and came up with changes to my own. The speed I calculated from my own ratio is very subjective though.

Check it out in my comments on my blog article

http://andytson.com/blog/2010/05/travelling-elephpant-solutions/comment-page-1/#comment-31