Paul Graham wrote a very informative article about "news stories" like this one many years ago. And congrats to the company behind RunRev, it is not that often/. runs slashvertizements for costly commerical software no one has ever heard of.
You are not using Ubuntu. One of the reason PA gets so much flack is because Ubuntu and certain other distros shipped asla configuration files which didn't work very well with PA. Of course the distributors are not Linux audio experts (most of the package maintainers are volunteers, as you know), so if the "path of least resistance" leads to a broken PA, then at least I would partially put the blame on PA.
The PA experience has been much better on Fedora which is not so strange considering that PA's main author is also a Red Hat employee.
How about the Vikings settling North America (Canada) and calling it Vinland because you could grow grapes in it around 1000 AD? Or settling areas of Greenland that were later covered by ice and only now being uncovered?
The grapes were likely Vitis riparia which still grows in Canada. The name Greenland was the name given to the island by its discoverer Erik the Red who wanted to persuade others to settle there. As opposed to the name "Iceland" which was given by the original inhabitants to discourage others from settling there. This is all covered in Wikipedia and you can yourself fact check it in 5 minutes using google. And it is very dishonest of you to bring up the same discredited bullshit that always comes up when GW is being discussed.
Cry me a river. The medias role is to enlighten and educate, not being a bunch of whiny bitches presenting whatever "view" their corporate masters want them to. If they can not plainly state that Obama's speech is the closest thing to "fuck you China" any US president has ever come, then they don't deserve to be called media because they have thoroughly failed.
That's great, until your huge refactoring introduces a new bug. And
it will, you can't expect to refactor a decent sized body of code
without breaking something. When it does, it doesn't matter that the
code is 100 times more readable and extensible, or that you fixed ten
other bugs while doing it, your ears will get hot. Because you broke
something which means more work for someone else and that the count of
outstanding bugs was just incremented.
This happens in the places where each bug report has to be
annotated with about two dozen different abbrevations and numeric
codes so that the correct departments and bug examiners will get to
look at it. When it takes two hours to file bugs and each bug has to
be examined by four persons, you can forget about filing bugs about
"potential problems." Bug reports are for the issues customers have
complained about and nothing else.
What about the next bug report that comes on? If it can even
remotely be associated with the new code you wrote, then it will
be. Because yours is the only new code in what is otherwise a totally
legacy code base with hundreds of band aids. Expect to take the
blame.
And then you have the original author of the body of code you just
killed/refactored. He wont be so amused about you rewriting in one
week what he spent four months writing. Expect to hear nitpicks and
complaints from his side. You won't be able to ask him anything about
the code anymore because "you destroyed it."
So yes, while refactoring code makes it better, you wont make many
friends while doing it and you are taking a huge personal
risk. Especially if you are doing it secretly.
Can you elaborate on that? The tracking pixels are used to report transactions to Bing's api by having the customers web browser doing a GET request to Bing's cashback server. Since it is all done on the client side, a malicious user could just include the MAC for the merchant in the forged transaction. So I don't see how using a MAC would help at all.
That's absurd reasoning. Oil can't be replaced with coal, it doesn't have nearly the same energy density and can not (efficiently) be used for transportation like oil. Without oil, a society dependant on oil will collapse. Frankly, I'd rather see that happen sooner than later. I'm under 30 which means that the oil will likely run out during my lifetime. The Americans wars for oil can't stop that fact. So I don't see what is hypocritical about pointing out that Bash and his junta are war criminals and 50 years ago men like them were hanged in tribunals?
Do you somehow believe that I, personally, have benefited from the Iraq war?
What bullshit. Considering that.Net basically *is* Java with all the stupid fixed, I don't think "server side" would be any "further along" without it..Net has properly implemented generics, closures, a truly multi-language capable vm and list comprehensions to boot. If it wasn't for.Net, Sun would never have gotten its act together and wouldn't have implemented useful new features for Java after letting it stagnate for several years. Truth is, Sun themselves fucked up Java by not supporting multiple-languages on the vm, waiting for to long to open source it, letting the JCP create broken specifications with incompatible implementations etc.
The correct analogy is an electronics company called McIntoshFun being sued by Apple Computer Inc. Because it would be ludicrous for a company to lay claim to a common word for an apple variety like that.
Um no. It is a miserable failure. After taxes they may be left with 60k tops, then deduct server costs, equipment cost and office rent. What remains is a miserable salary considering how much time they must have spent developing the game.
The data needed to transfer only grows exponentially if the server naively sends to much data to the client. Let's say there are 100,000 players in one spot. Using your numbers that would mean sending 100mb/s of traffic to each player. Obviously that won't work.
What if you rendered all the players data on the server and streamed it to them? Using high definition video that would mean sending "only" about 1.2mb/s per player. It is not a realistic idea, but the bandwidth need would now grow linearly with the number of players and not exponentially. Basically you can trade bandwidth with CPU processing like this.
Don't ask a fish how it likes to be catched. It is standard procedure for everyone to brush up their resumés, to highlight the good parts and try to hide the damaging ones. That is standard procedure not only for contractors but for everyone in the business. I'll wager to bet that whatever company you work for, they do the same thing with the products or services they sell.
Personally, when I have worked with head hunters, I've usually used multiple CV:s for each occasion. If we have a client looking for a Java developer, highlight my Java experience, read up on what the latest and greatest Java acronyms are (JDBC, JPA, JSTL etc). Same method if the client is after an embedded Linux kernel developer. I've also had to actively hide damaging facts such that I over 15 years ago grew up in a very "bad neighbourhood" or that I once was laid off.
The key part is to work *with* your head hunter(s) (use many, they are generally free until you get hired by a client) not against them like the OP seem to have done. You're like a team and you have a common goal. The commission and the salary. Correcting details an agency has given a client is just plain stupid. The asker could have easily avoided the situation by having "Zeke" send him the same documents he sent to the client. A sign of poor communication skills.
Always check what the head hunters send out. One who tried to sell me, failed to produce an interview in several months. I finally got to see what he was sending to the clients. Turns out he had thoughtfully rewritten all flowing text in my CV. To bad that he was dyslectic and had misspelled every other word.. My own fault for not checking it up earlier.
Bottom line: head hunters try very hard to sell you because the commission they get is ridiculous. Your CV is your advertising for a product which is you.
No, you are not committing click-fraud, what gave you that stupid idea? The point of cookie-tracking is that the advertisers can not defraud the merchants.
Loonies like you, who deny cookies, are still counted because the merchant can tell, when you make a purchase, whether you have an affiliate cookie set or not and people who deal with this kind of marketing are well aware of that cookie-tracking under counts what the affiliate delivers.
Which is why the provision given to the affiliate is very high. E.g. a porn site may pay an affiliate the monthly subscription price times three for each paying subscriber recruited using a cookie-tracked ad, or about 60$. The payout for a click on a porn sites ad is much less, generally from 1-10 cents.
Tracking users via cookies. When a user clicks an ad, it sets a cookie in that users browser. Then when that users makes a purchase/signs up, it can be shown that there is a direct link between the ad and the sale so the advertiser gets payed. That is how most serious ad networks operate these days.
It should also come as absolutely no surprise that a C++ pointer based linked list running native locally on the OS performs faster than a.Net Generics List running as CLR in the.Net run-time environment.
This is incorrect, just like the rest of your message. A list in a high-level language is almost always faster than a linked list in C++, because it is array-backed. The whole list is in one contiguous block of memory and iterating it means incrementing a pointer sizeof(int) bytes each iteration. Iterating a linked list on the other hand, means jumping around in memory following pointers for each iteration. Which is much slower and induces an enormous cache penalty.
This is basic stuff and just shows how futile using low-level languages is when people don't even understand why linked lists are slower than array lists...
You are pulling stuff out of your ass and have no clue about what you are talking about. Start your own publishing house if you think it is so easy, then you can too swim in cash. Good luck.
Slashdot Mirror
Paul Graham wrote a very informative article about "news stories" like this one many years ago. And congrats to the company behind RunRev, it is not that often /. runs slashvertizements for costly commerical software no one has ever heard of.
You are not using Ubuntu. One of the reason PA gets so much flack is because Ubuntu and certain other distros shipped asla configuration files which didn't work very well with PA. Of course the distributors are not Linux audio experts (most of the package maintainers are volunteers, as you know), so if the "path of least resistance" leads to a broken PA, then at least I would partially put the blame on PA.
The PA experience has been much better on Fedora which is not so strange considering that PA's main author is also a Red Hat employee.
Dude, your joke is getting stale.
How about the Vikings settling North America (Canada) and calling it Vinland because you could grow grapes in it around 1000 AD? Or settling areas of Greenland that were later covered by ice and only now being uncovered?
The grapes were likely Vitis riparia which still grows in Canada. The name Greenland was the name given to the island by its discoverer Erik the Red who wanted to persuade others to settle there. As opposed to the name "Iceland" which was given by the original inhabitants to discourage others from settling there. This is all covered in Wikipedia and you can yourself fact check it in 5 minutes using google. And it is very dishonest of you to bring up the same discredited bullshit that always comes up when GW is being discussed.
You are still wrong. Now either show us your sources proving that solar panels has a negative EROEI, or stfu and stop spreading dumb shit.
550W is about 0.74hp, not 75.
Wrong
I doubt you are working in a large company, in which case your naive attitude just wont fly.
And for what reason do we need people like you on this planet?
Cry me a river. The medias role is to enlighten and educate, not being a bunch of whiny bitches presenting whatever "view" their corporate masters want them to. If they can not plainly state that Obama's speech is the closest thing to "fuck you China" any US president has ever come, then they don't deserve to be called media because they have thoroughly failed.
That's great, until your huge refactoring introduces a new bug. And it will, you can't expect to refactor a decent sized body of code without breaking something. When it does, it doesn't matter that the code is 100 times more readable and extensible, or that you fixed ten other bugs while doing it, your ears will get hot. Because you broke something which means more work for someone else and that the count of outstanding bugs was just incremented.
This happens in the places where each bug report has to be annotated with about two dozen different abbrevations and numeric codes so that the correct departments and bug examiners will get to look at it. When it takes two hours to file bugs and each bug has to be examined by four persons, you can forget about filing bugs about "potential problems." Bug reports are for the issues customers have complained about and nothing else.
What about the next bug report that comes on? If it can even remotely be associated with the new code you wrote, then it will be. Because yours is the only new code in what is otherwise a totally legacy code base with hundreds of band aids. Expect to take the blame.
And then you have the original author of the body of code you just killed/refactored. He wont be so amused about you rewriting in one week what he spent four months writing. Expect to hear nitpicks and complaints from his side. You won't be able to ask him anything about the code anymore because "you destroyed it."
So yes, while refactoring code makes it better, you wont make many friends while doing it and you are taking a huge personal risk. Especially if you are doing it secretly.
Can you elaborate on that? The tracking pixels are used to report transactions to Bing's api by having the customers web browser doing a GET request to Bing's cashback server. Since it is all done on the client side, a malicious user could just include the MAC for the merchant in the forged transaction. So I don't see how using a MAC would help at all.
That's absurd reasoning. Oil can't be replaced with coal, it doesn't have nearly the same energy density and can not (efficiently) be used for transportation like oil. Without oil, a society dependant on oil will collapse. Frankly, I'd rather see that happen sooner than later. I'm under 30 which means that the oil will likely run out during my lifetime. The Americans wars for oil can't stop that fact. So I don't see what is hypocritical about pointing out that Bash and his junta are war criminals and 50 years ago men like them were hanged in tribunals?
Do you somehow believe that I, personally, have benefited from the Iraq war?
You're a retard.
What bullshit. Considering that .Net basically *is* Java with all the stupid fixed, I don't think "server side" would be any "further along" without it. .Net has properly implemented generics, closures, a truly multi-language capable vm and list comprehensions to boot. If it wasn't for .Net, Sun would never have gotten its act together and wouldn't have implemented useful new features for Java after letting it stagnate for several years. Truth is, Sun themselves fucked up Java by not supporting multiple-languages on the vm, waiting for to long to open source it, letting the JCP create broken specifications with incompatible implementations etc.
The correct analogy is an electronics company called McIntoshFun being sued by Apple Computer Inc. Because it would be ludicrous for a company to lay claim to a common word for an apple variety like that.
Um no. It is a miserable failure. After taxes they may be left with 60k tops, then deduct server costs, equipment cost and office rent. What remains is a miserable salary considering how much time they must have spent developing the game.
So that Slashdot will have something about it to write, to generate buzz about this new "iTunes LP" thing no one has ever heard about.
The data needed to transfer only grows exponentially if the server naively sends to much data to the client. Let's say there are 100,000 players in one spot. Using your numbers that would mean sending 100mb/s of traffic to each player. Obviously that won't work.
What if you rendered all the players data on the server and streamed it to them? Using high definition video that would mean sending "only" about 1.2mb/s per player. It is not a realistic idea, but the bandwidth need would now grow linearly with the number of players and not exponentially. Basically you can trade bandwidth with CPU processing like this.
Can we presume you have a degree in game design then.
Don't ask a fish how it likes to be catched. It is standard procedure for everyone to brush up their resumés, to highlight the good parts and try to hide the damaging ones. That is standard procedure not only for contractors but for everyone in the business. I'll wager to bet that whatever company you work for, they do the same thing with the products or services they sell.
Personally, when I have worked with head hunters, I've usually used multiple CV:s for each occasion. If we have a client looking for a Java developer, highlight my Java experience, read up on what the latest and greatest Java acronyms are (JDBC, JPA, JSTL etc). Same method if the client is after an embedded Linux kernel developer. I've also had to actively hide damaging facts such that I over 15 years ago grew up in a very "bad neighbourhood" or that I once was laid off.
The key part is to work *with* your head hunter(s) (use many, they are generally free until you get hired by a client) not against them like the OP seem to have done. You're like a team and you have a common goal. The commission and the salary. Correcting details an agency has given a client is just plain stupid. The asker could have easily avoided the situation by having "Zeke" send him the same documents he sent to the client. A sign of poor communication skills.
Always check what the head hunters send out. One who tried to sell me, failed to produce an interview in several months. I finally got to see what he was sending to the clients. Turns out he had thoughtfully rewritten all flowing text in my CV. To bad that he was dyslectic and had misspelled every other word.. My own fault for not checking it up earlier.
Bottom line: head hunters try very hard to sell you because the commission they get is ridiculous. Your CV is your advertising for a product which is you.
No, you are not committing click-fraud, what gave you that stupid idea? The point of cookie-tracking is that the advertisers can not defraud the merchants. Loonies like you, who deny cookies, are still counted because the merchant can tell, when you make a purchase, whether you have an affiliate cookie set or not and people who deal with this kind of marketing are well aware of that cookie-tracking under counts what the affiliate delivers.
Which is why the provision given to the affiliate is very high. E.g. a porn site may pay an affiliate the monthly subscription price times three for each paying subscriber recruited using a cookie-tracked ad, or about 60$. The payout for a click on a porn sites ad is much less, generally from 1-10 cents.
Tracking users via cookies. When a user clicks an ad, it sets a cookie in that users browser. Then when that users makes a purchase/signs up, it can be shown that there is a direct link between the ad and the sale so the advertiser gets payed. That is how most serious ad networks operate these days.
It should also come as absolutely no surprise that a C++ pointer based linked list running native locally on the OS performs faster than a .Net Generics List running as CLR in the .Net run-time environment.
This is incorrect, just like the rest of your message. A list in a high-level language is almost always faster than a linked list in C++, because it is array-backed. The whole list is in one contiguous block of memory and iterating it means incrementing a pointer sizeof(int) bytes each iteration. Iterating a linked list on the other hand, means jumping around in memory following pointers for each iteration. Which is much slower and induces an enormous cache penalty.
This is basic stuff and just shows how futile using low-level languages is when people don't even understand why linked lists are slower than array lists...
You are pulling stuff out of your ass and have no clue about what you are talking about. Start your own publishing house if you think it is so easy, then you can too swim in cash. Good luck.