Don't forget that William Adama had no dreams of Earth and wanting to save the remnants of humanity until he had a near death experience with a Dyson Sphere and a ration of Soylent Green....
>>Nice troll, but dyslexia is a neurological disorder that affects reading, not writing.
My understanding, as a dyslexic, is that the brain gets confused and/or mangles symbols - meaning letters. This can be manifested on the way in (reading) or on the way out (writing). In my case specifically, I have the writing / typing problem... and i also suffer from disgraphia.. where I tend to convolute numbers and formulas.
So take the access away but leave the laptops. What's going to stop someone from playing Solitaire or Tetris locally... or looking at a local cache of..images... ?
Myself, I'd be writing my comp sci projects in some lame lib arts mandated classes... but that's just me....
My guess is that Jimi just didn't get around to interpreting classical or other forms... Prog and Fusion rock of that type were just solidifying at the time he died (bands like Yes, ELP, and Floyd).
I think Jimi would have matured as a player and taken that stuff on, and taken the genre in a different direction than it is today, post Randy Rhodes.
Yes I know/. is a tech forum... but I like talking about music as much as I do C code.:)
As cool as this tech is.. Imagine hearing how Hendrix would approach covering the likes of Zeppelin, Rush, or hell even Stanley Jordan?
But what seems like a bad deal to me is the concept of extending copyright to 'style'. Does this mean that eventually any talented kid who manages to figure out (AKA, reverse engineer) Clapton's or Lifeson's style and sound perfectly, would be in violation of a copyright?
So much for paying homage to your inspirations....
... just do it in software. Meaning, code up a drive interface in C/C++... make it look like system calls to a physical drive, but behind the scenes said code would just write to a big pre-allocated 'drive file' sitting in your comp's filesystem.
I'm sure there's a bunch of ways to implement this, and problems to solve for sure. But it's probably less effort then overriding the error correction, etc, of modern HD's.
It's kind of cool when you know multiple languages / technologies.
I started off as a COBOL guy, and eventually taught myself c/c++, Java, and Perl.
I found that being multi-lingual was OK. -The right tool for the job, you know? But it got to the point where I was writing in COBOL and started to think in C, and just really brought some new ideas into how to structure and write a COBOL program. Got creative with arrays of tables, etc.
And the same thing the other way around... I started thinking in COBOL sometimes when writing C programs in distributed environments... which I guess led to better program structure, and more verbose code that I'd seen in examples..especially around string/data handling. Of course C/C++ give you a LOT more options than COBOL does... but there's also something to be said for simplicity when it makes sense, and lots of self descriptive code...
Anyone can learn a language - but it's really something when your experience from one place starts to kick in elsewhere..usually when you don't expect it to.
Like anything else, there's no right answer. It's not black and white.
My default is to never leave my guys alone if I can help it, and/or it makes sense. If it's a minor complexity or criticality problem, I'll just leave the guy and trust him to do his job. I try to build trust on my team - and let the developers own their stuff. I always hated being micromanaged, and I don't do it to my guys.
But if it's a high visibility problem, with significant financial or operational risk, then we're all in it together.
Depending on how the problem unfolds, I might be able to help with the debugging, or to coordinate different efforts that my guys have going on. I also find that it's my job to gather information that can help in the fixes, or in the workaround. The business/users needs to be managed, status needs to be communicated, phone calls need ot be made to get other support people on line, or grease the wheels / pre-cache work in order to help speed the implementation once the code is fixed. There's a lot to do, to keep the pressure off the team and to help them so they only have to worry about doing their job.
At the same time, if it's a long term (meaning more than a couple hours) fix, then the logical thing is to break the team into shifts. So that when the current guys are wiped out, the second team can pick up the work.
For the big problems, I find myself going onto team 2, which is usually the 'morning shift'. My thinking being that in the early morning the business and my senior management comes in and wants to know what's going on. I need to be fresh for that - and also, if the problem isn't fixed, I need to be able to speak to what went wrong, as well as help where I can with contingency, etc.
Bottom line - don't be a primadonna as a manager. Help where you can - coordinate, give ideas, be a sounding board, stop bad ideas that go down the wrong path, manage the users, buy pizza, etc. And make sure that when you do go home, make sure that the team trusts YOU. They need to know that you're leaving for good reason...not just because you want to go home.
>>If you start a small firework rocket, you can't predict how far up it will fly and when exactly it will blow up in a shiny and entertaining explosion. But you know the limits of that rocket, e.g. it won't fly up more than 200 feet, the light of the explosion won't last longer than 10 seconds and it won't get hotter than 150 degrees celsius in the center of the explosion (numbers completely made up by me).
>>The scientists know that the black hole and anything else that may come from LHC won't destroy the world.
Let us not forget though that every now and then one of those little bottle rockets goes astray and ends up exploding in someone's personal space. Eyes get lost, etc.
So even though we know that said rocket can only go 200 ft up, and can only burn at 150 C, when it does misbehave it usually ends up causing some amount of trouble.
Slashdot Mirror
that is my only question.
And all we get is a stinkin 3 second sound byte? What the hay??
I was expecting some grand thing..along the lines of "the sounds of the planets". Come on, at least make this sun thing at least 60 seconds long.
What's there - well I could have whipped that up myself in sound forge or gnural....
This is exactly what they want us to think.....
I've been dying to ask this question for years... why not just resurrect the trusty old Saturn and then build on it?
Or was that path considered and tossed out?
You forgot to mention Google Chrome's Simon Says knockoff icon...
Don't forget that William Adama had no dreams of Earth and wanting to save the remnants of humanity until he had a near death experience with a Dyson Sphere and a ration of Soylent Green....
Too bad you ended up getting the points as an AC. Bummer.
I disagree. I'd rather have Han's blaster than any era trek phaser.
And the Cylons were born. It was the Cylons, right?
>>Nice troll, but dyslexia is a neurological disorder that affects reading, not writing.
My understanding, as a dyslexic, is that the brain gets confused and/or mangles symbols - meaning letters. This can be manifested on the way in (reading) or on the way out (writing). In my case specifically, I have the writing / typing problem... and i also suffer from disgraphia.. where I tend to convolute numbers and formulas.
So take the access away but leave the laptops. What's going to stop someone from playing Solitaire or Tetris locally... or looking at a local cache of ..images... ?
Myself, I'd be writing my comp sci projects in some lame lib arts mandated classes... but that's just me....
$_ and the like aren't obscure enough, so I think that Larry and the boys are planning space variables for Perl 6. :P
My guess is that Jimi just didn't get around to interpreting classical or other forms... Prog and Fusion rock of that type were just solidifying at the time he died (bands like Yes, ELP, and Floyd).
I think Jimi would have matured as a player and taken that stuff on, and taken the genre in a different direction than it is today, post Randy Rhodes.
Yes I know /. is a tech forum... but I like talking about music as much as I do C code. :)
The concept and the technology itself have great promise.. no doubt. But once the lawyers get onto this train, things are going to get complicated.
Hendrix covering Vai. What a sweet thought that is... :)
As cool as this tech is.. Imagine hearing how Hendrix would approach covering the likes of Zeppelin, Rush, or hell even Stanley Jordan?
But what seems like a bad deal to me is the concept of extending copyright to 'style'. Does this mean that eventually any talented kid who manages to figure out (AKA, reverse engineer) Clapton's or Lifeson's style and sound perfectly, would be in violation of a copyright?
So much for paying homage to your inspirations....
... just do it in software. Meaning, code up a drive interface in C/C++ ... make it look like system calls to a physical drive, but behind the scenes said code would just write to a big pre-allocated 'drive file' sitting in your comp's filesystem.
I'm sure there's a bunch of ways to implement this, and problems to solve for sure. But it's probably less effort then overriding the error correction, etc, of modern HD's.
Instructions.
How, exactly?
It's kind of cool when you know multiple languages / technologies.
I started off as a COBOL guy, and eventually taught myself c/c++, Java, and Perl.
I found that being multi-lingual was OK. -The right tool for the job, you know? But it got to the point where I was writing in COBOL and started to think in C, and just really brought some new ideas into how to structure and write a COBOL program. Got creative with arrays of tables, etc.
And the same thing the other way around... I started thinking in COBOL sometimes when writing C programs in distributed environments... which I guess led to better program structure, and more verbose code that I'd seen in examples..especially around string/data handling. Of course C/C++ give you a LOT more options than COBOL does... but there's also something to be said for simplicity when it makes sense, and lots of self descriptive code...
Anyone can learn a language - but it's really something when your experience from one place starts to kick in elsewhere..usually when you don't expect it to.
Aunt Beru, can't I please have a Bantha for Life Day?
Like anything else, there's no right answer. It's not black and white.
My default is to never leave my guys alone if I can help it, and/or it makes sense. If it's a minor complexity or criticality problem, I'll just leave the guy and trust him to do his job. I try to build trust on my team - and let the developers own their stuff. I always hated being micromanaged, and I don't do it to my guys.
But if it's a high visibility problem, with significant financial or operational risk, then we're all in it together.
Depending on how the problem unfolds, I might be able to help with the debugging, or to coordinate different efforts that my guys have going on. I also find that it's my job to gather information that can help in the fixes, or in the workaround. The business/users needs to be managed, status needs to be communicated, phone calls need ot be made to get other support people on line, or grease the wheels / pre-cache work in order to help speed the implementation once the code is fixed. There's a lot to do, to keep the pressure off the team and to help them so they only have to worry about doing their job.
At the same time, if it's a long term (meaning more than a couple hours) fix, then the logical thing is to break the team into shifts. So that when the current guys are wiped out, the second team can pick up the work.
For the big problems, I find myself going onto team 2, which is usually the 'morning shift'. My thinking being that in the early morning the business and my senior management comes in and wants to know what's going on. I need to be fresh for that - and also, if the problem isn't fixed, I need to be able to speak to what went wrong, as well as help where I can with contingency, etc.
Bottom line - don't be a primadonna as a manager. Help where you can - coordinate, give ideas, be a sounding board, stop bad ideas that go down the wrong path, manage the users, buy pizza, etc. And make sure that when you do go home, make sure that the team trusts YOU. They need to know that you're leaving for good reason...not just because you want to go home.
I wonder how many times Guido has had to bear listening to that complaint about Python...
Not that I disagree, I dislike the tab based definition too..brackets defining blocks just works.
Not sure I get your comment, sorry. But what exactly does the cannon story have to do with Shrub's years in the White House?
>>If you start a small firework rocket, you can't predict how far up it will fly and when exactly it will blow up in a shiny and entertaining explosion. But you know the limits of that rocket, e.g. it won't fly up more than 200 feet, the light of the explosion won't last longer than 10 seconds and it won't get hotter than 150 degrees celsius in the center of the explosion (numbers completely made up by me).
>>The scientists know that the black hole and anything else that may come from LHC won't destroy the world.
Let us not forget though that every now and then one of those little bottle rockets goes astray and ends up exploding in someone's personal space. Eyes get lost, etc.
So even though we know that said rocket can only go 200 ft up, and can only burn at 150 C, when it does misbehave it usually ends up causing some amount of trouble.
Think about it.
or an animal attaching at short distance.....