all of those are so silent, so invisible and kill or hurt so many more people.
120 karma · joined July 22, 2012
all of those are so silent, so invisible and kill or hurt so many more people.
1/ When a coder thinks about writing "if a <= b", then he writes "if a <= b", he easily forgets that he should write "if a <= b + epsilon()"
2/ When people are faced with "I have to have this number with 2 decimals", they sometimes write a = round(a * 100)/100; forgetting that 'a' is a float (or double), and then they completely forget that the new 'a' is just not accurate.
3/ Issues with floats arise on simple operations such as addition. And people tend to think that simple operations have no rounding issues.
It'd be perfectly valid to work with floating point for money; but then you have to take care of the rounding issues much more often than with fixed point (or BigDecimal if you're in the java world). Once you use those BigDecimal, addition becomes safe, and "manual" rounding works as expected (when you round to 2 decimals, you get exactly 2, not an approximation).
So, after project managing several teams of developers, I can safely say that although F.P. can be fine, most people can't handle the mental load of thinking about rounding issues on each math operation they do (and "most people" includes myself). That's a human risk management issue, not a theoritical one.
"optional" like you have the choice in this free society : or you wear the damn badge or well, you find another job. But hey, you have choice, you have freedom.
ahahahaha !
>>> workers were given personalized dashboards that benchmarked their performance against that of the group.
rotfl:-) so you can reduce a human to a few metrics ?
>>> "The minute that you get the report that you're not speaking enough and that you don't show leadership, immediately, the next day, you change your behaviour,"
Hiring sheeps at Deloitte ? If they behave like that, they're not far away from Pavlov's dogs !
>>> "It's powerful to see how people want to display better behaviours or the behaviours that you're moving them towards."
Oh that little powerless, fragile geek now has a sense of POWER ! ah he's going to RULE the word. I'm sure he had got that little org4zm
>>> Generally, though, most companies are using these tools for positive ends
Ah, "generally" like 5.00001 out of 10 ?
Ah, it's for real ?
ouch
real like real ?
double hand palm :-(
damn... I really do have to find another planet, is there still room in the next human-without-return Mars mission ?
stF
I don't care if 20% of money goes back to research. I care that pharmaceutical companies use various means to "protect their assets". I once worked for Johnson&Johnson. Guess what was wirtten on every single desk there ? "We work for the good of our patients and investors". That is, patien on the same level as investor. For me, this doesn't sound like a sucess for humanity. That looks like the best of the worst solutions.
Python doesn't need such articles, that's for sure. If you want to use Python to write JavaScriptish web front end, then you're just going the wrong way. Just use JavaScript and that'll be so much easier.
believe me, we don't have millions of those ready. Many can code, but code in "real" life where you don't have luch room to learn from mistakes, well, there ain't many...
For me unicode was the reason to switch to 3, not everybody lives in an english-only world :-)
Basic income will make less poor but more slaves. Slaves that will be dependent on those (I assume it's the state) who define the exact amount of that uncondional income. Since a huge part of the population will be out of the "producer", thus the producer will have more power.
What must be done instead is to make sure power doesn't get concentrated. But this means less efficiency : one big optimised company is surely more efficient that ten smaller ones. With less power, the workforce can still negociate, the workforce can still share the remaining work, those who have no job still have a chance to get one if they want/need to. With basic income, there's no need to do that anymore...
So I don't like that basic income.
For example, there's a lot of unemployment in my country. People gets some allowance to live. The problem is that the lack of work is not acknowledged => those people are stigmatized. Anyway, they do get an allowance, kind of your basic income. The problem is that because of the unemployment, the employer are in a very strong position to pay people less (since many do want/need a job). So work valuation diminishes...
Competition is the problem, if companies would compete less, then basic income could work. There would be more space for choice : do I work or not ? can I share my work ?
Basic income means : let's detach ourselves from the consequences of competition.
- lots of information is ambient at the team place - because not all people are that concentrated at home - because working alone is difficult sometimes (especially when you're under stress) - because you're harder to contact (yes, some people are afraid to call a colleague at home) - because people don't like to have 4 simultaneous chat sessions with colleagues
So a day of remote work certainly help, but I'd venture to say that's a maximum for many. Of course there are people who a re remote 100% of the time, but not everybody can do that. You have to love your work for that, and many people don' t /love/ their work...
I totally agree. That's weird to see the n+1-th geek discovering something people have been doing since the dawn of humanity.
Damn, we're just talking about basic cooking. I understand many of us didn't learn the basics, but nonetheless, it's basic.
Imagine somebody saying he discovered "patterns to ride a bicycle" and explaining how to go from A to B with a regular bike in the most obvious fashion...
If you have backups, upgrade, access to monitoring tools, etc. 125$ / month is just 2 hours max of developer time.
That's a bargain and your standard Oracle admin should just feel threatened :-) (provided the company is willing to put its data on a server far away of its control room, which, I guess, doesn't happen so often :-))
so a bargain if you actually can make use of it...
ouch !
stF
I cracked a few games, looked at someone else's code but I can assure you that at the ASM level, it's very hard to understand that phong-shading routine to the point you can actually re-code it yourself...
(yes, I've tried :-))
stF
stF
I also cracked Ultima 6. That took me 3 days of intense work. The protection was hidden in the dialog engine. So you were not seeing the actual code, but the interpreter of dialogs actually interpreting the protection in the dialog engine (that was a super simple interpreter, more like a state machine). In the end, it was just a matter of understanding the dialog data and extracting the answer to the protection question ("on page 34, what is the third word ?").
I also cracked some football game by writing a program that would intercept disk access and the replay the disk-errors to cheat it. An emulation layer if you like.
The games that I've never cracked were Elite 2 frontier (the damn thing had checks all over the place and that was too hard); "le manoir de mortevielle" had super nasty decryption stuff. IIRC they were running decrypting code inside the interrupt table (so if you had to use the keyboard or timer to trace the code, then woosh :-)). I also went mad on Leisure Suit Larry were the protection was written in an interpreted language. At that time I was 16 or 17 and had no idea of what an interpreter was = >I've never understood the scheme :-(
You had also games with special messages in it such as "we worked very hard on this so don't crack us).
But the best thing I've seen is when I've tried to look into a already cracked game .the previous hacker Mr. Detergent I think, send a message along the line of "you're weaker than me". I Was sooooo upset :-)
I guess I cracked 20 or 30 games on PC. Most of them were very simple. But in the end things were getting harder. I had to use the Soft-ICE debugger (massive thing :-)) and then, well some had these hardware debugger and came the protected mode and, well, I got lost and started working on more creative stuff (Imphobia if one remembers :-))
stF
But then again. If I read well, he wants to 1st sort the points, 2 iterate over them and using the heap. So we have n log n for the sort and n * n log n for the heap use.. Basically (1+n) n log n (or i'm still tired ? :-))
On the other hand, designing pure algorithms is about figuring a solution for a given, canonical and often unforgiving problem (quicksort, graph colouring ?). To me, this is much harder. It involves quite the same amount of creativity but somehow, it's harder on your brain : no you can't cheat, no you can't linearize n² that easily :-)
To take an example. You can make "convincing" 3D on a C64 in a demo because you can cheat, precalculate, optimize in various way for a given 3D scene. Now, if you want to do the same level of 3D but for a video game where the user can look at your scene from unplanned point of views, then you need to have more flexible algorithms such as BSP trees. So you end up working at the algorithm/abstract level...
A very good middle ground here was Quake's 3D engine. They used the BSP engine and optimized it with regular techniques (and there they used the very smart idea of potentially visible sets) but they also used techniques found in demo's (M. Abrash work on optimizing texture mapping is a nice "cheat" -- and super clever)
Now don't get me wrong, academics is not more impressive than demoscene (but certainly a bit more "useful" for the society as whole) These are just two different problems and there are bright minds that makes super impressive stuff in both of them...
stF
http://www.taschen.com/pages/en/catalogue/art/all/01777/fact...