1,675 karma · joined June 2, 2017
This goes for non-fiction but also for fiction. As a fiction author I do relish being read and appreciated by the right people. However, the gratification I get from that is mainly an ego thing, whereas the gratification of producing something that I find complete and beautiful (that sense of rightness washing over you when you put in that final period) gives a deeper fulfillment.
I hope and suspect so, but taste is a fickle thing. It may be hard to believe but Bach, nowadays considered by many as the greatest composer ever, almost faded into obscurity.
In my first year of college I had to write a short essay for an English course. I was rather lazy as well as a fan of wordplay so I wrote an essay describing the life and work of an obscure 19th-century philosopher, who also happened to be completely fictional. Since I could just pull the "facts" out of my ass, it was easy to write.
A week later I was called in by the English department and had a sit down with two grim looking teachers. They confronted me with suspicions of plagiarism. Most of their case was built on my use of the word "gamut", which they thought a 19-year-old non-native speaker was not supposed to know. I was incensed (as well as flattered), but they only relented after I pointed out that the essay was an acrostic. The first letters of the paragraphs spelled the word "humbug".
Maybe the problem is that Dutch "resources" are easily Americanized. The American and Dutch ways of doing business are not that different in style, just in scale. I suspect many Dutch entrepreneurs secretly think that if they just act a little more American, they can cut through the red tape and get things done. That may work on some levels, but not in Dutch politics.
This may point to a culture clash, a misreading of Dutch values. Dutch business is widely known for its matter-of-factness not to say bluntness, Dutch politics is known for "polderen", the grinding process of seeking compromises between all parties involved. It seems like Meta may have confused the two.
Frankly your confession disturbed me a bit. Not because you (and doubtlessly other people) do it, but because I read the comments you cited and the lying is convincing enough to fool me.
I realize I have fallen for the naive idea that after almost 30 years of internet I have become inoculated to the BS floating around, as if I would have developed some kind of superpower. Thank you for the reality check. :-)
Your behavior seems less like trolling to me than some kind of appropriation: like a healthy person going online pretending to have cancer to get affection and support.
Exactly. When I was a teenager in the 80's the kids in school came in three classes: the majority who did not know what computers were or thought they were lame, a minority who dabbled in the nascent gaming scene and an even smaller minority (of maybe 5 people in a school of 1500) that was interested in programming a computer. I happened to be part of the latter minority.
The gamers were all about getting the newest (cracked) games as quickly as possible. Meanwhile we were cutting our teeth on the internals of the c64. While we were lousy gamers with zero connections, we had a certain amount of respect in the gamer community because we were actually capable of programming the intro's to their cracked games. In return we got to feed on their scraps, so there was a living in that. :-)
Fortunately his plans never came to much because of fierce opposition. They are representative of a certain way of thinking at the time though.
The book is a somewhat systematic tour of the smells of the world. Most of which are generated, one way or another, by organisms. It makes you realize that (because of this simple fact) the world is an even more special place than you already thought: most of the smells in this world probably exist nowhere else in the universe.
The book makes you see (smell) the similarities between things as disparate as a pine trees and lemons, melons and fish, ants and ginger, and it explains why they exist. You come out of the experience with a rich new vocabulary and a plethora of fascinating facts.
The book is a bit technical (lots of high school level organic chemistry) but it is a joy to read, because McGee is a very good writer who manages to be precise and lyrical at the same time. A book to savor slowly.
True, but mentally balancing parentheses is usually something that you do while writing the code: you pushpop a little stack in your head and this becomes second nature.
Mentally verifying if parentheses are balanced while reading code is hardly ever required. You can usually safely assume that they are (unless that darn compiler tells you otherwise).
I can imagine more useful highlighting than color coding the types of the symbols encountered. Lighting up the active scopes. Giving the same hue to names that look like each other. There are probably highlighters out there that do that. But "simple" syntax highlighting is still the norm.
(I appreciate the complexity of the problem, btw)