I work in the games industry, where most of the code I write ends up being UI code of some description (graphics, sound, etc.). This is also the area that ends up with the most bugs (it's easier for a tester to notice graphic glitches than to see poorly implemented AI).
With an extremely slim development team and timeline (we make GameBoy Advance games), it's difficult to justify unit tests, and usually comes down to the gall of the programmers on the project.
Of course, a crash bug that's very difficult to reproduce never helps in short timelines:P
Most of the flamebait gets moderated down anyway so users can choose to ignore it.
And anyway... Why should/. only be open to Linux users? I'm using Microsoft at work mostly because all the development software we need is released for it. Therefore most of my time is using Microsoft software.
I'm still reading/. because it's informative, up to date and generally/not/ biased towards any OS. There's flames, but you end up with flames no matter where you go...
PoorMan solution - Two computers. One sends mail. The other one encrypts files. Encrypted files are always copied by floppy in one direction - to the sender.
But if a target is suspected by the FBI, you would hope that they would be clever enough to watch for backdoors, shield their machines from EMF, etc.
We often play DVDs from our PS2 at work. One thing we noticed was that the movies sound and visuals slowly desynchronise as you watch the movie. The further you are in to the movie, the worse it gets.
Yes that's true, but I also wouldn't like someone breaking into my house to see if there is a fire.
Re:This has been mentioned before, but...
on
Why not Ruby?
·
· Score: 1
I agree.
Parse Trees are a lot easier to visualise in a LISP type syntax, even if you're using C to code the trees for speed.
Also, when I'm making a game for an imbedded system, I write in assembly for the routines that need to be quick, but still keep all the code in an object oriented type structure to make things easier to expand.
You couldn't fit the information you can fit in a pocket PC into your pocket though. I have to many phone numbers to fit them into my mobile, so instead I've got them all with me when I have my iPaq.
I often have to have a lot of technical documents with me. A lot of these documents are a lot easier to have in my hand while I'm trying to integrate them into whatever I'm doing. I have enough paper information lying all over my desk that sometimes it's just easier to search by document on my PocketPC.
Add E-books, it's always good to have something to do with me for times I'm waiting for a train/bus, etc.
A lot of the pad and paper work I do is code related, so it's a lot easier to have a diagram / pseudo-code on a memchip then on a pad of paper, so that I can alter and change it later. I now only do quick scribblings that I know will not be needed again, less trees wasted.
And I've got my MP3s to listen to on the way home thrown into the bargain:)
Add Australia to that ^_^ Of course Oakenfold is commercial trance, so you've got the same thing as Eminem...
:)
If you'd said Astral Projection or a similar group I would have completely agreed
Besides the visual reasons for wanting vinyl, vinyl has a very warm (said phat) sound, whereas CDs play a very "clinical" sound.
And a DJ mixing some tracks together on vinyl is going to beat someone mixing CDs any day IMHO.
I work in the games industry, where most of the code I write ends up being UI code of some description (graphics, sound, etc.). This is also the area that ends up with the most bugs (it's easier for a tester to notice graphic glitches than to see poorly implemented AI).
:P
With an extremely slim development team and timeline (we make GameBoy Advance games), it's difficult to justify unit tests, and usually comes down to the gall of the programmers on the project.
Of course, a crash bug that's very difficult to reproduce never helps in short timelines
What we need now is a competition to find the smallest illegal prime...
:-)
Hopefully one day an already established constant can become illegal for also being a decoder, etc. that'd be great
Most of the flamebait gets moderated down anyway so users can choose to ignore it.
/. only be open to Linux users? I'm using Microsoft at work mostly because all the development software we need is released for it. Therefore most of my time is using Microsoft software.
/. because it's informative, up to date and generally /not/ biased towards any OS. There's flames, but you end up with flames no matter where you go...
And anyway... Why should
I'm still reading
PoorMan solution - Two computers. One sends mail. The other one encrypts files. Encrypted files are always copied by floppy in one direction - to the sender.
But if a target is suspected by the FBI, you would hope that they would be clever enough to watch for backdoors, shield their machines from EMF, etc.
We often play DVDs from our PS2 at work. One thing we noticed was that the movies sound and visuals slowly desynchronise as you watch the movie. The further you are in to the movie, the worse it gets.
But I've run Unreal on a machine that doesn't have 3d hardware and it ran fine with all the effects.
I know that speed is an issue in games, but I'd rather have the choice between slow and good-looking or fast and featureless.
Yes that's true, but I also wouldn't like someone breaking into my house to see if there is a fire.
I agree. Parse Trees are a lot easier to visualise in a LISP type syntax, even if you're using C to code the trees for speed. Also, when I'm making a game for an imbedded system, I write in assembly for the routines that need to be quick, but still keep all the code in an object oriented type structure to make things easier to expand.
You couldn't fit the information you can fit in a pocket PC into your pocket though. I have to many phone numbers to fit them into my mobile, so instead I've got them all with me when I have my iPaq. I often have to have a lot of technical documents with me. A lot of these documents are a lot easier to have in my hand while I'm trying to integrate them into whatever I'm doing. I have enough paper information lying all over my desk that sometimes it's just easier to search by document on my PocketPC. Add E-books, it's always good to have something to do with me for times I'm waiting for a train/bus, etc. A lot of the pad and paper work I do is code related, so it's a lot easier to have a diagram / pseudo-code on a memchip then on a pad of paper, so that I can alter and change it later. I now only do quick scribblings that I know will not be needed again, less trees wasted. And I've got my MP3s to listen to on the way home thrown into the bargain :)