Aglehg's Blog


Just another site

IE6 the nightmare

This is the post I wish I had read on the blogs and forums out in the universe… About how to circle the  n different versions of IE which every developer know’s mostly have in common the fact that they are pretty crappy at following standards and are filled with support holes and MSonly object properties.

So for starters DON’T READ THE FORUMS, if you don’t know precisely what you are looking for . =P about 90% of the posts are novice, about 7% are people  hopping to play around and if you’re lucky to find some insigh… you have been browsing for hours.

Stand alone versions of i6 and other forms of bundled engines I’ve found, are good for pages with simple scripts and no authentication… but if you’re using a javascript library, ajax requests, and you have authentication… I’d run away from them.

MS proposes a solution which seams @first too much trouble.I mean who would want to install a virtual machine to run a browser.. please?! right? But in the end it may quite be your best solution. If you may be evading some specific IE corner… imagine what it’s like not knowing if that corner is the browser’s, the “emulator” of the browser’s or a gap in your code the other browsers covered for you.

Has an example I can tell you I wasted way to much time, just to realize that the thing I replaced IE with was not sending cookies along with the ajax request… :S

Now while javascript librarys can be a pain to keep track, CSS is pretty plain and there are plenty of valuable “compatibility tables”  like this one

which you really wanna check, so you can keep track of what’s going wrong without guessing to much.  The other think you might wanna look into are cheats that other people may have found…

So out of the tech talk… and in to the juice…  this is what I’ve (re)learned today. Guessing is your enemy. While it may be a fun game. Doing a test by case, can be a horrible way to get trough your problem. The idea is to build a stack of axioms you can rely on when you start formulating those theorems…  So much of the work is done in seconds in your brain and not in many hours on Google.


Filed under: Raios e Coriscos, webdev

OMG brilliant!


is the tittle of this brilliant reflexion on the community’s view of the programmer…. and the reality of it’s existence.

On the other hand I love the way it also reflects the more general principle that everyone values most, what he/she has more and better of.

which finally brings me back to this question that has stolen my sleep time:

How do you know the value of something?

To which I now stand with the following hypothesis:

The value of something is the highest value, by which someone else would still buy it. Given that you don’t consider ethics.

I have absolutely no idea of how to formulate an abstraction of it when you insert that nagging factor of ethics.

Filed under: e-moções, oikonomía, webdev

End day

I once read somewhere that a programmer is machine that transforms coffee in code… and eventually I fought in the company where I’m working to do just that… – I need focus on finishing that damn graduation… – I though

result => waste a lot more time codding because I’m totally out of the design.. so I have to work twice as hard to understand it… and deal with the fact that often I disagree with it, in a : as much passive way as possible… which is not much good for my stomach. It’s the trouble of being a girl I guess.. I get emotionally attached to the projects.  Like if each one of them was a child I wanted to see grow healthily..

Really.. I hate this pressure of “start coding” “start coding”.  Years of documentation on the importance of design… From my current knowledge…  mostly read, preached and applied in universities. Occasionally used in companies with university related people…   And pretended to be true else where.

Lesson learned: the more levels you have between the people that are implementing the request, and the person requesting.. the further away from it is the result. Do you know that game… tell a tale, to someone that tells the tale.. that tells the tale… make it circle around a table..

So far the best method, which I have only been able to apply for small free lance projects I did on the side. Seems to be a sort of “Iterative” development.

1º Request Requisites

2º Reply Interpretation of requisites with sketch design, as little implementation details as possible

3º Confirmation from client, with notes. Usually there are always corners that are bent.

4º Implementation of requisites

5º Submit to client evaluation. (you can call this the alfa )

6º Client inputs back changes  Repeat steps 4,5,6 until everyone is happy

It is more important to understand the problem, than to figure out ways of solving it. ‘Cause most of the time, you end up solving the wrong problem. To try to know everything from the beginning is just.. plain stupid. But you need to be very careful not to do the opposite. Which is why I like that feedback method. It’s not a conversation. It is an independent swap of readings of the problem. No one is in the way of anyones reasoning. So the odds of escaping comprehension are smaller.

I guess there’s a reason why big company’s use SRS’s… 

2.4 General Constraints

well it was done,  generally…



Filed under: e-moções, webdev

i6 funeral

“Internet Explorer Six, resident of the interwebs for over 8 years, died the morning of March 1, 2010 in Mountain View, California, as a result of a workplace injury sustained at the headquarters of Google, Inc. Internet Explorer Six, known to friends and family as “IE6,” is survived by son Internet Explorer Seven, and grand-daughter Internet Explorer Eight.
Thanks to all who came out last night, and thanks Microsoft for sending flowers! Checkout the pics on flickr. “

Just plain Hilarious!

Filed under: webdev