"We try to solve the problem by rushing through the design process so that enough time is left at the end of the project to uncover the errors that were made because we rushed through the design process."
Coding mantra at my university (as in, I heard it from more than a few teachers) is that you should never have your includes in header files.
Gosh, that's incredibly dumb. I've worked on projects with hundreds of header files - I'm supposed to remember which files I need to include first?
Header files should be modular - the best way to do this is to #include the.h file as the first line of the.c/.cpp file - that way if your header file is not modular, your implementation code won't even compile.
Over-commented code (the kind where there's 2-3 lines of comments for every one line of code -- not every closing brace needs a reminder that we're exiting a code block, thanks!) is pretty awful too.
That may be true, but when I think back over my programming career to date, and think about the problems I've had with code, I can assure you that "There were just too many comments!" doesn't come up all that often:-).
I do feel sorry for a little sorry for those who cannot get one, but I also write it off as them not trying hard enough. With a little effort, it wasn't hard to get a Wii back in Oct. [snip] If you called every day, you'd have gotten one in a week.
Er, that just raises the bar for how difficult it is to get them. It won't magically make there be more Wiis manufactured and be available to buy. So there will still be the same number of people who can't get one.
don't mention that IE is the non-standard one. Let the client get excited about your good design and good price. When they figure out that it needs to be broken to work round IE, they will already be engaged.
Wow. Sucks to be your customers.
Reminds me of the story Steve McConnell told about going to a software development conference: One of the key speakers was asked a question about schedules, and told people to underestimate on schedules/cost. His logic was that then the project would get greenlit, and then you could deal with the fallout later - but at least you get to do the project. (McConnell was not impressed, in case you are wondering.)
Given my experience of coding a facebook app, you have to guess at so much information because it's so poorly documented (esp. the security/authentication stuff) that this is extremely likely.
Ah yes, you're right there. I've got a few months old MacBook which is pretty nippy for most things, but Flash tends to hit the CPU hard, for reasons I can't work out. It could well be Safari, as Safari on my PC often maxes out one core when playing some flash.
I believe Flash on Win32 has hooks into the graphics hardware that lets it get away with that.
I presume you mean it's allowed to use hardware blitting (what else would video codecs use? I know some gfx cores have codec chips but they're pretty specific, and I doubt they're directly exposed to a browser plugin - could be wrong). I would have thought that blitting would be nicely abstracted by the OS - it's 2007 after all.
For one, their video codec doesn't suck up 100% CPU to DECODE a 320x240 video on a decently powerful machine.
What do you describe as a decently powerful machine? Admittedly I just upgraded my PC, so I have a new Core 2 Duo (6750 I think) which is pretty damn fast, but I'm playing a youtube video here via Flash (natch) and the Windows task manager is showing the CPU usage as alternating between 1% and 0%.
Hmm, odd...I bought my sister an iPod Shuffle, and put some music on it via my PC to christen it. When she got home and intalled iTunes, iTunes would either offer to delete all the music and then sync with her iPod, or do nothing. If she didn't agree to delete all the music, the device didn't show up in iTunes, so she couldn't put any music on it.
Maybe that behaviour is specific to the Shuffle or something.
You honestly think that having seen a cop steal a donut doesn't prove that they could?
No, and nowhere did I say that.
Your problem is obviously that you're equating a counter example with "That's possible, but not necessarily true." It isn't.
No, I'm not. You are. The original point was "That's possible, but not necessarily true.", and offered some anecdotal evidence of why the person believed it. The second poster seemed to think they refuted the claim with their anecdotal evidence. They didn't. They just showed that some stores behave differently to others.
My store doesn't do that and I'm sure other don't either isn't just "not necessarily true" in light of the brother who does exactly that, it's false. Not likely to happen? Well it clearly does.
I don't mean to be rude, but you really need to differentiate between the two claims "Unlikely" and "Never happens".
Let me state it again:
I believe it unlikely that a cop would steal from a donut shop. If you see a cop stealing from a donut shop, that does not mean you have refuted that it is unlikely.
Let's try another:
The Hoopoe is a rare bird (in the UK). I consider it very unlikely that you will see one. If you do, that does not mean that I was wrong. It could just mean you experienced an unlikely event.
Seriously, what is hard to understand about this?
With purely anecdotal evidence, you have no way of asserting or disproving the likelihood of something. You might say my claims are unfounded - that's possible, but they certainly haven't been refuted.
You know, I can't believe I'm arguing this. It's like the Land that Logic Forgot.
Er, you need more than "That's possible, but not necessarily true." in order to claim that someone is putting forward the case for a universal positive.
Unless my understanding of English is broken, of course.
That's why I said what I did. The original guy said "That isn't likely to happen", and the other guy said "Here's an example of where it did!"
That's like me saying that it's unlikely that a cop would steal from a donut shop, and someone saying "Oh yeah? Well I know this cop that did!"
Amazon Germany will no longer ship Wiis to the UK - they stopped last week, I believe. I just checked on amazon.de to confirm. I suspect amazon.fr will be the same story.
I also like how they avoid mentioning that you could just crack uxtheme.dll yourself, which is what FlyAKiteOS does, and theme to your heart's content, instead opting to plug WindowBlinds, which is again inferior due to sluggishness.
Yeah that sounds easy. Out of interest, are you serious?
Slashdot Mirror
Sounds pukka!
So your claim to writing plenty of 100% bug free code is dependent on your ability to redefine the term 'bug' as you see fit?
Hmm...
-- Glenford Myers
Or as the saying goes:
"I'll start coding - you find out what they want."Gosh, that's incredibly dumb. I've worked on projects with hundreds of header files - I'm supposed to remember which files I need to include first?
Header files should be modular - the best way to do this is to #include the .h file as the first line of the .c/.cpp file - that way if your header file is not modular, your implementation code won't even compile.
That may be true, but when I think back over my programming career to date, and think about the problems I've had with code, I can assure you that "There were just too many comments!" doesn't come up all that often :-).
My post was a troll?!
Are the moderators on crack?
Ah, I've always wanted to say that :-)
Fixed that up for ya.
Er, that just raises the bar for how difficult it is to get them. It won't magically make there be more Wiis manufactured and be available to buy. So there will still be the same number of people who can't get one.
I know I do, but then I've read Influence: The Psychology of Persuasion by Robert Cialdini, so I'm even more aware of when I'm being played.
Reading that book changes the way you deal with people like that - you tick off the strategies in your head as they use them...
"Oh, there we go, 'Enforced Scarcity'...check! I wonder which one is next..."
It's a great book btw - even tells you how to make sure someone helps you if you have a heart attack :-)
Wow. Sucks to be your customers.
Reminds me of the story Steve McConnell told about going to a software development conference: One of the key speakers was asked a question about schedules, and told people to underestimate on schedules/cost. His logic was that then the project would get greenlit, and then you could deal with the fallout later - but at least you get to do the project. (McConnell was not impressed, in case you are wondering.)
Given my experience of coding a facebook app, you have to guess at so much information because it's so poorly documented (esp. the security/authentication stuff) that this is extremely likely.
No, Americans would call it Doug Adams. After all, that's what they always seemed to call the man, no matter how much he hated it.
It was his favourite, too.
Ah yes, you're right there. I've got a few months old MacBook which is pretty nippy for most things, but Flash tends to hit the CPU hard, for reasons I can't work out. It could well be Safari, as Safari on my PC often maxes out one core when playing some flash.
I believe Flash on Win32 has hooks into the graphics hardware that lets it get away with that.I presume you mean it's allowed to use hardware blitting (what else would video codecs use? I know some gfx cores have codec chips but they're pretty specific, and I doubt they're directly exposed to a browser plugin - could be wrong). I would have thought that blitting would be nicely abstracted by the OS - it's 2007 after all.
Still, with software, anything's possible :-)
What do you describe as a decently powerful machine? Admittedly I just upgraded my PC, so I have a new Core 2 Duo (6750 I think) which is pretty damn fast, but I'm playing a youtube video here via Flash (natch) and the Windows task manager is showing the CPU usage as alternating between 1% and 0%.
I'm actually quite impressed by that :-)
LAKE MONSTER!!!
:-)
I wonder if those two rooms are connected via a corridor, making an 'H' shaped building.
Hmm, odd...I bought my sister an iPod Shuffle, and put some music on it via my PC to christen it. When she got home and intalled iTunes, iTunes would either offer to delete all the music and then sync with her iPod, or do nothing. If she didn't agree to delete all the music, the device didn't show up in iTunes, so she couldn't put any music on it.
Maybe that behaviour is specific to the Shuffle or something.
If the UI is anything like that website, I may have stumbled on the answer.
No, and nowhere did I say that.
Your problem is obviously that you're equating a counter example with "That's possible, but not necessarily true." It isn't.No, I'm not. You are. The original point was "That's possible, but not necessarily true.", and offered some anecdotal evidence of why the person believed it. The second poster seemed to think they refuted the claim with their anecdotal evidence. They didn't. They just showed that some stores behave differently to others.
My store doesn't do that and I'm sure other don't either isn't just "not necessarily true" in light of the brother who does exactly that, it's false. Not likely to happen? Well it clearly does.I don't mean to be rude, but you really need to differentiate between the two claims "Unlikely" and "Never happens".
Let me state it again:
I believe it unlikely that a cop would steal from a donut shop. If you see a cop stealing from a donut shop, that does not mean you have refuted that it is unlikely.
Let's try another:
The Hoopoe is a rare bird (in the UK). I consider it very unlikely that you will see one. If you do, that does not mean that I was wrong. It could just mean you experienced an unlikely event.
Seriously, what is hard to understand about this?
With purely anecdotal evidence, you have no way of asserting or disproving the likelihood of something. You might say my claims are unfounded - that's possible, but they certainly haven't been refuted.
You know, I can't believe I'm arguing this. It's like the Land that Logic Forgot.
Er, you need more than "That's possible, but not necessarily true." in order to claim that someone is putting forward the case for a universal positive.
Unless my understanding of English is broken, of course.
That's why I said what I did. The original guy said "That isn't likely to happen", and the other guy said "Here's an example of where it did!"
That's like me saying that it's unlikely that a cop would steal from a donut shop, and someone saying "Oh yeah? Well I know this cop that did!"
So what? Nothing is refuted in either case.
Amazon Germany will no longer ship Wiis to the UK - they stopped last week, I believe. I just checked on amazon.de to confirm. I suspect amazon.fr will be the same story.
You're right! Your anecdotal evidence totally trumps that other guy's anecdotal evidence!
Go you!
Yeah that sounds easy. Out of interest, are you serious?