You 'desktop' system is probably doing quote a bit of >=80bit processing especially if you running games (the fpu), what 64bit's gives you far more than bigger numbers, you should also get an architecture change, otherwise no-one would be bothering to develop 64bit systems, most markets that require that kind of pression are fairly well saturated.
In your example the only real problem with 16bit systems is memory addressing limit, so why didn't intel make a 16 bit processor with 32bit addressing registers? it's far easier than making a 32bit processor.
The idea is to build up the level of test data you have, You could have somthing that generats loads of test data , and use a simple script to check that it's data is ok, and even see what happens when bad data is fed in.
If someone one finds a bug, they generate test cases(and variants).
UAT testing should generate loads of data.
An live envoriemts give you loads of data for full-cycle developments.
Most of the 'worst' bugs i've come accross are down to bas systems design, before a single line of code is written. If a system is designed well then you should have far fewer bugs, even if you are using code monkies who don't know a quick sort from a n^2 bubble.
Design you systems well, know your people, Bill's good at that kind of thing and likes it(but crap at ui's say), Jess loves doing data imports, (may not be that quick, but always does them well). Fread always designes and produces good/fast systems cores.
Get your developers talking and sharing knowlage, 'I'm, having a bit of a problem' , or 'Who knows how to', are good things for people to be saying, so incorrage them to own up to the inadiquacies, and they won't have them for long.
If you can manage that then your productivity and bug counts should drop dramaticly, and the bugs you do have should be easier to fix.
Looks like you have a problem understanding emotional comment. Let's explain, First take the subject, Create a counter argument,(this can be counter to the subject, or counter to a releated subject). Now make that argument extream. Add in a bit of, over-the-top ness, just so people can see that you constructing an emotional comment.
The idea of an emotional comment is to prevoke though about the nature of the argument in the more intelegent, short sighted people can't look beond the extreamness which makes them easy to pick out.
Here's a translation of the post for you.
Most code that is produced is poor quality, why? Well if you comapre it to another disiplin that has reciently had poor quality defective products (e.g. World trade centre that was build in a rushed and wasn't as structurly sound as it should have been!)
Now most buildings have crap design, but we all live in them and put up with it, (why is that window there, who put the power socket at that end of the room.... etc....)
Point out that another disiplin, many people regard as highly professional, that has rule to go by dosn't do a job, that much better than most software designers.
Good design is always the best way to avoid buggy, hard to fix code. But for testing it depends what you testing, a good general test process for data processes (most functions can be though of as dataprocesses) is
Generate some input test data, Work out what the results should be by hand. this is your first stage regression.
Now run the input test data through the application/function
Diff the results against your hand generate file.
Any descrepancies should be resolved as, A bug in the application/function or A Bug in the hand generated files.
Fix all the hand-job problems
Repeat until you test files are perfect.
You now have a second stage regression test, Known good inputs, and known good outputs
Use the correct test files to fix the application bugs.
If a bug is found that isn't in you second stage regression, then generate test files for it.
Fix the bug in the application(using the test files).
Then run you second stage regression and check that any differences are down to the bug that was found (and been corrected).
Following this process you application should always get better, and a you should soon be able to build up a fairly large sample of test data.
The test harnis is simple enough (just a diff on the files and a bit of code to wrap up the functions.), to prevent artifacts caused by the testing process.
Any-how that's more-or-less what I do for most of my testing, bug fixing.
Well that's kinda the point, Software is more of a art/science disiplin and not an engenerian disiplin, There are two feasable ways of enginering software. 1: Have precise specifications, and take the type to perform all mathamatical analysys on the project. e.g. Space projects. 2: Re-write the whole thing, now you know what your doing.
1, isn't praticle for most things, You frequently don't know the requirements before you start and it would take forever to write word that way.
2, This is great for reverse enginering projects, but most companies need some return on investment, a Re-write/re-work would be thrown out [I usually re-work modules is a sneeky way, and make sure all the missing/assumed business requirements are resolved first]
And the third option,
Release somthing you know has bugs,
Have full regression tests for the software,
when a bug is found get a test case,
Fix the bug,
Check the test case,
Re-run all regression tests and check that any descrepancies were caused by the bug and are now fixed.
Re-build all regression tests. Repeat
Most companies I';ve workd for don't do 3 either, so you just get hack-ware
to design you a house, then when he was almost done, said that the walls must be made from foam. ....except the one on thats in the swamp.... ....and now that you've disigned one house, it shoudln't take you long to do a few more... ..and did i say there has to be a high speed rail link between them...It must travel faster than the speed of sound, but never hit any animals that happen to wander on to the track. ..and can you make that house bomb proof.... whys that house got walls made out of foam?
Evry other Gnutella client i've tried has been crap, the searhes turn up nothing, and you can never down-load. that was until I found lime wire, I think it runs on the gnutella network, but it dosn't perform like it does,
SFAIK, Sun are intending to use GNU tools for there Unix. because GNU is now more-or-less de-facto Unix standard.
Now all Sun need to do is change there name to UNG and everything will fit perfectly inplace. Now if HP were to use GNU then maybe there Unix wouldn't have buffer limits of cat etc.....
to design you a house, then when he was almost done, said that the walls must be made from foam. ....except the one on thats in the swamp.... ....and now that you've disigned one house, it shoudln't take you long to do a few more... ..and did i say there has to be a high speed rail link between them...It must travel faster than the speed of sound, but never hit any animals that happen to wander on to the track. ..and can you make that house bomb proof.... whys that house got walls made out of foam?
Here's my like 1[x 2] = 'aa....a' 2[1 3] = 'aa...b' 3[2 4] = 'aa...c' 4[3 5] = 'aa.....ba' etc... say eack node has a 10k string in it, you may need to search all 10000 nodes,
you'r not looking for the data pointer that matches, you looking for the data,so a log2(n) search is not only possible, but probably faster.
ftp.kde.org/pub/stable/mandrake/3.0.1/8.2/
on
Is RPM Doomed?
·
· Score: 2
I ended up getting most of my packages from there, but there's no kdevelop or koffice in the 3.0.1 directory for mandrake.
If there was a reasonable standard base I would have used a suse packege. Would have known that the packeges were at ftp://whereever,
And that still leaves the question open , why MYSQL?
IMHO RPM's need a MSCW rating system for deps. Must have glibc>34 Sould have.... Would like to update/install mysql as well.
Just got ADSL, Just had a nightmare with packages
on
Is RPM Doomed?
·
· Score: 3, Insightful
I aggree, I installed mandrake 8.2 a while ago, since then there have been a lot of 1.0 releases out. OpenOffice, Mozilla, KDE (3.0.1) etc.... But mandrakes packages have some rediculios deps, to install KDE 3.0.1 from there cooker(dev), it wanted me to update thinkgs like unixODBC and MYSQl,I don't wan't mySQL and call me stupid but obdc's a protocol!!! and i dont think the latest unixODBC changes that , why the hell have they put such non-granular pagkages togeter, if i had a release plan like that at work I'd probably be out of a job. The RPM tree locations in mandrake used to be different from the package defaults which ment i could'nt install wines RPM and know i wasn't going to screw up package management some time in the future.
Dependencies of RPM's really need sorting out, and there should be no reason why i can install a suse package on redhat (so long as they both follow LSB!!)
Ok this is why it's a good question given the following code
rteval f(x,.....){
f(x,......); }
all calling f(x) inside f(x) does is allocate some space on the stack, this stack space can be preallocated as an array, so that a loop can be used instead of a recursive function call..
Well not quite, The interview went somthing like this, Do you now what function of larlar does ralral., [quick scratch of the head, brain in top gear] Sorry I can't remember at the moment, I'm sure I'd find the answer in the help file under sys.io though.
Questions like, here is a recursive function, write the code to turn it into a loop.
Write some code to rotate/scale an image.
Fine an element in this sorted list (of say 10000)
Give this xxx write a class model for it.
Now as long as they don't expect perfect code, eg. forgeting to +1 because of a rounding error, or a binary search can result in a high or low result(for a non-perfect match), these seem fair enough questions to me because:-
They all test your abilty to write good code, not just code that works.
I know loads or 'programmers' who don't know how to turn a recursive function into a loop.
Would use sin/cos to rotate each point on the image, instead of using an interger line drawing algo to scan accross the image to rotate it (or even floating point)
Would write a n order search instead of a binary search.
And would use a poor or unflexable design pattern.
So long as they mark your programming skills and not how perfect your code is, i don't see a problem.
Debugging is also a key skill, but is very hard to test in an exam, a good debugger uses a hell of a lot of past experiance and insperation to locate, fix and check that there are no simila bugs.
SFAIK, evryone that evry wrote a JPEG decompressor based it on the example jpeg compressor on the JPEG site, the code was there, easy to use worked lovely like. This is the same code borland use for the jpeg filter in CBuilder and Delphi, The same code use by ACDSee The same code used by me, and probably the same code used by libJpeg on linux
I was talking about this to a friend a few months ago, the theory is that you can store a virus in the information block, or past the eng of a jpeg/gif or mpeg file,then modify the file to cause a buffer overrun in the decompression software and execute the virus.
Since a lot of software uses the same JPEG libraries a good infection rate should be achievable.
Regards,
Oliver Stieber.
without going against the license
on
Extensible IDEs?
·
· Score: 1
Yeh they used to have a 'use it loke a book' license, i noticed they'd changed it to.
Entry/pro level Borland products are reasonably prices in my opinoin (very entry level is free).
There Enterprise product are very 'Enterprise', and have a price to match, unfortuntly there pro products aren't pro enough (DB conictivy in Kylix-pro is crap!)
Well, the company has already licenced the use of there patent, under the terms of GPL. Companies either, Sit on patnets and sue, Sit on them an hold the market and sue, License the use of there patents (GPL in this case).
Or have 'open patents', e.g. a group of telcos all have patents in key ares, and to stop all the licensing/sueing problems they aggree to share there patents in an open way.
Slashdot Mirror
So no-one should be trying to find me?
I ment more along the lines of EDI, ESI, EDX
You 'desktop' system is probably doing quote a bit of >=80bit processing especially if you running games (the fpu),
what 64bit's gives you far more than bigger numbers, you should also get an architecture change, otherwise no-one would be bothering to develop 64bit systems, most markets that require that kind of pression are fairly well saturated.
In your example the only real problem with 16bit systems is memory addressing limit, so why didn't intel make a 16 bit processor with 32bit addressing registers? it's far easier than making a 32bit processor.
The idea is to build up the level of test data you have,
You could have somthing that generats loads of test data , and use a simple script to check that it's data is ok, and even see what happens when bad data is fed in.
If someone one finds a bug, they generate test cases(and variants).
UAT testing should generate loads of data.
An live envoriemts give you loads of data for full-cycle developments.
Most of the 'worst' bugs i've come accross are down to bas systems design, before a single line of code is written.
If a system is designed well then you should have far fewer bugs, even if you are using code monkies who don't know a quick sort from a n^2 bubble.
Design you systems well, know your people, Bill's good at that kind of thing and likes it(but crap at ui's say),
Jess loves doing data imports, (may not be that quick, but always does them well).
Fread always designes and produces good/fast systems cores.
Get your developers talking and sharing knowlage, 'I'm, having a bit of a problem' , or 'Who knows how to', are good things for people to be saying, so incorrage them to own up to the inadiquacies, and they won't have them for long.
If you can manage that then your productivity and bug counts should drop dramaticly, and the bugs you do have should be easier to fix.
Looks like you have a problem understanding emotional comment.
Let's explain,
First take the subject,
Create a counter argument,(this can be counter to the subject, or counter to a releated subject).
Now make that argument extream.
Add in a bit of, over-the-top ness, just so people can see that you constructing an emotional comment.
The idea of an emotional comment is to prevoke though about the nature of the argument in the more intelegent, short sighted people can't look beond the extreamness which makes them easy to pick out.
Here's a translation of the post for you.
Most code that is produced is poor quality, why?
Well if you comapre it to another disiplin that has reciently had poor quality defective products (e.g. World trade centre that was build in a rushed and wasn't as structurly sound as it should have been!)
Now most buildings have crap design, but we all live in them and put up with it, (why is that window there, who put the power socket at that end of the room.... etc....)
Point out that another disiplin, many people regard as highly professional, that has rule to go by dosn't do a job, that much better than most software designers.
Good design is always the best way to avoid buggy, hard to fix code.
But for testing it depends what you testing,
a good general test process for data processes (most functions can be though of as dataprocesses) is
Generate some input test data,
Work out what the results should be by hand.
this is your first stage regression.
Now run the input test data through the application/function
Diff the results against your hand generate file.
Any descrepancies should be resolved as,
A bug in the application/function
or
A Bug in the hand generated files.
Fix all the hand-job problems
Repeat until you test files are perfect.
You now have a second stage regression test,
Known good inputs, and known good outputs
Use the correct test files to fix the application bugs.
If a bug is found that isn't in you second stage regression, then generate test files for it.
Fix the bug in the application(using the test files).
Then run you second stage regression and check that any differences are down to the bug that was found (and been corrected).
Following this process you application should always get better, and a you should soon be able to build up a fairly large sample of test data.
The test harnis is simple enough (just a diff on the files and a bit of code to wrap up the functions.), to prevent artifacts caused by the testing process.
Any-how that's more-or-less what I do for most of my testing, bug fixing.
Nor can you patent a technique for appying for a parent that isn't on the books or in the process of being put on the books.
Well that's kinda the point, Software is more of a art/science disiplin and not an engenerian disiplin,
There are two feasable ways of enginering software.
1: Have precise specifications, and take the type to perform all mathamatical analysys on the project. e.g. Space projects.
2: Re-write the whole thing, now you know what your doing.
1, isn't praticle for most things, You frequently don't know the requirements before you start and it would take forever to write word that way.
2, This is great for reverse enginering projects, but most companies need some return on investment, a Re-write/re-work would be thrown out [I usually re-work modules is a sneeky way, and make sure all the missing/assumed business requirements are resolved first]
And the third option,
Release somthing you know has bugs,
Have full regression tests for the software,
when a bug is found get a test case,
Fix the bug,
Check the test case,
Re-run all regression tests and check that any descrepancies were caused by the bug and are now fixed.
Re-build all regression tests.
Repeat
Most companies I';ve workd for don't do 3 either, so you just get hack-ware
to design you a house,
then when he was almost done, said that the walls must be made from foam.
....except the one on thats in the swamp....
....and now that you've disigned one house, it shoudln't take you long to do a few more...
..and did i say there has to be a high speed rail link between them...It must travel faster than the speed of sound, but never hit any animals that happen to wander on to the track.
..and can you make that house bomb proof....
whys that house got walls made out of foam?
Evry other Gnutella client i've tried has been crap, the searhes turn up nothing, and you can never down-load. that was until I found lime wire, I think it runs on the gnutella network, but it dosn't perform like it does,
Well more two objectives inspired by greed, see there must be profit in there somewhere.
SFAIK,
Sun are intending to use GNU tools for there Unix.
because GNU is now more-or-less de-facto Unix standard.
Now all Sun need to do is change there name to UNG and everything will fit perfectly inplace.
Now if HP were to use GNU then maybe there Unix wouldn't have buffer limits of cat etc.....
Make the world a better,
Less gready,
More liberal place.
Step 3= Go to heaven ( or wil a nobel prize?)
to design you a house,
then when he was almost done, said that the walls must be made from foam.
....except the one on thats in the swamp....
....and now that you've disigned one house, it shoudln't take you long to do a few more...
..and did i say there has to be a high speed rail link between them...It must travel faster than the speed of sound, but never hit any animals that happen to wander on to the track.
..and can you make that house bomb proof....
whys that house got walls made out of foam?
Here's my like
1[x 2] = 'aa....a'
2[1 3] = 'aa...b'
3[2 4] = 'aa...c'
4[3 5] = 'aa.....ba'
etc...
say eack node has a 10k string in it,
you may need to search all 10000 nodes,
you'r not looking for the data pointer that matches, you looking for the data,so a log2(n) search is not only possible, but probably faster.
I ended up getting most of my packages from there, but there's no kdevelop or koffice in the 3.0.1 directory for mandrake.
If there was a reasonable standard base I would have used a suse packege.
Would have known that the packeges were at ftp://whereever,
And that still leaves the question open , why MYSQL?
IMHO RPM's need a MSCW rating system for deps.
Must have glibc>34
Sould have
Would like to update/install mysql as well.
I aggree,
I installed mandrake 8.2 a while ago, since then there have been a lot of 1.0 releases out.
OpenOffice,
Mozilla,
KDE (3.0.1)
etc....
But mandrakes packages have some rediculios deps, to install KDE 3.0.1 from there cooker(dev), it wanted me to update thinkgs like unixODBC and MYSQl,I don't wan't mySQL and call me stupid but obdc's a protocol!!! and i dont think the latest unixODBC changes that , why the hell have they put such non-granular pagkages togeter, if i had a release plan like that at work I'd probably be out of a job.
The RPM tree locations in mandrake used to be different from the package defaults which ment i could'nt install wines RPM and know i wasn't going to screw up package management some time in the future.
Dependencies of RPM's really need sorting out, and there should be no reason why i can install a suse package on redhat (so long as they both follow LSB!!)
grrrrrrrrrrrrrrrr
Ok this is why it's a good question
given the following code
rteval f(x,.....){
f(x,......);
}
all calling f(x) inside f(x) does is allocate some space on the stack, this stack space can be preallocated as an array, so that a loop can be used instead of a recursive function call..
Well not quite,
The interview went somthing like this,
Do you now what function of larlar does ralral.,
[quick scratch of the head, brain in top gear]
Sorry I can't remember at the moment, I'm sure I'd find the answer in the help file under sys.io though.
Questions like, here is a recursive function, write the code to turn it into a loop.
Write some code to rotate/scale an image.
Fine an element in this sorted list (of say 10000)
Give this xxx write a class model for it.
Now as long as they don't expect perfect code, eg. forgeting to +1 because of a rounding error, or a binary search can result in a high or low result(for a non-perfect match), these seem fair enough questions to me because:-
They all test your abilty to write good code, not just code that works.
I know loads or 'programmers' who don't know how to turn a recursive function into a loop.
Would use sin/cos to rotate each point on the image, instead of using an interger line drawing algo to scan accross the image to rotate it (or even floating point)
Would write a n order search instead of a binary search.
And would use a poor or unflexable design pattern.
So long as they mark your programming skills and not how perfect your code is, i don't see a problem.
Debugging is also a key skill, but is very hard to test in an exam, a good debugger uses a hell of a lot of past experiance and insperation to locate, fix and check that there are no simila bugs.
SFAIK, evryone that evry wrote a JPEG decompressor based it on the example jpeg compressor on the JPEG site, the code was there, easy to use worked lovely like.
This is the same code borland use for the jpeg filter in CBuilder and Delphi,
The same code use by ACDSee
The same code used by me,
and probably the same code used by libJpeg on linux
I was talking about this to a friend a few months ago, the theory is that you can store a virus in the information block, or past the eng of a jpeg/gif or mpeg file,then modify the file to cause a buffer overrun in the decompression software and execute the virus.
Since a lot of software uses the same JPEG libraries a good infection rate should be achievable.
Regards,
Oliver Stieber.
Yeh they used to have a 'use it loke a book' license, i noticed they'd changed it to.
Entry/pro level Borland products are reasonably prices in my opinoin (very entry level is free).
There Enterprise product are very 'Enterprise', and have a price to match, unfortuntly there pro products aren't pro enough (DB conictivy in Kylix-pro is crap!)
Well, the company has already licenced the use of there patent, under the terms of GPL.
Companies either,
Sit on patnets and sue,
Sit on them an hold the market and sue,
License the use of there patents (GPL in this case).
Or have 'open patents', e.g. a group of telcos all have patents in key ares, and to stop all the licensing/sueing problems they aggree to share there patents in an open way.