Might and Logic
No, it's not might and magic. Might and Logic... it's like solving an ACM problem with brute force against some elegant wrong solution.
Yesterday, I went out with two of my co-workers to have merienda at the cafeteria. One of them is a technical lead, while the other is a newly hired AP. Basically, all three of us are programmers.
While taking a break, we were discussing some fairly technical topics (a typical thing we usually do especially whenever I am assigned with bugs that are difficult to fix). As for yesterday's session, the AP was comparing our company's development framework with the framework he was using in his previous company. He was saying that since our company's framework is more mature than the ones available in the market(fyi, our framework is older than struts), it must be good. Although we sort of disagree, we explained it by saying that each have their own purpose why they were designed like such.
Anyway, when we were about to leave the caf, we were faced with a different 'technical' problem. The door at the veranda was locked and we can't enter the building. My fellow AP was trying to turn the knob, but the knob was stuck. Since we don't want to get attention by destroying the door, the technical lead and me were thinking of going to the door at the other side of the building. A logical 'Plan-B' in case the nearest door is locked.
When we were about to go to the other door, a janitor came and pulled the door without turning the knob. Apparently, the knob of was broken and it cannot be locked. We just need to pull it a little harder in case door gets closed.
The three of us laughed after realizing that programmers tend to be 'too logical' in solving problems sometimes when all we need is a little 'brute force'.
Yesterday, I went out with two of my co-workers to have merienda at the cafeteria. One of them is a technical lead, while the other is a newly hired AP. Basically, all three of us are programmers.
While taking a break, we were discussing some fairly technical topics (a typical thing we usually do especially whenever I am assigned with bugs that are difficult to fix). As for yesterday's session, the AP was comparing our company's development framework with the framework he was using in his previous company. He was saying that since our company's framework is more mature than the ones available in the market(fyi, our framework is older than struts), it must be good. Although we sort of disagree, we explained it by saying that each have their own purpose why they were designed like such.
Anyway, when we were about to leave the caf, we were faced with a different 'technical' problem. The door at the veranda was locked and we can't enter the building. My fellow AP was trying to turn the knob, but the knob was stuck. Since we don't want to get attention by destroying the door, the technical lead and me were thinking of going to the door at the other side of the building. A logical 'Plan-B' in case the nearest door is locked.
When we were about to go to the other door, a janitor came and pulled the door without turning the knob. Apparently, the knob of was broken and it cannot be locked. We just need to pull it a little harder in case door gets closed.
The three of us laughed after realizing that programmers tend to be 'too logical' in solving problems sometimes when all we need is a little 'brute force'.