You could probably rewrite that as "not Silicon Valley". Or is there some other location you have in mind that could also support "hypergrowth"?
406 karma · joined December 18, 2012
You could probably rewrite that as "not Silicon Valley". Or is there some other location you have in mind that could also support "hypergrowth"?
> especially when he complains about being tired all the time
He never said he complains all the time. He says he is tired; he did not say he complains that he is tired all the time. So why did you immediately conclude he must complain all the time?
See, I read the point of the post as this: when you have a disease with no name -- no one can classify you as having a thing. You just have symptoms. I read his point as being that people sympathize with those who have a disease, but if you can't name your disease, it's almost as if you didn't have one. And hence his roommate who decided it'd be awesome to ride their exercise bike in his room as a form of punishment for not having a better sleep schedule. His roommate couldn't sympathize.
Here's an exercise: you know how recent security exploits all have fun little names? And how those exploits have all gotten fairly extensive press mentions as a result? Do you think they would have had the same if they were left nameless, as most exploits in the past were?
Way back when, when I first was learning C, I didn't comprehend it very well. I was OK with it. A friend gave me some CDs with FreeBSD on it, one with the OS, and one with program sources. It was that source code which really opened my eyes, and you could digest small programs (like chmod) and see, you know, this is working, production code, and it's not hard, and you can do this.
Tip #1: get a good knife. If you can, go to a store that'll let you actually hold a knife prior to purchase, to test its heft and balance. Find one that fits you comfortably. (I like Shun knives, but this is a pretty personal topic; don't let that be my personal endorsement so much as my personal choice.) The knife should be sharp, and you should keep it honed with a honing steel. Eventually it may get dull to the point where you might want a whetstone to sharpen it again, but you'd probably need to use your knife a decent amount before it gets to that point.
Tip #2: mis-en-place, which is French for, basically, putting things into place. Your mis is your work station. Clean your counters. Get out your cutting board. Have a bowl for food waste (e.g. the ends you cut off a carrot, the skin off a potato that you peel) and somewhere to put food once you have finished whatever you are doing.
Tip #3: prep work will make your life much, much easier. If the dish calls for diced onions, then you should dice your onions before you turn the heat on the stove. Having all of the vegetables chopped, things marinated, meat salted and spiced, whatever -- ahead of time -- will make the act of cooking about ten times less stressful than otherwise.
Tip #4: taste your food. Needs some salt? Add salt. Maybe some pepper will make it pop. This is a hard thing to quantify; how things taste and what you think you will need is partly your palate, which you can develop beyond what it is now, but some stuff (salt makes things taste better -- to a point, beyond which it just makes things taste like salt) is universal. Just don't be afraid to try some things, in small measures at least, and taste it to see where it's at.
Email and letter-writing go together, in my mind. Not so much because email is a literal model of letter-writing, but rather because they give you an important abstraction that I think we all need, which is a form of passive communication.
You may get letters which are urgent, and you may get email that is urgent, but the nature of both is that they are hands-off. You don't need to be present to receive mail or email. Well, there is some physical mail that you do need to be present for! -- that being certified mail, some package deliveries, and those represent perhaps a different abstraction. That aside, you have a mailbox to hold mail, and a carrier to deliver it to you. Nobody needs to talk to you, to tell you that happened. You can go and check your mailbox and see what you have at any time.
People who want to "kill" email may dislike the form, the implementation, but the abstraction is useful. It will likely continue to be useful -- I don't foresee a time when it will not be. Email, in some sense, will stick around.
No kidding. One of the party members, Geoffrey (who was a fighter and represented the virtue of Valor) is behind a locked door in a game where it's not entirely easy to buy keys to said doors.
My father, brother and I had the hardest time of finding the shepherd companion (Katrina). I think in the end we solved the problem by starting the game as a shepherd, which is basically "hard mode" as you have the weakest starting position (level 1 out of 8, whereas other starting characters begin at level 2 or 3), you can never use magic, and you start off on a small island near a ruined city.
Much later on, we found the damn shepherd, south of the starting point in said ruined city, entirely off of any road there.
But when you think back on how assembly looked and worked at the time, you realize that the line numbers are sort of analogous to addresses in memory. If you were on a 6502, you might JMP to a point in memory. You'd do the same in BASIC, except instead of a point in memory, it was an arbitrary number you used for the line.
So, weirdly, my thoughts on BASIC today is not that it was really BASIC. Not even that it was necessarily a great beginner language, though some people treated it that way. It was an easier shorthand for assembly.
Whatever you think of Eich, of Mozilla, or of the entire situation, Firefox and Javascript are not the same thing here. If anyone means to make their displeasure felt in Mozilla's revenue, banning Javascript wouldn't make sense.
Well, since you asked: http://lmgtfy.com/?q=why+is+deflation+bad%3F
The teacher may be responsible, sure. The harassment happened; knowing that, it is an absolutely fair question to wonder if more could have been done by the teacher.
> Students have remedies, they all know what they are. I knew. If the child spoke up to a teacher, principal, janitor, or anyone and the school did nothing then I'd side with the OP in a heartbeat.
I feel it must be pointed out, and repeated if necessary, that someone does not need to report a wrong action for that action to be wrong. I know that's not exactly what you said. The author's daughter was harassed, and that is wrong. Full stop.
> Absent any real facts about what happened I'd have to guess (and it's only a guess) that the teacher wasn't the problem here.
If you are absent any real facts, why hazard a guess at all?
> The author is being unfair when she is holding the teacher solely accountable for bullying.
Come, now. Yours is not a reasonable conclusion to make from the blog post. It should be obvious to the reader that the bullies in question are responsible. The author's point was that the teacher shares responsibility in providing a safe environment for all students in the class. Perhaps you don't agree (and what a shame if you don't), but you should not misrepresent the author's argument to make your case.
I mean, ten years ago, did you think lots of people would be coding in Objective C? It's funny how things change.
I look them up to see what they're up to and, of course, they are no longer in operation. Interestingly enough, it was owned by a man named Robert Swartz, who just happened to be the father of one Aaron Swartz. What coincidence.
(Wikipedia page here: http://en.wikipedia.org/wiki/Mark_Williams_Company)
Sure, you may not want people to live forever, but that has absolutely nothing to do with the above comment; indeed, what you've said might be viewed as somewhat callous when considering the context that someone has revealed that they have terminal cancer.