181 karma · joined June 27, 2012
This is clearly forbidden by NC.
Something very similar to this exists: A version of Origin of Species with a 50-page rebuttal attached: https://www.google.com/search?q=creationist+origin+of+specie...
Do you speak Hindi? Russian? Why not these too? Are you too busy just learning Japanese?
[0] (well, justifiable homicide, anyway)
They didn't say "screen images simulated" because they weren't showing a screen.
Every camera ad shows fake footage. Example:
http://www.amazon.com/Samsung-Megapixel-Digital-Optical-Stab...
That's the second "#.blahId.websiteName" tracker hash I've seen today. What product/pattern is that?
> The better you write, the higher you go in Ogilvy & Mather. People who think well, write well.
Most of this advice applies to coding as well (with some liberties...):
1. Read Effective Java / Effective Go, etc
2. Use normal idioms of the language, not clever constructions.
3. Short variable names, short methods, short classes.
4. Don't force "Patterns" into your code unnaturally.
5. 1000 lines to a file, max.
6. Check the APIs you use (at least the docs), that they do what you want them do.
7. Don't submit code the day you write it in a fury of creation. Sleep on it and review it the next day, and clean it up.
8. Code Review.
9. Write clear understandable code, not just code that you fiddled until it compiled and ran.
10. Don't just send an email and expect the reader to act. Talk to the person to get their commitment.
That's not very secure. Why not send the password directly to the input manager (as keyboard events or what-have-you), so the password only is seen by the app that needs it, instead of every app the user is running?
I guess the target audience is programming novices who have never written anything like source code before. Go seems like a strange choice for a first language, being neither foundational (C, Assembler, Scheme/Lisp) nor front-end scripty (JS, Logo, Scratch).
uch a tease:
The excellent Amit Singh rants about how useful procfs is and how Mac doesn't have it, but then says it's not really needed, and then almost builds it anyway, then gives up due to unrelated hardware problems:
http://osxbook.com/book/bonus/ancient/procfs/
(2003)
This case is one of the more blatant demonstrations showing the superiority of The Unix Way of "everything is a file. "