I think it would be just as foolish to dismiss this outright, considering the " tantalizing hints that there may be something to it" and the developing theories as it would be to start dumping your life savings into Rossi's company.
How many times has Microsoft broken everyone's code with one of their updates? How many times has someone's code been broken by some other app dicking around with things it shouldn't? How many times has some idiot administrator broken code by fucking with security? How many times has someone's code been broken by a DBA changing shit in the database? How many times has someone's code been broken by the user jacking around with it and deleting stuff they shouldn't be messing with? How many times has someone's code been broken by viruses, malware, etc? How many times has someone's code been broken because the user changes the OS? How many times has code been called broken because the user didn't know exactly what they needed and genius here didn't bother to catch it?
You can write perfect code and there are legions of ways it can be "broke" by others in ways you can't and/or shouldn't anticipate.
That's because they wanted people to keep their spear disassembled when not in use. So when a Sabertoothed Tiger came into your cave, you would have had to ask it to wait while you tied the pointy rock to the end. And before you start, short pointy sticks are only good against other cavemen.
If you think that being responsible for things that have a bottom line impact on the company, being responsible for people's jobs, mortgage payments, their ability to feed and cloth their children, if you think that sucks, then yeah, you will clearly not be interested in these positions.
On the other hand, if you enjoy making an impact and helping the business (which helps everyone else in the business and its investors) then you may want to think about learning about business instead of just being a little, replaceable cog in the machine.
What you overlook is that business practices don't really "evolve". Invoices will always be invoices, accounts will always be accounts, etc. As a result, business systems rarely have to be re-invented, just tweaked.
All the fancy stuff can extend the business systems through controlled access to the core business data, but the core business processes are pretty much fixed in place by law and well established business practices.
A huge number of business are still running RPG, COBOL and FORTRAN. Why? Because the stuff they wrote with it does what it is supposed to do and has been debugged for years and years and so is almost bullet proof now.
And the biggest role of software in most companies if running the business. Imagine all the code behind Netflicks. Probably done in the latest and greatest frameworks and languages, etc. But you can bet that their business systems are probably in a large Cobol package like SAP.
Technology comes and goes, but an Invoice will always be an Invoice.
It's know what the hell the Purchasing Manager is saying when they say they need a Purchase Price Variance Report.
It's knowing what to do when the Accountant says that something happened to the GL Transactions and he can't close the month out,which has to happen in 2 days in order for production to continue.
It's knowing the different between a Dock Date, Promise Date and a Required Date.
It's knowing how to take all these fancy new techniques and languages and make them worth bothering to have someone learn in the first place.
It's these people who get paid more and have more of impact on the business. Dweeb version 101 and his toolbox of shit mean nothing unless they can be used effectively to run the business.
Slashdot Mirror
If you are speaking E-Cat. Yes.
If you are speaking LENR, then we should just let the research take it's course and not kill it out of some prejudice of some kind
I should clarify: "This" is LENR, not the E-cat.
Which is why I said not to conflate, confuse, the two.
Rossi's failure to provide a machine freely for examination is a sure sign he's doctoring something.
I think it would be just as foolish to dismiss this outright, considering the " tantalizing hints that there may be something to it" and the developing theories as it would be to start dumping your life savings into Rossi's company.
Don't conflate a charlatan with the science. NASA is still looking at this.
I do not pay for bugs.
This guy is a prick.
And you are not far behind.
How many times has Microsoft broken everyone's code with one of their updates?
How many times has someone's code been broken by some other app dicking around with things it shouldn't?
How many times has some idiot administrator broken code by fucking with security?
How many times has someone's code been broken by a DBA changing shit in the database?
How many times has someone's code been broken by the user jacking around with it and deleting stuff they shouldn't be messing with?
How many times has someone's code been broken by viruses, malware, etc?
How many times has someone's code been broken because the user changes the OS?
How many times has code been called broken because the user didn't know exactly what they needed and genius here didn't bother to catch it?
You can write perfect code and there are legions of ways it can be "broke" by others in ways you can't and/or shouldn't anticipate.
What is this? History Channel's Deadliest Warrior episode?
Nice.
Everyone knows that the Aliens built those.
Nice.
I'd like some Italian dressing with that.
Remember...treat a spear like it's ALWAYS sharp.
That's because they wanted people to keep their spear disassembled when not in use. So when a Sabertoothed Tiger came into your cave, you would have had to ask it to wait while you tied the pointy rock to the end. And before you start, short pointy sticks are only good against other cavemen.
The Romain Empire used concrete extensively, even hydraulic cement (cures under water).
After the Empire fell, they went back to building with rocks.
...rocks with rules scratched into them regarding Spear Control.
'nuff said.
Bite me.
If you think that being responsible for things that have a bottom line impact on the company, being responsible for people's jobs, mortgage payments, their ability to feed and cloth their children, if you think that sucks, then yeah, you will clearly not be interested in these positions.
On the other hand, if you enjoy making an impact and helping the business (which helps everyone else in the business and its investors) then you may want to think about learning about business instead of just being a little, replaceable cog in the machine.
Mark your sarcasm as such. I've worked in SAP and it is done by and large in COBOL, batch processing environment.
What you overlook is that business practices don't really "evolve". Invoices will always be invoices, accounts will always be accounts, etc. As a result, business systems rarely have to be re-invented, just tweaked.
All the fancy stuff can extend the business systems through controlled access to the core business data, but the core business processes are pretty much fixed in place by law and well established business practices.
A huge number of business are still running RPG, COBOL and FORTRAN. Why? Because the stuff they wrote with it does what it is supposed to do and has been debugged for years and years and so is almost bullet proof now.
And the biggest role of software in most companies if running the business. Imagine all the code behind Netflicks. Probably done in the latest and greatest frameworks and languages, etc. But you can bet that their business systems are probably in a large Cobol package like SAP.
Technology comes and goes, but an Invoice will always be an Invoice.
It's more of knowing how the business works.
It's know what the hell the Purchasing Manager is saying when they say they need a Purchase Price Variance Report.
It's knowing what to do when the Accountant says that something happened to the GL Transactions and he can't close the month out,which has to happen in 2 days in order for production to continue.
It's knowing the different between a Dock Date, Promise Date and a Required Date.
It's knowing how to take all these fancy new techniques and languages and make them worth bothering to have someone learn in the first place.
It's these people who get paid more and have more of impact on the business. Dweeb version 101 and his toolbox of shit mean nothing unless they can be used effectively to run the business.
So...you want me to work a ten hour day AND learn the latest bullshit fade language after hours.
Fuck You sonny boy.
To paraphrase the fictional Dr. Ian Malcolm:
"Tyranny finds a way".
I'm sorry, what Government Agency needs to pay attention to this and what should they do about it?
Answer: None.
The only reason 9 and 10 year old children are sleep deprived is because of dumb shit parents who don't give a fuck about their kids.
And the only people who can do anything about it is the dumb shit parents.
So...according to the Government, the second Amendment only protects Muskets and the 4th only protects snail mail.
I hope they double check their calculations or they may die quicker than they figured by slamming into Mars.