I've had the pleasure of such phyric "career changes" in the past when I couldn't tale how "stoopud" or "ignurnt" the analysts or upper management were.
I went from calamity to disaster always leaving a few weeks before the hand-writing was on the wall for the companies or the departments or the projects involved. Shit happens but it wasn't happening to me.
The last time, I actually waited for the manager to offer me my head on a plate and JUMPED at the opportunity to not let the door hit me in the ass on the way out. That bit of grand-standing saved my life (I worked on the 83rd floor at the WTC and lived next door,) but I ended up not working for a year. (Okay I must admit, I was rattled and worth shit for several months after my lucky escape. I slacked off and burnt through my 401k. But I was ALIVE.:-)
Now I'm going employed again but I'm going back to school and looking for a better job NOT doing software development.
I would never buy a toilet designed and built by a software firm. I couldn't trust that the idiots programmed water to CONSISTENTLY run down-hill.
Come to think of it, I don't trust software firms to hold to any set of laws; physical, moral or legal. We have had plenty of expensive lessons that they DON'T.
None. They only care(d) about imposing their will.
Ask the Germans how long the Nazis lasted and how well The country fared under them.
The fact is that the record buying public is only a small source of money for the RIAA. They actually earn more money from elevators and building lobbies. Their second largest source of revenue is commercial jingles.
Anywhere where they don't have to pay the artist a dime (check the books, they don't have to and they damn well don't...)
Wanna KILL the RIAA?
Go to a show. Support the artist directly by showing up, buying a ticket right there and give the money to the band directly by putting it in a bucket on the stage.
If you're a band, refuse to sign a contract where YOU don't receive 75% of the GROSS.
The RIAA is screwing YOU the listener and the artists.
This is a dead issue. Specially when dealing with Apple's supplier list. People have gone insane trying to guess what Steve Jobs is going to do.
That is the kind of stochastic tittilation usually provided by people trying to predict the direction the an elephant will travel from a point of view only slightly in front of its tail.
In some respects this is the LEAST interesting application of WiFi and networking.
I definitely do NOT want total strangers bugging me while I'm trying to do something on my TiBook anymore than I'd want them to yammer away on a cel phone while I'm trying to watch a movie.
Somebody hurt this moron.
Sometimes just being able to do something, like driving big rusty spikes into your eyeballs, does not make it desirable in the least.
But the new developments and apartment buildings will probably get fibre because its cheaper for the telcos.
We've been paying a surcharge for years for this and there's zilch implemented. My old building that was built in 1949 had twisted wire pair clad in cotton. I thought it was the wire for the friggin' door bell.
The newer ones have had four condictor plastic clad wire sincethen until now. As for fibre to your house, or even street switch box... Fuggedaboudit...
They wait until the infrastructure suffers an irrevocable breakdown (like a pole falling over, an underground pipe getting a back-hoe through it or fire and explosion at a CO,) before replacing a foot of wire.
And even then they're going to use left-over copper wire until its all gone.
A "perfect" copyright system would uterly stop civilization by utterly stopping the dissemination of information.
You can't quote from the Bible (Koran, Torah, whatever,) its copyright.
You can't quote from Shakespeare, its copyright. (Guttenberg project to the contrary, check the verbiage on the scripts of movies. Shakespeare is 0wn3d by the MPAA studios.)
You can't use text books in your course material. They're copyright.
And if you're not a member of some xxAA the only thing you'll be able to do is consume and pay. And they'll pay themselves too, but its just shifting from one pocket to another, that doesn't hurt quite as much.
And forget about sites like/. where we're forever quoting things giving book and movie reviews etc.
You'll be dealing with the INS. As self-serving a bunch of human beings as you're likely to encounter. They make sure you wear brown lipstick because they have some things (a visa and the power to toss you onto the next plane to nowhere,) only one of which you want.
It doesn't get worse than that unless you're black, don't dress in visibly wealthy "old money" style and just went through a stop sign...
America is a great place as long as you have money... Its pretty damn dismal when you don't.
Losing source code and var names (name spaced globals aka statics and scoped locals) allows the cracker (these are rarely hacking tools, they're mostly cracking tools,) to focus on what the machine actually was told to do instead of smothering it with shades of meaning which interfere with understanding the code.
C++ or Java or Smalltalk, or almost any highly structured language using machine code libraries or virtual machines result in structured blocks of code and heap and stack allocation.
A good decompiler can take the machine code, peel away the name spaces and code calls, extract the patterns in the code and the hacker/cracker can read the patterns instead of wasting time on the code.
Forensic analysis work is extremely useful at telling you what happened when something dies but it is no good at telling you how something worked. For that you need code traces.
Map those code traces onto the structure the decompiler reveals and you understand the program better than the authors/coders.
"Trust us..." (Old expression meaning "Fuck You!")
The problem is self made and perpetuated by history. It's the difference between a simple lever which punches a hole in a piece of paper and which anyone can see and understand, and the incredibly bull-shit filled explanations of the process that most comp-sci majors will come up with to explain the code.
Every mistake that can be made in describing the specifications, the code, the inputs or the results will be made. From anthropomorphization to bald-faced blustering.
There is no field of endeavor which professes to be a profession where the fundamentals are so obscurely obfuscated and the advances are so incredibly unbelievable.
I don't trust comp-sci majors to install plumbing.
come up with a bad idea, hype it up, make it look like its making money, and M$ is sure to fall for it, integrate it into their OS and never realize why people look to Apple and Linux for alternatives.
Repeat until the OS sucks so badly that not even a PHB would buy it.
The first is for the silicon scrapers. Guys who write device drivers and who are amply served by assembler (for the real propeller-head bit-twiddlers) and and by C (Not C++, C) There is no sense of reality at this level.
The second level is for the tool makers. The guys who bring you APIs and services like TCP/IP, Tuxedo, database managers, OpenGL, compilers, browsers and the like. Those folks use C++ and Java. Its a mistake to think that you can make an application in C++ or Java or Smalltalk. You can cobble something together that will cost too much and be too brittle for real-world use and eventually break (or break the bank.) The world becomes real.
The last level is integrative. There aren't any languages which assimilate the concepts which programmers are confronted with in the real world.
The best we have to date is sort of the second and a half level with languages which, with the support of a whole bunch of other third party systems (both code and manual procedures,) are sort of capable of some mimetic link between soma (the code) and extro (the specs.) (Sort of like CICS COBOL on mainframes.)
From what I saw, F#, uh, isn't. Its better but still, its like C++, ObjectiveC or Smalltalk or any other container based language where contained objects have no clue that they contained unless the programmer creates and maintains explicit references to the container.
The flaw starts there and gets carried forward.
And computing is so fundamentally simple. Its a game of N-Dimensional topology bounded by finite vectors in every dimension. There's no mystery involved. You just need to maintain a meta-model of the system and you can generate the rest.
What do you think programmers are and what do you think they're doing? They're code generators that fetch their own meta-model. Some do itbetter than other and some such at code generation too.
Been around the spook community since 70s/80s
on
Book-Digitizing Robots
·
· Score: 2, Informative
This is not new.
The hardware has been hard at work since the late 70s/early 80s when PDP-8s and PDP-11s were used to control the hardware and store the results.
The first scanners had very small CCD arrays and these had to be pulled across the page horizontally as well as vertically AND it had vacuum "bars" on robot-arm "page turners".
I bought an Old English dictionary. YOU OWE ME $$!
on
OSI vs SCO
·
· Score: 1
That's about the level of the argument here.
I hope that the court DOESN'T just throw this out of court but fines SCO into oblivion as a warning to other IP vultures (and saves IBM the time and expense of counter-suing.)
They don't have a screen shot of Aqua and they only said that their OS sucked through a straw and needed something better like Linux or OS X (and not even Apple would object unless they try to get Aqua running on it. Then they'd feel the wrath of Jobs and his legal minions.)
You need to get the code monkey off the production box.
They need a Dev environment. And THAT's ALL they touch. They deliver their code to UAT.
QA needs 2 environments: - Unit Acceptence testing (UAT) and all bugs go back to Dev - Integration Testing (IT) and all bugs back to Dev or you need SysAdmins who need to hack the OS middleware &| environment)
Production where NOHING is allowed until its gone through UAT & IT.
In North America the scheme for eliminating freight ways is doomed.
Too much volume. How many donkeys does it take to carry the same weight and volume as a 40 foot semi trailer.? No multiply that by six orders of magnitude.
The use of containers in shipping has eliminated billions of dollars in pilferage and cut many organized crime revenue streams off at the knees.
And if you have roads for freight, they car also carry cars...
with a USB base to boot.
I've had the pleasure of such phyric "career changes" in the past when I couldn't tale how "stoopud" or "ignurnt" the analysts or upper management were.
:-)
I went from calamity to disaster always leaving a few weeks before the hand-writing was on the wall for the companies or the departments or the projects involved. Shit happens but it wasn't happening to me.
The last time, I actually waited for the manager to offer me my head on a plate and JUMPED at the opportunity to not let the door hit me in the ass on the way out. That bit of grand-standing saved my life (I worked on the 83rd floor at the WTC and lived next door,) but I ended up not working for a year. (Okay I must admit, I was rattled and worth shit for several months after my lucky escape. I slacked off and burnt through my 401k. But I was ALIVE.
Now I'm going employed again but I'm going back to school and looking for a better job NOT doing software development.
Life is good.
by neophites and dabblers.
I would never buy a toilet designed and built by a software firm. I couldn't trust that the idiots programmed water to CONSISTENTLY run down-hill.
Come to think of it, I don't trust software firms to hold to any set of laws; physical, moral or legal. We have had plenty of expensive lessons that they DON'T.
None. They only care(d) about imposing their will.
Ask the Germans how long the Nazis lasted and how well The country fared under them.
The fact is that the record buying public is only a small source of money for the RIAA. They actually earn more money from elevators and building lobbies. Their second largest source of revenue is commercial jingles.
Anywhere where they don't have to pay the artist a dime (check the books, they don't have to and they damn well don't...)
Wanna KILL the RIAA?
Go to a show. Support the artist directly by showing up, buying a ticket right there and give the money to the band directly by putting it in a bucket on the stage.
If you're a band, refuse to sign a contract where YOU don't receive 75% of the GROSS.
The RIAA is screwing YOU the listener and the artists.
Personally, if I owned any boxen with SCO on 'em, they'd be SCO 'libre' PDQ.
I urge all SCO customers to do the same. SCO has no legitimacy and no further reason for existence.
I can already get video on demand. Well I could if I owned a TV set and had cable hooked up to it...
This has Prior Art written all over it.
This is a dead issue. Specially when dealing with Apple's supplier list. People have gone insane trying to guess what Steve Jobs is going to do.
That is the kind of stochastic tittilation usually provided by people trying to predict the direction the an elephant will travel from a point of view only slightly in front of its tail.
In some respects this is the LEAST interesting application of WiFi and networking.
I definitely do NOT want total strangers bugging me while I'm trying to do something on my TiBook anymore than I'd want them to yammer away on a cel phone while I'm trying to watch a movie.
Somebody hurt this moron.
Sometimes just being able to do something, like driving big rusty spikes into your eyeballs, does not make it desirable in the least.
And now morally bankrupt.
But the new developments and apartment buildings will probably get fibre because its cheaper for the telcos.
We've been paying a surcharge for years for this and there's zilch implemented. My old building that was built in 1949 had twisted wire pair clad in cotton. I thought it was the wire for the friggin' door bell.
The newer ones have had four condictor plastic clad wire sincethen until now. As for fibre to your house, or even street switch box... Fuggedaboudit...
They wait until the infrastructure suffers an irrevocable breakdown (like a pole falling over, an underground pipe getting a back-hoe through it or fire and explosion at a CO,) before replacing a foot of wire.
And even then they're going to use left-over copper wire until its all gone.
You can't quote from the Bible (Koran, Torah, whatever,) its copyright.
You can't quote from Shakespeare, its copyright. (Guttenberg project to the contrary, check the verbiage on the scripts of movies. Shakespeare is 0wn3d by the MPAA studios.)
You can't use text books in your course material. They're copyright.
And if you're not a member of some xxAA the only thing you'll be able to do is consume and pay. And they'll pay themselves too, but its just shifting from one pocket to another, that doesn't hurt quite as much.
And forget about sites like
You'll be dealing with the INS. As self-serving a bunch of human beings as you're likely to encounter. They make sure you wear brown lipstick because they have some things (a visa and the power to toss you onto the next plane to nowhere,) only one of which you want.
It doesn't get worse than that unless you're black, don't dress in visibly wealthy "old money" style and just went through a stop sign...
America is a great place as long as you have money... Its pretty damn dismal when you don't.
they for the people who are going to try to USE the software so that they have cleasr and understandable processes and APIs.
not the source's lies.
Losing source code and var names (name spaced globals aka statics and scoped locals) allows the cracker (these are rarely hacking tools, they're mostly cracking tools,) to focus on what the machine actually was told to do instead of smothering it with shades of meaning which interfere with understanding the code.
C++ or Java or Smalltalk, or almost any highly structured language using machine code libraries or virtual machines result in structured blocks of code and heap and stack allocation.
A good decompiler can take the machine code, peel away the name spaces and code calls, extract the patterns in the code and the hacker/cracker can read the patterns instead of wasting time on the code.
Forensic analysis work is extremely useful at telling you what happened when something dies but it is no good at telling you how something worked. For that you need code traces.
Map those code traces onto the structure the decompiler reveals and you understand the program better than the authors/coders.
"Trust us..." (Old expression meaning "Fuck You!")
The problem is self made and perpetuated by history. It's the difference between a simple lever which punches a hole in a piece of paper and which anyone can see and understand, and the incredibly bull-shit filled explanations of the process that most comp-sci majors will come up with to explain the code.
Every mistake that can be made in describing the specifications, the code, the inputs or the results will be made. From anthropomorphization to bald-faced blustering.
There is no field of endeavor which professes to be a profession where the fundamentals are so obscurely obfuscated and the advances are so incredibly unbelievable.
I don't trust comp-sci majors to install plumbing.
come up with a bad idea, hype it up, make it look like its making money, and M$ is sure to fall for it, integrate it into their OS and never realize why people look to Apple and Linux for alternatives.
Repeat until the OS sucks so badly that not even a PHB would buy it.
and they'll go to Norway and haul your ass into a US court.
There are three levels to programming.
The first is for the silicon scrapers. Guys who write device drivers and who are amply served by assembler (for the real propeller-head bit-twiddlers) and and by C (Not C++, C) There is no sense of reality at this level.
The second level is for the tool makers. The guys who bring you APIs and services like TCP/IP, Tuxedo, database managers, OpenGL, compilers, browsers and the like. Those folks use C++ and Java. Its a mistake to think that you can make an application in C++ or Java or Smalltalk. You can cobble something together that will cost too much and be too brittle for real-world use and eventually break (or break the bank.) The world becomes real.
The last level is integrative. There aren't any languages which assimilate the concepts which programmers are confronted with in the real world.
The best we have to date is sort of the second and a half level with languages which, with the support of a whole bunch of other third party systems (both code and manual procedures,) are sort of capable of some mimetic link between soma (the code) and extro (the specs.) (Sort of like CICS COBOL on mainframes.)
From what I saw, F#, uh, isn't. Its better but still, its like C++, ObjectiveC or Smalltalk or any other container based language where contained objects have no clue that they contained unless the programmer creates and maintains explicit references to the container.
The flaw starts there and gets carried forward.
And computing is so fundamentally simple. Its a game of N-Dimensional topology bounded by finite vectors in every dimension. There's no mystery involved. You just need to maintain a meta-model of the system and you can generate the rest.
What do you think programmers are and what do you think they're doing? They're code generators that fetch their own meta-model. Some do itbetter than other and some such at code generation too.
This is not new.
The hardware has been hard at work since the late 70s/early 80s when PDP-8s and PDP-11s were used to control the hardware and store the results.
The first scanners had very small CCD arrays and these had to be pulled across the page horizontally as well as vertically AND it had vacuum "bars" on robot-arm "page turners".
That's about the level of the argument here.
I hope that the court DOESN'T just throw this out of court but fines SCO into oblivion as a warning to other IP vultures (and saves IBM the time and expense of counter-suing.)
They don't have a screen shot of Aqua and they only said that their OS sucked through a straw and needed something better like Linux or OS X (and not even Apple would object unless they try to get Aqua running on it. Then they'd feel the wrath of Jobs and his legal minions.)
This was a bogus post.
You need to get the code monkey off the production box.
They need a Dev environment. And THAT's ALL they touch. They deliver their code to UAT.
QA needs 2 environments:
- Unit Acceptence testing (UAT) and all bugs go back to Dev
- Integration Testing (IT) and all bugs back to Dev or you need SysAdmins who need to hack the OS middleware &| environment)
Production where NOHING is allowed until its gone through UAT & IT.
Imagine getting a kilovolt (at a kiloamp) back from a web site that's being slashdotted.
Or better yet. Imagine sending THAT as a response to some Spam.
That would take care of the problem PDQ.
In North America the scheme for eliminating freight ways is doomed.
Too much volume. How many donkeys does it take to carry the same weight and volume as a 40 foot semi trailer.? No multiply that by six orders of magnitude.
The use of containers in shipping has eliminated billions of dollars in pilferage and cut many organized crime revenue streams off at the knees.
And if you have roads for freight, they car also carry cars...
with their software and file formats.