mouse

Aside

“O hai, don’t mind me, just taking a look around. Oh, you’re closing the door in front of me? That’s cool, bro, I’ll just go beneath it and leave you wondering where the fuck i’m going” – mouse in my kitchen.

Sleeping patterns

Good Morning

According to the above comic, I’ve traveled round the globe twice in the last week, if I’m not mistaken.

For some time now, I’ve had no societal restraints on when I should wake up or go to sleep. School’s out, and the closest thing to my job is Summer of code, which entails working from home on your own terms. Also, I found that I have someone to talk to, or go out for a coffee at about any hour, night or day. So there’s no real reason for me to enforce the 12AM – 8AM sleeping pattern right now, and that gave me some weird kind of creative freedom.

What I’ve observed for the past few days is that, without any kind of enforced schedule,  I sleep for about 4-5 hours for about every 10-12 waking hours. This seems to work pretty good, but I doubt it’s all that healthy. I fall asleep for short 20 minute naps in between the main sleeping sessions, and that’s the only time I get to actually dream anything, which might be an indication I don’t get enough REM sleep. Also, I don’t feel well rested, but I’ve been having this problem for months now, so I doubt it’s the new schedule’s doing.

Sleep is a curse, though, I’m sick and tired of it and I hate that I’m its’ slave. If you have some tips on how to reduce the sleeping time while still being productive, please tell.

Writing is effin hard.

What the title says.

There’s nothing as intellectually humbling (for me,at least) as trying to put an idea, which is crystal clear in my head, in words for all to see. It’s when I usually realize I don’t really know what I’m talking about. I tend to agonize over every sentence and every construct, not to mention the constant questioning if the world needs another poorly written blog (answer: no.).

I find I fare better with live conversation because I don’t have the time to over-analyze everything that comes out of my mouth, and hope that people don’t have as much time to analyze it. So basically, I just think of conversation of having a lower standard than writing, and also, talking allows spontaneity, something which I kill while writing.

Jeff Atwood’s post about “tricking” developers into writing first got me thinking. He’s right. People (and especially developers, and especially me) need to learn to write. That’s part of the reason I started this blog. You can exercise your writing skills just fine on SO. But it also adds a few hurdles which discourage me. You have to be fast, otherwise someone else gets the up votes, and you feel as though you put your effort into writing your post for nothing. You also have to write answers to specific questions (doh,  it’s a Q&A site). That’s fine, but deadlines and specific topics are what journalists should worry about.

Whether it’s a review, a rant, technical documentation, an email, or anything longer than 140 chars, I’m lost for words. That’s why this blog is so static, and feels semi deserted. I believe most people feel this way and that’s why most blogs are in this state. That’s (part of) why Twitter is blooming. 140 chars are enough to transmit the gist of an idea, but little else. Elaborating on a basic idea is usually what scares me away (also, redundancy – I hate that I always have to worry if it’s been done/written before; double hate the fact that the answer is a Google search away.).

The above post illustrates just how hard writing is for me. But I’ll keep at it.

Quick tip: edge case for overflow:hidden, position:absolute and anchors

EDIT – Wow, talk about the perfect storm! It seems like the bug I encountered happens in a very special case.

If you reference an element by the id (or a named ‘a’ element) which is contained in an element with the properties ‘overflow:hidden’ and ‘position:absolute’, you WON’T BE ABLE to scroll back up.

Here is what basically must happen:

1
2
3
4
5
6
7
<body>
    <div id="container" style="overflow: hidden; position: relative; height:400px;">
        <div style="position:absolute;height:300px">
            <a name="anchor">This is where I have to go.</a>
        </div>
    </div>
</body>

It is very important that #container is a direct descendent of body, and that the element which has “position:absolute” is a child of his, so this is pretty much an edge case, which I just happened to encounter and which I thought was way more common. meh.
Now, in this example, adding “#anchor” to your URL will make your page scroll down to the link, but you won’t be able to scroll back up. Probably. I’ll do further tests on all browsers.
I’m not sure if this is expected behavior or not, but it is pretty dumb either way.
YOU HAVE BEEN WARNED.