If I were writing a video player for a porn site I would have it buffer the last X% of the film before buffering the start. Isn't that the part the viewers care about?
(I was going to make a joke about it being the climax of the film but actually, when you think about it, makes sense to program it that way so it's a serious comment)
Using your post as an example: Let's see here... you could be charged with - a criminal death threat - possession with intent (if you own a rifle) - conspiracy to commit murder (since you discussed with all of us and presumably none of us called the police) - making a terrorist threat - material support for terrorism (if you donate to a charity the DA doesn't like) - and a whole bunch of "minor" crimes.
So... have fun in prison... we'll see you in 150 years or so.
This started out as a "+1 funny"... but now I just feel "-1 WTH is happening to your country?":-(
Each overlay shows where the eight year old child was allowed to cover unsupervised. Sad how much more constricted and hemmed in each generation of that family has become over the last century.
Once I put Rockbox (!) on it, I can play flac, ogg, avi.
Last time I checked, you also couldn't connect with usb, charge, or dock the sansa with rockbox installed. You had to do something like "power cycle while holding left arrow, then wait 30 sec, then power off, then connect the usb cable"... that got you back to the normal firmware so you could transfer songs and charge the thing.
So I didn't upgrade to rockbox. The benefit wasn't worth the hassle.
Maybe the new version's fixed that... if so I'll give it a try on my e260
* High def videos of their kid's birthday parties? * Installing Windows $Name Ultimate Extreme we_promise_this_is_really_the_best_version 2010? * porn? * Lots of extra "can't skip past it" advertising at the start of movies? * Extra space for all that next generation DRM? * Half Life 4?
simple and easy to maintain would be win-win for everyone.
Except for the mechanics that fix the complicated engines, the companies that make and sell the replacement parts the mechanics use, all the people that work in the distribution systems for those parts, all of their suppliers, etc. *shrug*
Never attribute to malice that which can be adequately explained by stupidity. -- Hanlon's razor
I've worked with Marketing people before and can easily believe that they had no clue about the infrastructure requirements and possible fail points. Actually, even if they did, they wouldn't have asked a techie. They would have asked the techie's manager who probably told them "don't worry about it.
Business as usual in a big, dysfunctional, corporate environment.
crap, I meant to click "Continue editing" instead of "Submit":-(
That should read "Original music in the style of popular artists and/or genres"
Also, Slashcode shouldn't force a cooldown period when you want to immediately reply to your own pst.... at least, not for the first response. Grrr.....
Strangely enough. I still enjoy his parodies long after the original song has dropped out of sight. Let's remember too that only about half of his work is parody. The other half is 100% his own work.
Wow, that guy forgot the first rule of Fight Club. err... "Acquisition Club"
On the other hand: he told the AUDITOR the step-by-step instructions for equipment theft... and he still got away with it? That's some serious mojo. (yes, I know the boss was pointy-haired... but still)
* Learn how to use your company's version control system.. and *use* it
* Comment your code and be smart about it. That is... Keep the signal/noise ratio of your commenting as high as possible. Comment the big picture and a description of what tricky bits of code are supposed to be doing (and why). Not commenting trivial things.
* Avoid putting tricky bits in your code:-)
* Never assume that some code you write is temporary. Lots of mission-critical systems started off as a "temporary" project.
* Always try to write the best code you can, even if it's just a little one-off (see above point)
So, that means making sure your function names, variables, etc all have intelligent names. Each block of code does one thing. Each block of code is small (try to keep it on a single printed page, including all whitespace and comments)
Avoid using global variables, gotos, tightly coupled code, code that messes with the internals of objects/data-structures, etc.
* Set up a little svn server on your workstation for all those little snippets of test code you write. You never know when you're going to want to go back and look at that stuff again.
* Read other people's code. Try to figure out if it does what it's supposed to do.
* Get a good IDE and learn how to use it really well. Use the same one as the majority of your dev team (unless it really sucks).
* Make yourself as FAST as possible. If you're really fast/efficient then you have more time to think and solve problems: - Learn how to type. seriously. get a typing tutor program and do 30 minutes a day until you can touch type as fast as you can speak.
- Learn the hot-key combos for your programming environment. You won't believe how much faster you'll be.
- Stop using your mouse for common tasks.
- Use code templates everywhere you can get away with it. Every time you start a new file, every time you write a new function
- Learn the idioms of whatever language they have you using. You should never have to stop and think about common constructs in your code
* Keep a spellbook. If you learn anything cool, interesting, or elegant. WRITE IT DOWN. By HAND I know it sounds stupid, but it really helps
* Learn how to accurately estimate your time. For everything you're asked to do. Write down how long you think it will take (in hours). At the end of the task, or the end of the workday, track how much time you've currently put in, and how much more you think you'll need. (Never modify your original estimate). Then, when people start asking you to estimate how long a project will take you'll have some historical data to help you come up with a realistic number.
Pro tip... when you're starting out. Multiply all your estimates by 3. Newbies are usually way too optimistic
* Read. lots Read books on the language your company expects you to learn. Try to also read general books on programming, design, project management, etc. Try to understand the big picture of your project as well as the nitty-gritty of the part you're working on.
Some good books to get you started - Code Complete - Pragmatic Programmer: from journeyman to Master - Programming Pearls - Joel on Software book - Mythical man month - Getting Things Done
* At the end of each project, keep a log of what the project was called, what it was for, who it was for, and what you did to contribute. You can also jot down what language you used, what gotchas sprung on you, your estimate accuracy ratio, etc.
I suspect you're trolling but I'll bite. There's nothing stopping wikipedia from trying to verify that the takedown notice is legit *before* removing the info.
"We received your request to takedown [list of pages] that you allege fall under your copyright.
We comply with all valid DMCA notices. Before we comply, you must provide proof, in writing, that demonstrates both A) That this material is copyrighted B) That you are the copyright holder.
We need that information to combat frivolous and questionable takedown notices. Please provide the above information by [date 30 days in the future] to avoid the legal action we take against persons who send us baseless threats
Slashdot Mirror
If I were writing a video player for a porn site I would have it buffer the last X% of the film before buffering the start. Isn't that the part the viewers care about?
(I was going to make a joke about it being the climax of the film but actually, when you think about it, makes sense to program it that way so it's a serious comment)
Prostitution is legal in most of Europe as well as Canada.
Please back that up with some documentation.
Why is it illegal to charge for an activity that's legal to give away for free?
-- George Carlin (paraphrased)
bwa ha ha.... my Coffee-B-Gone works!
Once again we prove that the best way to "report" a security flaw is to tell a bunch of script kiddies about it.
Then you don't have to outrun the law... you just have to outrun the script kiddies.
Using your post as an example:
Let's see here... you could be charged with
- a criminal death threat
- possession with intent (if you own a rifle)
- conspiracy to commit murder (since you discussed with all of us and presumably none of us called the police)
- making a terrorist threat
- material support for terrorism (if you donate to a charity the DA doesn't like)
- and a whole bunch of "minor" crimes.
So... have fun in prison... we'll see you in 150 years or so.
This started out as a "+1 funny"... but now I just feel "-1 WTH is happening to your country?" :-(
The next time I grab a 15-year-old girl to rape and kill her ...
I'm all for freedom of speech, but could we exercise a little self-control over what we say and publish?
Oh the irony....
Yet challenging an idea confers no harm on others.
It certainly harms those in political power in the sense that it makes it harder for them to stay in power.
Do they have OCR systems capable of reading the truly crappy handwriting that people use these days?
That reminds me this wonderful little map of Sheffield, Britain, with "allowed to roam" overlays: http://img.dailymail.co.uk/i/pix/2007/06_02/playgraphicDM1406_736x800.jpg
Each overlay shows where the eight year old child was allowed to cover unsupervised. Sad how much more constricted and hemmed in each generation of that family has become over the last century.
Hmm... looks like the problems still exist http://www.rockbox.org/twiki/bin/view/Main/SansaFAQ
Though they're not as bad as I remembered them being. Maybe it's worth giving it a try after all.
Once I put Rockbox (!) on it, I can play flac, ogg, avi.
Last time I checked, you also couldn't connect with usb, charge, or dock the sansa with rockbox installed. You had to do something like "power cycle while holding left arrow, then wait 30 sec, then power off, then connect the usb cable" ... that got you back to the normal firmware so you could transfer songs and charge the thing.
So I didn't upgrade to rockbox. The benefit wasn't worth the hassle.
Maybe the new version's fixed that... if so I'll give it a try on my e260
So, a Dwarf Asteroid then?
* High def videos of their kid's birthday parties?
* Installing Windows $Name Ultimate Extreme we_promise_this_is_really_the_best_version 2010?
* porn?
* Lots of extra "can't skip past it" advertising at the start of movies?
* Extra space for all that next generation DRM?
* Half Life 4?
simple and easy to maintain would be win-win for everyone.
Except for the mechanics that fix the complicated engines, the companies that make and sell the replacement parts the mechanics use, all the people that work in the distribution systems for those parts, all of their suppliers, etc. *shrug*
They also need their management team to stop stabbing each other in the back :-(
Can you provide a link to that report? I'd like to read it.
Never attribute to malice that which can be adequately explained by stupidity.
-- Hanlon's razor
I've worked with Marketing people before and can easily believe that they had no clue about the infrastructure requirements and possible fail points. Actually, even if they did, they wouldn't have asked a techie. They would have asked the techie's manager who probably told them "don't worry about it.
Business as usual in a big, dysfunctional, corporate environment.
They want to be sure the advertisements and trailers are up to date.
crap, I meant to click "Continue editing" instead of "Submit" :-(
That should read "Original music in the style of popular artists and/or genres"
Also, Slashcode shouldn't force a cooldown period when you want to immediately reply to your own pst.... at least, not for the first response. Grrr.....
He has four categories of music:
You can see the whole list here: http://en.wikipedia.org/wiki/List_of_songs_by_%22Weird_Al%22_Yankovic
Strangely enough. I still enjoy his parodies long after the original song has dropped out of sight. Let's remember too that only about half of his work is parody. The other half is 100% his own work.
Wow, that guy forgot the first rule of Fight Club. err... "Acquisition Club"
On the other hand: he told the AUDITOR the step-by-step instructions for equipment theft... and he still got away with it? That's some serious mojo. (yes, I know the boss was pointy-haired... but still)
Here are a few tips off the top of my head.
* Learn how to use your company's version control system.. and *use* it
* Comment your code and be smart about it.
That is... Keep the signal/noise ratio of your commenting as high as possible.
Comment the big picture and a description of what tricky bits of code are supposed to be doing (and why). Not commenting trivial things.
* Avoid putting tricky bits in your code :-)
* Never assume that some code you write is temporary. Lots of mission-critical systems started off as a "temporary" project.
* Always try to write the best code you can, even if it's just a little one-off (see above point)
So, that means making sure your function names, variables, etc all have intelligent names. Each block of code does one thing. Each block of code is small (try to keep it on a single printed page, including all whitespace and comments)
Avoid using global variables, gotos, tightly coupled code, code that messes with the internals of objects/data-structures, etc.
* Set up a little svn server on your workstation for all those little snippets of test code you write. You never know when you're going to want to go back and look at that stuff again.
* Read other people's code. Try to figure out if it does what it's supposed to do.
* Get a good IDE and learn how to use it really well. Use the same one as the majority of your dev team (unless it really sucks).
* Make yourself as FAST as possible. If you're really fast/efficient then you have more time to think and solve problems:
- Learn how to type. seriously. get a typing tutor program and do 30 minutes a day until you can touch type as fast as you can speak.
- Learn the hot-key combos for your programming environment. You won't believe how much faster you'll be.
- Stop using your mouse for common tasks.
- Use code templates everywhere you can get away with it. Every time you start a new file, every time you write a new function
- Learn the idioms of whatever language they have you using. You should never have to stop and think about common constructs in your code
* Keep a spellbook. If you learn anything cool, interesting, or elegant. WRITE IT DOWN. By HAND I know it sounds stupid, but it really helps
* Learn how to accurately estimate your time. For everything you're asked to do. Write down how long you think it will take (in hours). At the end of the task, or the end of the workday, track how much time you've currently put in, and how much more you think you'll need. (Never modify your original estimate). Then, when people start asking you to estimate how long a project will take you'll have some historical data to help you come up with a realistic number.
Pro tip... when you're starting out. Multiply all your estimates by 3. Newbies are usually way too optimistic
* Read. lots
Read books on the language your company expects you to learn. Try to also read general books on programming, design, project management, etc. Try to understand the big picture of your project as well as the nitty-gritty of the part you're working on.
Some good books to get you started
- Code Complete
- Pragmatic Programmer: from journeyman to Master
- Programming Pearls
- Joel on Software book
- Mythical man month
- Getting Things Done
* At the end of each project, keep a log of what the project was called, what it was for, who it was for, and what you did to contribute. You can also jot down what language you used, what gotchas sprung on you, your estimate accuracy ratio, etc.
I suspect you're trolling but I'll bite. There's nothing stopping wikipedia from trying to verify that the takedown notice is legit *before* removing the info.
"We received your request to takedown [list of pages] that you allege fall under your copyright.
We comply with all valid DMCA notices. Before we comply, you must provide proof, in writing, that demonstrates both
A) That this material is copyrighted
B) That you are the copyright holder.
We need that information to combat frivolous and questionable takedown notices. Please provide the above information by [date 30 days in the future] to avoid the legal action we take against persons who send us baseless threats
Thank you very much
[Name here]"