If you have a backend routing your image request, it's as simple as counting the request and save the count somewhere, along with meta info for that specific image.
neat insight! A friend of mine convinced me to try React, though I can't say that I'm sticking with it. Besides the mix syntax, my take was it's just another way of building the UI.
My breaking point was when it breaks all my jshint and jscs grunt tasks :) So now I'm migrating to use RactiveJS instead (same virtual DOM diff) with the addition of Mustache as a full template engine, which is what we actually need :)
Dead wrong. All these tools require a very different way of abstract thinking away from the usual "press this button, machine will do this", and learning how to code (one way) will trigger the right part of your brain to help using these tools more efficiently.
There are many types of coders. If you're doing hardcore statistic and magic on your screen, it doesnt mean building a simple website and/or implemente a tracking call to GA (in case of a growth hacker) is any less important.
I have to disagree. Both statistics and economics requires understanding of Math, which lives on the same side of the brain that's needed for understanding logic, thus coding falls into the same bucket. Though I suspect you're refering to "understand coding" as "understand complex algorithm". In which case, I agree because there are many type of coder, and some of which doesnt neccessarily needs to "understand and/or write complex algorithm".
Here's the context... Someone with moderate statistics can take a Microeconomics class and with a few hours a week of studying can get conversational, and apply it. With only introductory calculus, they can take a second and third class, and know enough to be professionally employed in the field. 90% of the folks who start the first class can take the 2nd and 3rd.
3 classes isn't enough for competence in coding, and much less than 90% get out of the first class.
That's because we have 12 years (in the US) of general math studies to prepare us for stats and calculus. Integrate programming into the sciences and math courses (physics and geometry have obvious points for integration, I'm less certain about the others) and a first course in programming will actually be able to get students much further than they often do today.
Had this happened to me a while back. They don't completely "delete" your stuff, just disable access to it. After contact support and the admin of the account, everything is sugar again.
A designer's job is not about using tools to make things look good. A designer job is to make decision about how things work together. And because of that, this post title pissed me off. If you're talking about a visual tool, talk about the tool, don't say you can design without designer.
+1 and yet, most arguments will end up toward the direction of "platforms consistency," especially on Facebook-related application since they have it "OK" | "Cancel" order.
I agree that in the long run it would be better for users; yet as a user, I'm used to clicking on the Okay button on the left. Every time I see one isolated application with the Okay button on the right, I'm going to have a slower/harder time knowing which button I need to press.
If one of your users uses 50 applications, and he uses yours once in a week, he's going to be annoyed at your application for being different; even if that "different" is supposedly better, reflexes have taught the user to scan the buttons in a certain way.
I'm not suggesting that the order we have now is better; but until one of the OSs or an application like Facebook moves to the "better" button order, I can't see why a designer might do so for his own application.
Android changed the order of positive/negative buttons in dialogs with 4.0 and it took me ages to get used to the new order. Just stick with the platform default, please: it's what users expect.
I agree, platform consistency is more better for your app than following something which is theoretically better. I'd be reticent to change the Ok -> Cancel order without some harder evidence than this.
