Ah, yes, thank you for the explanation.
51 karma · joined February 27, 2012
This is quite harsh sarcasm, but if it isn't true for the GP, it's true for so many people. Well said.
What I understood (due to hastily coming to conclusions) was it is dangerous to believe that life has lows and highs.
Is this not certainly true?
> Your life is not a prewritten narrative with defined story arcs.
It seems to be that someone could believe in the statement before this and not this.
people who've done an incredible amount,
social media and how he reacted to growth,
and how life is after you've reached (what seems to be) your highest point
TL; DR: You're changing OSes, expect for a complete change in landscape.
Was anyone else surprised to see "bunch"? Why did they use that, when "group" would be a much better word?
As someone who likes to read quotes and examine the wisdom within (or at least I tell myself that), I see no wisdom here.
The only possible interpretation which I find makes sense, is that the priorities of the expert are much clearer then the beginners. The expert (through experience and intelligence) knows what matters, and what details are not critical. The beginner however, places great importance on things which are near-worthless.
If that is the more correct interpretation, then I find the wording clumsy. If this isn't then please enlighten me.
Why I'm working for the man and not doing a startup?
Stability and lack of passion.
Two good reasons, however, not too insightful (subjective).
for the rule:
%.gz: %
edit, that rule above only makes sense to me if the file name to be gzipped was passed to make. Is that correct? (I'm new to make)
> We constantly have to ask ourselves: are we causing any issues or slowdowns on our customers’ websites? [sic]
The GP's noting of irony (is that correct?) seems to be valid.
While I'm sure you didn't mean it this way, your wording deflects blame from the site's retarded text contrast to the GP (robomartin).
(no snark intended)
> This is why I don't believe in computer science degrees. What you learned 5 years ago may not be relevant today.
CS degrees aren't about what you learned, but what concepts your mind digested and grew from.
The 600,000 the article mentioned were mostly of this type, I presume (not the part time maybe, but the other two).
E.g. Secretarial/bureaucracy type jobs which rarely pay more then $15/hour, and usually ~$10/hour, are quickly being replaced with computers.
> Careers? Full time, living wage that can support a family, full benefits packages? Those are becoming obsolete, and fast.
I wouldn't say obsolete. I doubt they're growing at the same rate of the population, but there are still many fields where building a career is a reasonable venture.
Agreed.
> It doesn't seem odd to anyone that we're reading a post describing the author's epiphany that epiphanies are useless?
Not overly so. Meta can cause strange cases of logic at times (e.g. there are always exceptions).
If you don't want to run out of ideas, the best thing to do is not to execute them
You can tell yourself that you don't have the time or resources to do them right
Then they stay around in your head like brain crack
So no matter how bad it gets, at least you have those "good ides" that you'll get to "later"
Some people get addicted to that brain crack
and the longer they wait, the more they convince themselves of how perfectly that idea should be executed
and they imagine it on a beatiful platter with glitter and rose petals
and everybody is clapping, *for them*
but the bummer is must ideas kinda suck when you do them
and no matter how much you plan, you still have to do something for the first time
and you're almost guaranteed the first time you do something it'll blow
but somebody who does something bad three times still has 3x the experience of that other person who's still dreaming of all the applause.
when I get an idea, even a bad one, I try to get it out in the world asap
cause I certainly do not want to get addicted to brain crackAs Ze Frank said:
"The longer they [those with the "good" ideas] wait, the
more they convince themselves of how perfectly that idea
should be executed, and they imagine it on a beatiful
platter with glitter and rose petals."
scotch_drinker accurately described my sentiments. Generalizing the points he made, I'll say two (and half) things:
1. Up the level of your writing a bit. It's currently in ripped jeans and an Ed Hardy shirt (have'nt?!). Don't go full black tie, but at least get a blazer and clean pair of jeans on. See here: http://www.wikihow.com/Avoid-Colloquial-%28Informal%29-Writi...
2. (a) Have one point (your thesis), and make sure (virtually) every sentence is directly related to it. You had far too many distractions. The fact that you were a "negger" and some people benefited from being one is completely irrelevant.
2. (b) Make sure very sentence is strongly related to your thesis. E.g. if you want to show how it's a nice day, don't say you went for a walk, tell me you went to the beach. An example from your post would be the great implementers you mentioned. Mentioned fewer implementers, but when giving one, expound a bit, and show the reader how much it related - or is applicable - to your thesis.
The message (which was poorly conveyed) is correct however. Have results as soon as you possibly can (just try not to sacrifice too much elegance).
A (lousy) example would be Linux & GNU Hurd.