Winetricks is a multi-purpose tool for Wine that helps when Windows applications forget to bundle needed runtime libraries, fonts, tools, or plugins. It knows the safest place to legally get the missing files (often at microsoft.com), and will painlessly install them for you. It also can tweak Wine settings, and can automatically install about 100 applications and games, including any needed workarounds. It is a simple shell script, and does not require installation. If invoked with no arguments, it displays a simple GUI to let you pick exactly what you would like to install.
Changing news source / comments
Right click on the text area, then pick the "News Feed"
A few things I'd like to change:
1. I'd like to be able to select multiple news sources
and cycle thru them.
2. I'd like to disable the little dialog box that comes
up when it gets new data.
3. It should probably also let you tell it how often to
get new data, it's doing a lot of downloads now.
4. It should let you specify how fast it scrolls.
Time to get my hands dirty...
When I worked at a biggish game company, they used service
testing early on, and production testing towards the end.
The test team was told what parts of the game were ready
for test, but little else. There was no formal process.
It was quite expensive; it would have been much cheaper
if we had hired a couple more really good programmers and engaged
in better development practices (e.g. software inspections,
I agree that testing should start before code
is written -- even on a one-man project.
In my own work, I find that writing simple unit
tests for each class while (or before!) coding
each class is a big win; not only are my classes
better understood and less buggy, but much of the
debugging takes place in a nice, happy unit test
rather than a big messy application. I now use gnu
automake, and it generates a simple makefile
rule to run all my unit tests. This comes in handy
for regression testing.
For any multiuser system, writing a system-level load test
should be done long before the system goes to QA, and
used by the developer to find his own dang bugs.
The load test can then also be used by the test team.
In a way, I feel that developers themselves are directly responsible for the quality of the code received by the
consumer. Managers should NEVER tell a programmer
"Oh, don't worry about finding all the bugs; QA will do
that for you," becase the sad truth is, catching bugs in
QA is far more expensive and difficult than in development.