When you flash a CCD, the affected cells will affect their cell column, resulting in a bright line from the hotspot straight up to the edge of the photo. This doesn't look like an overloaded CCD, in other words.
> one other thing that i really should make clear is that i used - and still use - a programming technique which recently gained a name: "extreme programming".
> basically what i do is i build up a picture in my head of what results i want to achieve, and how, in broad architectural terms that that picture should be built.
> then i start incessantly, repeatedly, rapidly, bluntly and brutally chipping away at the details: in the case of coding that could result in 30 cvs commits per day.
This is precisely the *opposite* of the Extreme Programming.
XP means you have to first decide on the exact functionality that you want to deliver, then write the stubs (i.e. classes/function calls that do nothing) and tests for those stubs (which invariably fail).
Then you implement the stubs, making the tests work one by one.
One of the defining characteristics of XP is that the committed code always builds and always does something, and you can always *tell* which part of it works by looking at the test runs.
Committing broken code into CVS is not programming at all. It's team disruption and is inexcusable. It also raises your own productivity at the cost of lowering everyone else's, something else that I find inexcusable.
Is it just me, or does this thing really looks SOOOOO much like runabouts from Voyager (sans warp nacelles, but I guess it's a Minor Mater of Engineering...:) )?
> But that aside the reason why I as an IT guy am not impressed by Windows is that it is difficult to administer remotely (when Microsoft shows me a version of Windows that I can admin over a 9600 BPS serial link with a CLI I'll be interested) and the fact that I don't want to be Microsoft's bitch.
Well, using 9600 serial link as an example nowadays would likely give you a blank look and a 'why would you want to do that anyway' from your typical advocacy target (even if -I- know that it comes in handy).
But a better example would be: I can ssh into my Linux boxen by installing PuTTY on a Symbian mobile phone. Like my Nokia 3660. It's even cheap, since I get charged by bandwidth and not by time.
You should've seen the faces of my coworkers when I demonstrated this the first time.:)
> "creeping" indeed. C# is here now, and you can write real apps in it now. Parrot still hasn't gotten out of the gate. It just happened to move a little.
But the languages covered by Parrot have been around long before.NET was even conceived of, and there is a huge pile of software already written in each of them. Parrot simply ups the ante to the whole new level.
> perhaps, though, they should create a list of state-approved electromechanical stimulation devices. somehow the notion of a state sanctioned "sexual energy dissipation device" would fit nicely with the whole "control" thing they're into.
While at it, perhaps they should also offer state subsidy for the multiuser product.
The company where I work currently uses the oldest programming language for the numerics core of its software package (that'd be FORTRAN) and we're in the starting phase of the move of everything else to the second oldest language (that'd be LISP).
Here, if you know what you're doing, you buy components. Which is what I do. Preassembled PCs are generally also preinstalled. With Linux, as of late, unless you make a mistake of buying a Dell (which are sold here, too).
Actually in many countries they levy tax on blank media on presumption that they'll be used for piracy. They already won that battle from a different direction.
> Why go through all the trouble of buying a machine with an OS when you can just get a barebones machine and then load what ever OS you want.
Because of the strong Microsoft campaign against selling those machines as 'encouraging piracy', many vendors don't offer them at all. Others only offer this if you buy components and assemble them yourself - this is beyond many users who do want to run Linux.
Which is what the fuss is all about - a nice MS marketing ploy is falling apart and they're taking notice.
> What used to happen is that one kid would nick one of these magazines and bring it to school. Everyone else would borrow said magazines (the rest is left as an exercise for the reader).
Wasn't it an exercise for everyone involved, actually?:)
'Hey, look what I found. It's German Scheisse Fetisch Movie' 'It's Cartman's mom!' 'What are they doing?!' *sounds of disgust. Kyle vomits* 'What's wrong with these Germans?'
My coworker is currently recovering from 3 days' bugfixing session.
In C++, he called a virtual method off uninitialised pointer. The random piece of code that got run somehow managed not to crash the program immediately. Instead, it overran stack in random places. The program would crash in a corrupted STL list, in a completely unrelated spot. And it wasn't compatible with Valgrind.
Frankly, I'd take bugs in Java code instead of this anytime.
This means sufficient output power to drive really good earphones (we're still talking 50-100mW... most mp3 players only do 5 or so, and when they spend 200mW to begin with, the difference doesn't affect battery life/that/ much), and some love&care when selecting the output amplifier. And no, well-encoded mp3s at a good bitrate don't sound bad even on a good pair of phones.
Now my experience with MegaBass, WoW and all such toys is that on a good pair of phones, they turn bass from perfect to overwhelming, and on earbuds, they turn bassless music into bassless noise.
Any suggestions for a player that sounds good (with all bells and whistles irrelevant to the comparison)?
Caveat: what I tend to consider good earphones is not something you'd want to jog with. Form factor is not that high on my list of priorities.
The only problem with cold-dead-hands argument is that it's a bit unimpressive to point Kazaa at the person who wants to take it from you and pull 'Download'.
I'm somewhat familiar with the way mp3 works. It won't artifact on pure tones with not-too-much harmonics, or on several pure tones with not-too-much harmonics. What kills it is noise.
Also, listening on anything approaching decent equipment, the artifacts are nothing like subtle. They sound like raindrops and are spatially separated from the music itself - i.e. if what you use to listen can do anywhere near decent stereo imaging and reproduce half-decent highs, you'll hear them in a nasty, in-your-face way.
> The Spatial Nautilus is very very annoying - it's much like the default Windows behaviour of popping up zillions of windows that you always have to turn off every time you reinstall Windows.
Double-middle-click (or double-right-click, I'm not sure) on a directory closes the current window and pops the new one. This de-annoyifies Nautilus quite a bit.:)
... but if you look for a materialistic value, I for one haven't had a job interview where my (actually rather meager) list of OSS contributions didn't make an impact - quite contrary to Clemens' blather. In fact, it tends to shadow both my education and work experience as an employment factor.
That's because you can *prove* your worth with a couple of URLs.
Mind you, I have no problem with writing software for sale. But I also require (before accepting any job) an explicit permission to continue with OSS on my own time.
> The size of DVD images can be too big: many sites would hesitate to publish it afraiding too many people would download it and crash their sites, while many users would hesitate to download it as it's too big for their DSL lines.
Duh! This is exactly the problem that BitTorrent is designed to solve!:)
Slashdot Mirror
When you flash a CCD, the affected cells will affect their cell column, resulting in a bright line from the hotspot straight up to the edge of the photo. This doesn't look like an overloaded CCD, in other words.
> one other thing that i really should make clear is that i used - and still use - a programming technique which recently gained a name: "extreme programming".
> basically what i do is i build up a picture in my head of what results i want to achieve, and how, in broad architectural terms that that picture should be built.
> then i start incessantly, repeatedly, rapidly, bluntly and brutally chipping away at the details: in the case of coding that could result in 30 cvs commits per day.
This is precisely the *opposite* of the Extreme Programming.
XP means you have to first decide on the exact functionality that you want to deliver, then write the stubs (i.e. classes/function calls that do nothing) and tests for those stubs (which invariably fail).
Then you implement the stubs, making the tests work one by one.
One of the defining characteristics of XP is that the committed code always builds and always does something, and you can always *tell* which part of it works by looking at the test runs.
Committing broken code into CVS is not programming at all. It's team disruption and is inexcusable. It also raises your own productivity at the cost of lowering everyone else's, something else that I find inexcusable.
Is it just me, or does this thing really looks SOOOOO much like runabouts from Voyager (sans warp nacelles, but I guess it's a Minor Mater of Engineering... :) )?
--
> But that aside the reason why I as an IT guy am not impressed by Windows is that it is difficult to administer remotely (when Microsoft shows me a version of Windows that I can admin over a 9600 BPS serial link with a CLI I'll be interested) and the fact that I don't want to be Microsoft's bitch.
:)
Well, using 9600 serial link as an example nowadays would likely give you a blank look and a 'why would you want to do that anyway' from your typical advocacy target (even if -I- know that it comes in handy).
But a better example would be: I can ssh into my Linux boxen by installing PuTTY on a Symbian mobile phone. Like my Nokia 3660. It's even cheap, since I get charged by bandwidth and not by time.
You should've seen the faces of my coworkers when I demonstrated this the first time.
--
> "creeping" indeed. C# is here now, and you can write real apps in it now. Parrot still hasn't gotten out of the gate. It just happened to move a little.
.NET was even conceived of, and there is a huge pile of software already written in each of them. Parrot simply ups the ante to the whole new level.
But the languages covered by Parrot have been around long before
--
> I believe Bush has some sort of speech impediment and a difficulty speaking extemporaneously.
Yes, I could agree that he would have great difficulties saying 'extemporaneously'.
--
> perhaps, though, they should create a list of state-approved electromechanical stimulation devices. somehow the notion of a state sanctioned "sexual energy dissipation device" would fit nicely with the whole "control" thing they're into.
While at it, perhaps they should also offer state subsidy for the multiuser product.
--
The company where I work currently uses the oldest programming language for the numerics core of its software package (that'd be FORTRAN) and we're in the starting phase of the move of everything else to the second oldest language (that'd be LISP).
;)
70's, 80's and 90's didn't really happen.
--
I wouldn't know, I'm in Croatia.
Here, if you know what you're doing, you buy components. Which is what I do. Preassembled PCs are generally also preinstalled. With Linux, as of late, unless you make a mistake of buying a Dell (which are sold here, too).
--
Actually in many countries they levy tax on blank media on presumption that they'll be used for piracy. They already won that battle from a different direction.
--
> Why go through all the trouble of buying a machine with an OS when you can just get a barebones machine and then load what ever OS you want.
Because of the strong Microsoft campaign against selling those machines as 'encouraging piracy', many vendors don't offer them at all. Others only offer this if you buy components and assemble them yourself - this is beyond many users who do want to run Linux.
Which is what the fuss is all about - a nice MS marketing ploy is falling apart and they're taking notice.
--
> What used to happen is that one kid would nick one of these magazines and bring it to school. Everyone else would borrow said magazines (the rest is left as an exercise for the reader).
:)
Wasn't it an exercise for everyone involved, actually?
--
'Hey, look what I found. It's German Scheisse Fetisch Movie'
:)
'It's Cartman's mom!'
'What are they doing?!'
*sounds of disgust. Kyle vomits*
'What's wrong with these Germans?'
South Park lives forever.
--
Before they (uncutely) renamed it to imglib2, the Mozilla's image reader library was officially called libpr0n.
--
Hear, hear!
My coworker is currently recovering from 3 days' bugfixing session.
In C++, he called a virtual method off uninitialised pointer. The random piece of code that got run somehow managed not to crash the program immediately. Instead, it overran stack in random places. The program would crash in a corrupted STL list, in a completely unrelated spot. And it wasn't compatible with Valgrind.
Frankly, I'd take bugs in Java code instead of this anytime.
--
> Games
In most environments where you might expect a visit from MS salesman, 'Does Not Run Games' is considered a feature.
--
... is all I ask.
/that/ much), and some love&care when selecting the output amplifier. And no, well-encoded mp3s at a good bitrate don't sound bad even on a good pair of phones.
This means sufficient output power to drive really good earphones (we're still talking 50-100mW... most mp3 players only do 5 or so, and when they spend 200mW to begin with, the difference doesn't affect battery life
Now my experience with MegaBass, WoW and all such toys is that on a good pair of phones, they turn bass from perfect to overwhelming, and on earbuds, they turn bassless music into bassless noise.
Any suggestions for a player that sounds good (with all bells and whistles irrelevant to the comparison)?
Caveat: what I tend to consider good earphones is not something you'd want to jog with. Form factor is not that high on my list of priorities.
--
The only problem with cold-dead-hands argument is that it's a bit unimpressive to point Kazaa at the person who wants to take it from you and pull 'Download'.
--
I'm somewhat familiar with the way mp3 works. It won't artifact on pure tones with not-too-much harmonics, or on several pure tones with not-too-much harmonics. What kills it is noise.
Also, listening on anything approaching decent equipment, the artifacts are nothing like subtle. They sound like raindrops and are spatially separated from the music itself - i.e. if what you use to listen can do anywhere near decent stereo imaging and reproduce half-decent highs, you'll hear them in a nasty, in-your-face way.
--
You were lucky. I saw a fresh, just brought from the shop ATI 7500 do a Chinese syndrome through the AGP slot.
--
> The Spatial Nautilus is very very annoying - it's much like the default Windows behaviour of popping up zillions of windows that you always have to turn off every time you reinstall Windows.
:)
Double-middle-click (or double-right-click, I'm not sure) on a directory closes the current window and pops the new one. This de-annoyifies Nautilus quite a bit.
--
... but if you look for a materialistic value, I for one haven't had a job interview where my (actually rather meager) list of OSS contributions didn't make an impact - quite contrary to Clemens' blather. In fact, it tends to shadow both my education and work experience as an employment factor.
That's because you can *prove* your worth with a couple of URLs.
Mind you, I have no problem with writing software for sale. But I also require (before accepting any job) an explicit permission to continue with OSS on my own time.
--
> Learn 5, because it will probably take a few months until 6 is standard.
;)
In the same vein, I'm probably going to get my copy of Half Life 2 in a week or two...
--
> But how does eval $string work in a runtime with no compiler?
Parrot is a jitter, fed by the bytecode compiler written in... parrot. The bytecode compiler is part of the runtime, of course.
--
> The size of DVD images can be too big: many sites would hesitate to publish it afraiding too many people would download it and crash their sites, while many users would hesitate to download it as it's too big for their DSL lines.
:)
Duh! This is exactly the problem that BitTorrent is designed to solve!
--