Live data from Hacker News

Real geeks die early

norbu09.org

21–30 of 42 posts

Re: Real geeks die early

#21
post #6
post #3

Earlier quoted context omitted.

> I am working with multiple resources, First step: stop calling people "resources"

heh, sure. I see how my comment is coming off as bitchy and is being downmodded. However, I am genuinely curious. There are people in my team that are currently just working 9-5. There is one guy who is working nights and weekends because he likes it, and then there is one guy that's working (productivity wise) 25-30 hrs a week while missing internal milestones. Its frustrating to be in my place, because I feel sad f…

There are people in my team that are currently just working 9-5.

Were they hired with the expectation that they would work longer than that? I ask because it's not unheard of to be told you'll be working one set of hours, and then expected to work something completely different.

If no expectations were set at all during the hiring process, that's more the company's fault than the employees' fault.

Re: Real geeks die early

#22
post #20
post #4

Apparently so do their shift keys.

does it bother you that people don't capitalize properly in their personal blogs? i never understood that. i read through it just fine. i know it's proper, but i guess i'm kind of lazy in that way. in the words of christopher walken: "i never liked capitalization. it felt like more of an imposition."

th prblm s nt tht ts mprpr, bt tht yr gvng th rdr lss nfrmtn

Re: Real geeks die early

#23
post #6
post #3

Earlier quoted context omitted.

> I am working with multiple resources, First step: stop calling people "resources"

heh, sure. I see how my comment is coming off as bitchy and is being downmodded. However, I am genuinely curious. There are people in my team that are currently just working 9-5. There is one guy who is working nights and weekends because he likes it, and then there is one guy that's working (productivity wise) 25-30 hrs a week while missing internal milestones. Its frustrating to be in my place, because I feel sad f…

Unless the project is the Apollo-11, I have never understood why 9-5 is not sufficient. That's 7 solid hours of work (1 hour for lunch). If pointless meetings consume a lot of that time, I get that may not be sufficient.

Personally, whenever I've put in 7-8 solid hours of coding and/or design/thinking, I'm spent for the day. Done. Over. I just want to give my brain a rest at that point. I don't think it's humanly possible to be working at peak capacity for anything before 10 hours a day. I wish modern workplaces focused more on how to create an environment/culture where employees are in "the zone" more often than just having them put in longer hours. That I believe would produce higher quality work.

This whole thing about expecting programmers to work beyond 9-6 is just sad. I have never once seen a Product Manager or Business Dev guy work late into the night.

Re: Real geeks die early

#24
post #22
post #20

Earlier quoted context omitted.

does it bother you that people don't capitalize properly in their personal blogs? i never understood that. i read through it just fine. i know it's proper, but i guess i'm kind of lazy in that way. in the words of christopher walken: "i never liked capitalization. it felt like more of an imposition."

th prblm s nt tht ts mprpr, bt tht yr gvng th rdr lss nfrmtn

if acronyms and proper names were capitalized, we'd have everything covered? punctuation already signals the end of a sentence.

i could read and comprehend what you said in your example, but it required more mental effort. i don't think reading a blog without caps requires more mental effort, but if it does to most people, then i might have to switch back.

Re: Real geeks die early

#25
post #22
post #20

Earlier quoted context omitted.

does it bother you that people don't capitalize properly in their personal blogs? i never understood that. i read through it just fine. i know it's proper, but i guess i'm kind of lazy in that way. in the words of christopher walken: "i never liked capitalization. it felt like more of an imposition."

th prblm s nt tht ts mprpr, bt tht yr gvng th rdr lss nfrmtn

It looks like no-vowels slows down my reading to about 50% of original speed, whereas no-caps slows me down only to maybe 90%. This might be because I spend so much time on IRC.

Re: Real geeks die early

#26
post #24
post #22

Earlier quoted context omitted.

th prblm s nt tht ts mprpr, bt tht yr gvng th rdr lss nfrmtn

if acronyms and proper names were capitalized, we'd have everything covered? punctuation already signals the end of a sentence. i could read and comprehend what you said in your example, but it required more mental effort. i don't think reading a blog without caps requires more mental effort, but if it does to most people, then i might have to switch back.

Only 1/3 of the periods in e.g. this sentence signal the end of it.

Re: Real geeks die early

#27
post #6

Earlier quoted context omitted.

heh, sure. I see how my comment is coming off as bitchy and is being downmodded. However, I am genuinely curious. There are people in my team that are currently just working 9-5. There is one guy who is working nights and weekends because he likes it, and then there is one guy that's working (productivity wise) 25-30 hrs a week while missing internal milestones. Its frustrating to be in my place, because I feel sad f…

There are people in my team that are currently just working 9-5. Were they hired with the expectation that they would work longer than that? I ask because it's not unheard of to be told you'll be working one set of hours, and then expected to work something completely different. If no expectations were set at all during the hiring process, that's more the company's fault than the employees' fault.

I think that he's more concerned with dealing with the guy that is not pulling his weight, not with motivating the 9-5'ers to work overtime.

Re: Real geeks die early

#28
post #26
post #24

Earlier quoted context omitted.

if acronyms and proper names were capitalized, we'd have everything covered? punctuation already signals the end of a sentence. i could read and comprehend what you said in your example, but it required more mental effort. i don't think reading a blog without caps requires more mental effort, but if it does to most people, then i might have to switch back.

Only 1/3 of the periods in e.g. this sentence signal the end of it.

i believe the correct grammatical use of "e.g." uses commas anyway, in which case i would have easily understood the example without caps:

only 1/3 of the periods in, e.g., this sentence, signal the end of it.

Re: Real geeks die early

#29
post #20
post #4

Apparently so do their shift keys.

does it bother you that people don't capitalize properly in their personal blogs? i never understood that. i read through it just fine. i know it's proper, but i guess i'm kind of lazy in that way. in the words of christopher walken: "i never liked capitalization. it felt like more of an imposition."

I just found it to be an unnecessary distraction.

It's not that it bothers me. It just makes it more difficult than necessary for me to read. I make an assumption that by posting something on the internet, the person wants me to read it and wants to share their ideas with me.

Why distract readers from one's ideas by not following simple grammatical convention?

Re: Real geeks die early

#30
post #4

Apparently so do their shift keys.

Well, there was a politicised line of thought in 20C modernist typography towards abandoning capitals due to their implied hierarchies. Herbert Bayer’s experimental Architype (http://en.wikipedia.org/wiki/Bayer_Architype) would be one example of a specific typeface designed with this in mind, but there were also many other typographic designs of the time which abandoned capitalisation.

We’re still seeing the filter down of these experiments now, every few years another company rebrands and drops their capital letters to “humanise” their image or some such reasoning.

So… maybe it was a conscious decision by the author along these lines. Or as you say probably just a broken shift key.

Post reply on HN