I worked for a bank back in the day, was told to make code changes to the online screens to add an extra 'service fee' to the clients account, had to add a checkbox so that it could be switched off if the client complained. Checked it a couple months later, not many people even noticed it or complained, netted them an extra half a mil a month.
Don't trust banks / bankers / insurance / sales people. They do not have your own best interests at heart.
And stable, you can whine as much as you like about the death of the mainframe, but until there is a reliable solid alternative it will be around for many many more years. (And no Linux might be more reliable than windows, but it does not come close).
Let's also not forget the billions of lines of code you will have to rewrite.
Wrong, I think you will find that most compilers will balk at any single line of code longer than 65 536 characters.
I doubt OpenCV is that short.
Also you forgot about the carriage returns. (Me being pedantic)
But if we had to extend your reasoning to everything and ignore line limits then we could say that all the software in the world is a single line of code and we pay programmers too much for one line of code.
I worked at a company that measured work progress by lines of code (LOC) stupid bloody idea that only a non programmer could come up with.
I have never come across more long ass winded code in my entire life.
Some calculation which could be done one one line took seven (or more)
Instead of refactoring common code into a function it was copy / pasted everywhere to bulk up LOC!
Suffice to say small changes to the common code was fraught with errors as one set of code was updated and a missed in a couple other places while digging through millions of lines of verbose code
Whoever came up with the idea of LOC as a measurement should be buried under the lines of redundant code it produced.
All software ends up a bloated pile of cr@p eventually UNLESS
You have policies in place to prevent it (like code reviews) as well as no quick fix's, rush jobs, or hacks..... Yeah right! Never worked in a company like that Ever!
Maybe the guys who get to code stuff like satellites and Mars rovers get the luxury of time to get things right/perfect
I know a ton of places which add the fee onto the CASH price if you want to pay with a credit card. So if you pay cash or do an EFT they do not add the charge for the credit card.
Clearly you have a different relationship with your parents than most people.
If my father says he wants x then x is what he gets
What he used at work, he wants at home, because he is familiar with it and it does what he wants/needs.
Also I have to comment on the fact that people who say that libre office is just as good as Office clearly do not understand or use Office to it's full ability.
Libre office has a looong way to go. (and just to clear things up I fvcken hate Office)
That being said Libre office will do for people why are just typing up the odd email, or summing a list of items etc.
But office has not been a major vector for viruses in a long while.
Do all updates and make sure automatically update is on (it's on by default)
Switch off hide file extensions for known file types
Install a good antivirus.
Most important of all, instill a fear of "When in doubt do not click", or at least forward it to you to check out first.
Therein lies the problem, your simple trigger will fire ALL THE TIME. When all I want to watch is record A value B. Triggers are expensive, do you really want to weigh your tables down with unnecessary trigger calls? Clearly you are only dealing with a couple hundred transactions a second, but when things get into the thousands, and at peak millions, placing a trigger on a database is sheer stupidity. Triggers which are utilized are due to bad planning, last resort efforts/or because of crap code. Three guesses which one is usually the culprit? No wonder DBA's are annoyed with programmers.
Good god (or in this case bad god)
Every damn company I have ever worked in has some (albeit smart) idiot who creates a smart excel/access application which does wonderful things.
Who then distributes it to xyz people
Then the datasource (ip address) changes and the thing breaks.
Or the datasource changes (database table changes) and the thing breaks
Or his hardcoded status codes changes or is expanded and the thing breaks
Then they call you out of the blue and say, please fix it!
Access is an evil which should die. Advocates of it are welcome to come debate the matter with me. I need fresh meat.
Excel is extremely powerful and a handy tool, but as soon as anyone adds a datasource they should come and debate the matter with me.
I know of one (sort of). His church elders had an issue working at a betting company so he resigned.
So I suppose you can say he caved into peer pressure, instead of his own personal morals.
I've been asked to reverse engineer / crack / hack and decrypt stuffs by some of the companies I've worked at.
I don't have an issue with it.
I also would not use any of that for personal gain.
(Well I gave myself 10 bucks to prove to them their secure credit card page was not as secure as they thought it was, but I gave it back).
I never said it was the best OS ever made.
I said that is what they are used to, comfortable with and unwilling to change from.
See how long you stay in business by force feeding your users with something they don't want, or in fact don't need because XP works for them.
I agree totally with what your are saying about security etc.
But if you don't give your users what they want (not NEED, but WANT) then shortly thereafter you won't have any users and it becomes a moot point
Because someone else will step in and give them what they want.
The best you can do is present to them the risks of running unsupported software etc and hope they make the right call.
Clearly you work in a cubicle farm with someone in charge making the right decisions instead of dealing with users who are paying you and refuse to change.
WTF? I did this a day or two ago! No issues.
We have some legacy software which requires VS 2003 to make changes (SDK only works with 2003 and XP)
Fired up a new VM, installed XP, ran updates, installed VS 2003, installed SDK, opened solution, fixed references, build, success, made minor changes, build, succes
Done
You are forgetting about people's comfort zone. XP works, they know how to change their settings for whatever.
The drivers for their XYC device install and work
The ancient app that they use to do their books/orders/whatever work
Old office (before the ribbon bar) works, and they know it backwards
IMHO MS are being fcking stupid by trying to force people off XP by no longer supporting it. When it becomes clear that they have to upgrade because of all the vulnerabilities that have now been left open people are going to upgrade. But will they upgrade to an MS OS? Drop support for XP when the user base has become negligible, not when there are still billions of users.
People DO NOT LIKE CHANGE (except from vending machines)
Oops, soz. Meant to reply to your query but got distracted by your sig.
Yes I went to school in a former British colony, so it's British English and British Law
In hindsight I think it was more about my teacher being British herself which made me lose points due to American spelling.
Then again I almost always scored 95+ on essays, she had to find fault somewhere?
Valid point, sad but true.
Also I suppose I am leeching knowledge of these sort of things (proxies et al) into my children since they were five.
I keep overestimating the typical user.
Slashdot Mirror
When I see how much hardware and electricity is wasted digging chunks of hardened carbon out of the ground, I can only shake my head.
When I see how much hardware and electricity is wasted jumping out of perfectly good airplanes, I can only shake my head.
We humans tend to do things because we want to, not because it makes sense to you.
I worked for a bank back in the day, was told to make code changes to the online screens to add an extra 'service fee' to the clients account, had to add a checkbox so that it could be switched off if the client complained. Checked it a couple months later, not many people even noticed it or complained, netted them an extra half a mil a month.
Don't trust banks / bankers / insurance / sales people. They do not have your own best interests at heart.
80 000 lines? Come back when you work on a real system.
And stable, you can whine as much as you like about the death of the mainframe, but until there is a reliable solid alternative it will be around for many many more years. (And no Linux might be more reliable than windows, but it does not come close).
Let's also not forget the billions of lines of code you will have to rewrite.
clearly he only reads /. at work (instead of working)
I think you are missing the point, if it has less resistance there will be less lost in long distance transmission.
Can imagine the wailing and nashing of all the 'concerned' mothers about a printer that can print a gun that can shoot more than once :-(
Wrong, I think you will find that most compilers will balk at any single line of code longer than 65 536 characters.
I doubt OpenCV is that short.
Also you forgot about the carriage returns. (Me being pedantic)
But if we had to extend your reasoning to everything and ignore line limits then we could say that all the software in the world is a single line of code and we pay programmers too much for one line of code.
I worked at a company that measured work progress by lines of code (LOC) stupid bloody idea that only a non programmer could come up with.
I have never come across more long ass winded code in my entire life.
Some calculation which could be done one one line took seven (or more)
Instead of refactoring common code into a function it was copy / pasted everywhere to bulk up LOC!
Suffice to say small changes to the common code was fraught with errors as one set of code was updated and a missed in a couple other places while digging through millions of lines of verbose code
Whoever came up with the idea of LOC as a measurement should be buried under the lines of redundant code it produced.
Less than a 100 lines???
How many lines of code are in OpenCV?
All software ends up a bloated pile of cr@p eventually
UNLESS
You have policies in place to prevent it (like code reviews) as well as no quick fix's, rush jobs, or hacks.....
Yeah right! Never worked in a company like that Ever!
Maybe the guys who get to code stuff like satellites and Mars rovers get the luxury of time to get things right/perfect
Nevermind did a quick google.
Bug 1
Bug 2
I know a ton of places which add the fee onto the CASH price if you want to pay with a credit card. So if you pay cash or do an EFT they do not add the charge for the credit card.
1990
"Lets fit everyone with a radio tracking device so we know where they are at all times"
"What, they would never allow that, it would never work"
2013
I can has two cellphones!
Mission achieved
Clearly you have a different relationship with your parents than most people.
If my father says he wants x then x is what he gets
What he used at work, he wants at home, because he is familiar with it and it does what he wants/needs.
Also I have to comment on the fact that people who say that libre office is just as good as Office clearly do not understand or use Office to it's full ability.
Libre office has a looong way to go. (and just to clear things up I fvcken hate Office)
That being said Libre office will do for people why are just typing up the odd email, or summing a list of items etc.
But office has not been a major vector for viruses in a long while.
Do all updates and make sure automatically update is on (it's on by default)
Switch off hide file extensions for known file types
Install a good antivirus.
Most important of all, instill a fear of "When in doubt do not click", or at least forward it to you to check out first.
I refer you to the tag below
Therein lies the problem, your simple trigger will fire ALL THE TIME. When all I want to watch is record A value B. Triggers are expensive, do you really want to weigh your tables down with unnecessary trigger calls? Clearly you are only dealing with a couple hundred transactions a second, but when things get into the thousands, and at peak millions, placing a trigger on a database is sheer stupidity. Triggers which are utilized are due to bad planning, last resort efforts/or because of crap code. Three guesses which one is usually the culprit? No wonder DBA's are annoyed with programmers.
Good god (or in this case bad god)
Every damn company I have ever worked in has some (albeit smart) idiot who creates a smart excel/access application which does wonderful things.
Who then distributes it to xyz people
Then the datasource (ip address) changes and the thing breaks.
Or the datasource changes (database table changes) and the thing breaks
Or his hardcoded status codes changes or is expanded and the thing breaks
Then they call you out of the blue and say, please fix it!
Access is an evil which should die. Advocates of it are welcome to come debate the matter with me. I need fresh meat.
Excel is extremely powerful and a handy tool, but as soon as anyone adds a datasource they should come and debate the matter with me.
I know of one (sort of). His church elders had an issue working at a betting company so he resigned.
So I suppose you can say he caved into peer pressure, instead of his own personal morals.
I've been asked to reverse engineer / crack / hack and decrypt stuffs by some of the companies I've worked at.
I don't have an issue with it.
I also would not use any of that for personal gain.
(Well I gave myself 10 bucks to prove to them their secure credit card page was not as secure as they thought it was, but I gave it back).
He was a script kiddie wannabe.
No I did not (I have now however)
It's not often that I get to throw in a bash quote.
Couldn't help myself.
I never said it was the best OS ever made.
I said that is what they are used to, comfortable with and unwilling to change from.
See how long you stay in business by force feeding your users with something they don't want, or in fact don't need because XP works for them.
I agree totally with what your are saying about security etc.
But if you don't give your users what they want (not NEED, but WANT) then shortly thereafter you won't have any users and it becomes a moot point
Because someone else will step in and give them what they want.
The best you can do is present to them the risks of running unsupported software etc and hope they make the right call.
Clearly you work in a cubicle farm with someone in charge making the right decisions instead of dealing with users who are paying you and refuse to change.
WTF? I did this a day or two ago! No issues.
We have some legacy software which requires VS 2003 to make changes (SDK only works with 2003 and XP)
Fired up a new VM, installed XP, ran updates, installed VS 2003, installed SDK, opened solution, fixed references, build, success, made minor changes, build, succes
Done
You are forgetting about people's comfort zone. XP works, they know how to change their settings for whatever.
The drivers for their XYC device install and work
The ancient app that they use to do their books/orders/whatever work
Old office (before the ribbon bar) works, and they know it backwards
IMHO MS are being fcking stupid by trying to force people off XP by no longer supporting it. When it becomes clear that they have to upgrade because of all the vulnerabilities that have now been left open people are going to upgrade. But will they upgrade to an MS OS?
Drop support for XP when the user base has become negligible, not when there are still billions of users.
People DO NOT LIKE CHANGE (except from vending machines)
Oops, soz. Meant to reply to your query but got distracted by your sig.
:-)
Yes I went to school in a former British colony, so it's British English and British Law
In hindsight I think it was more about my teacher being British herself which made me lose points due to American spelling.
Then again I almost always scored 95+ on essays, she had to find fault somewhere?
English is easy, you just have to read a lot.
Clearly you did not follow any of the links in theshowmecanuck's post.
While you may have made it more uniform all you are doing is muddying the water
And what's with your crappy date format (m/d/y) it causes untold grief in the computer world
And fucking switch to metric already
Knock Knock
Who's there
9/11
9/11 Who?
YOU SAID YOU'D NEVER FORGET!
Bash Quote
Valid point, sad but true.
Also I suppose I am leeching knowledge of these sort of things (proxies et al) into my children since they were five.
I keep overestimating the typical user.