|
In this article I digested a number of MapReduce patterns and algorithms to give a systematic view of the different techniques that can be found on the web or scientific articles. Several practical case studies are also provided. All descriptions and code snippets use the standard Hadoop’s MapReduce model with Mappers, Reduces, Combiners, Partitioners, and sorting. They MapReduced all the MapReduce.
|
|
|
|
|
This is my attempt at distilling software engineering into 20 tweets (less than 140 characters). Not entirely sure that it is wholly satisfactory. Please try your own! Zen mind. Programmer mind.
|
|
|
|
|
Twitter is great and, hopefully, it will grow into an even better product that makes us happy to use it. But the real-time web is the future, and It’s time we make sure that it isn’t dominated by a single option. Are projects like App.net bringing a better future?
|
|
|
|
|
I'm still waiting for an ad-free version of Code Project that is supported by membership fees.
|
|
|
|
|
|
HyperCard was a groundbreaking, beautiful, and even thrilling app. Ahead of its time for sure. But the time it was ahead of seems to me to be not so much the Age of the Web as the Age of the App. I don’t know why there isn’t now an app development environment that gives us what HyperCard did. Apparently HyperCard is still ahead of its time. Apple killed off HyperCard in 2004, but it remains more than a fond memory to many of us.
|
|
|
|
|
I remember HyperCard and SuperCard. Frankly, they were nothing more than souped up software punch cards. They were not ahead of their time, or everyone would be using them. They were a step back, a novelty. Everything limiting about HyperCard was said of HTML 4.0 prior to AJAX.
m.bergman
For Bruce Schneier, quanta only have one state : afraid.
To succeed in the world it is not enough to be stupid, you must also be well-mannered. -- Voltaire
In most cases the only difference between disappointment and depression is your level of commitment. -- Marc Maron
I am not a chatbot
|
|
|
|
|
OpenSubdiv is a set of open source libraries that implement high performance subdivision surface (subdiv) evaluation on massively parallel CPU and GPU architectures. This is the same code that Pixar uses internally for animated film production. Our intent is to encourage high performance accurate subdiv drawing by giving away the “good stuff”. Lights, camera... render!
|
|
|
|
|
Picture doing a remote software upgrade. Now picture doing it when the machine you're upgrading is a robotic rover sitting 350 million miles away, on the surface of Mars. That's what a team of programmers and engineers at NASA are dealing with as they get ready to download a new version of the flight software on the Mars rover Curiosity, which landed safely on the Red Planet earlier this week. Just what do you think you're doing, JPL?
|
|
|
|
|
|
With all the legal and privacy issues, and now this, will facebook continue to thrive. Will other companies break into the market?
|
|
|
|
|
It might look silly to read through two tutorials to finally control a LED with your iPhone. Oh and it would be useless too. So why are you doing that? Well, an instructor at my university once said: “If you can control a LED, you can control ANYTHING”. And guess what, he’s right! Basically, turning a LED on or off is just like switching a Fan, TV, Dishwasher, or any other device. So for simplicity we’re gonna use a LED. But if you can get this working, then you can control anything. When I was a kid we used discrete components to control a lightbult... and we liked it!
|
|
|
|
|
Logging is important. Very important. When your application breaks, the first place you usually check for a hint of what went wrong is the logs. Unfortunately, I have found that most log messages are absolutely terrible. They include snarky comments, lack any indication of what was going on, and sometimes do not even include the current time. Based on my experience, here's what a good log message looks like... Could not complete this subhead due to unspecified error.
|
|
|
|
|
Seems like logging is not much emphasised. I think that the logs should be very readable. It may not be a programmer that is reading them.
|
|
|
|
|
I agree, they should be as clear as possible
|
|
|
|
|
I’ve been racking my brain for a week straight on the best way to employ test-driven principles to HTML. Hell, I’ve been trying to figure out if it even can be done. Trying to figure out if it’s even worth it. Mostly through blind faith, I’ve come up with the beginning of what I hope becomes a winning strategy for test-driven HTML development. If you can write it you can test it. Hopefully.
|
|
|
|
|
“Management is the craft of enabling people to get things done.” Why is management a craft? It’s a craft for the same reasons engineering is a craft. You can read all the books you want on something but crafts are learned by getting your hands in it and getting them dirty. Crafts have rough edges, and shortcuts, and rules of thumb, and things that are held together with duct tape. The product of craft is something useful and pleasing. Don’t become an engineering manager because you want power - that’s the worst possible reason.
|
|
|
|
|
Bottom line is: when you find #000000 in your color picker, ask yourself if you really want pure black. You’re probably better off with something more natural. And if you’re feeling adventurous, try staying away from the left edge of the color picker altogether. It's like, how much more black could this be? and the answer is none. None more black.
|
|
|
|
|
I can't say I understand most of his reasoning...then again, I'm not a designer. Personally, I like things to have black backgrounds, it makes things stand out without the need to burn white backgrounds into my retinas.
|
|
|
|
|
lewax00 wrote: I can't say I understand most of his reasoning
He explained it quite clearly I have to say.
Wout
|
|
|
|
|
The clarity of his explanation isn't the problem, the problem is it just doesn't make sense to me. Don't use black because it's not natural? Neither is a computer screen, or most of the things displayed on it. (Ever see a Start bar wandering around on it's own, detached from a computer? Not likely.) Especially when his example is the work of a single painter, who is painting scenes that can be found in the real world. It's apples and oranges.
modified 10-Aug-12 10:05am.
|
|
|
|
|
Well it does make sense. Perhaps a screen is not natural, but your eyes and your brains are, so the designer should attempt to design things such that they are pleasant and easy on the eye and brain. The screen is just a medium, it could just as well be paper, T-shirt, or a painting as the author showed. In painting using blue in shadows is actually very common, it is not just this one painter that does this. Just that one example is shown, doesn't mean other painters do not do this. The reason they do this is that there is actually more blue in shadows. This is because the sky is blue, and where direct sunlight doesn't hit a spot, the blue light from the sky will.
There's nothing against using high contrasting bright colors at the extreme ends of the spectrum, but it will tire the eye and brain. His way of picking optimal brightness/saturation values is quite intelligent. Going to either 0% or 100% would be very unsubtle. Things on the screen may not be natural things, but still they go through your eye and brain, and you can't get around how they work. E.g. sharp edges are less pleasant to look at than round edges. Sharp objects can possibly hurt you, so there is special circuitry in the brain to detect that. Bright high contrasting colored animals are usually very dangerous or poisonous.
Also most people don't have the brightness + contrast settings on a screen at 100%. Might be pretty to look at for perhaps 2 minutes, but after an hour your eyes would start to burn.
Wout
|
|
|
|
|
wout de zeeuw wrote: Just that one example is shown, doesn't mean other painters do not do this. The reason they do this is that there is actually more blue in shadows. This is because the sky is blue, and where direct sunlight doesn't hit a spot, the blue light from the sky will.
The number of painters wasn't my point. How many computer screens are lit primarily by the sun & sky? It makes sense when painting a landscape or some other natural model, but again computers are not. Instead of trying to hide the differences by pretending one is the other, the uniqueness of the virtual environment should be embraced and utilized, not hidden away.
Also, even darker blacks can be found in nature. Have you ever been deep inside a cave system, where the sun doesn't reach, and turned off all artificial lights? That's much blacker than a computer screen will ever be (mostly because of the back light).
|
|
|
|
|
Quote: lewax00 wrote: <layer>The number of painters wasn't my point.
It does appear so from:
Quote: Quote: Especially when his example is the work of a single painter
Hence the reaction about it not being one single painter's creation, but a general natural phenomenon.
Quote: lewax00 wrote: How many computer screens are lit primarily by the sun & sky?
The author is using examples to clarify a more general observation about how the brain interprets color. The point the author was trying to make, even when you think you're seeing black, or seeing gray, it is almost never a pure black or gray. So when making a design, the objective is using a generally color scheme to get a particular effect (e.g. appearing gray). He quite clearly demonstrates with examples how far you can deviate from pure greys while your brain still thinks the color is grey. So even when designing a grey theme it wouldn't be necessarily a good idea to limit oneself to the pure black and greys (just like painters do).
lewax00 wrote: Instead of trying to hide the differences by pretending one is the other, the uniqueness of the virtual environment should be embraced and utilized, not hidden away.
I don't see where the author is hiding or underutilizing color. He is doing quite the opposite, through understanding of perception of color he is intelligently choosing appropriate colors to achieve a certain effect, rather than limiting himself to pure black and greys.
Wout
|
|
|
|
|
wout de zeeuw wrote: I don't see where the author is hiding or underutilizing color.
The title is "Design Tip: Never Use Black". Never. Not "avoid it in certain cases", not "use it when it's appropriate", but "never". He's saying to avoid using a section of the color space on computers simply because it isn't as natural as other choices. And I don't think that's correct. I'm not saying black is right for everything, but it does have very appropriate uses in a virtual environment.
|
|
|
|