Skip to main content

Childhood Memories

My awareness with the field of Software started in my early childhood.

Engineering Symptoms

Some engineering symptoms started appearing on me when I was a kid… At first, I was staring at things for hours without talking… My father told me that he was always wondering “what’s going on in her mind!”…

Sometime later, I started disassembling things, starting from toys and ending with electrical appliances (radio cassettes, washing machines…) and using the spare parts to build something else. I sometimes just disassembled machines just to rebuild them after a great exploration phase. I was kind of danger, but my folks liked this.

I also used to sketch weird drawings for images in my mind till I was introduced to my first PC at the age of 11. When I saw it, new ideas started formulating in my head, I was reading a lot, and I wrote my first computer game at the age of 12, it was kind of strange for people around me but I liked the idea a lot and I decided to be an engineer, a computer’s engineer.

The Decision

Since then, I had one target in mind and I worked very hard to reach it for the next 6 years… I was heading the Engineering Faculty… and thank God, I reached my goal. During these 6 years I did a lot of things amongst which I remember writing a certain program which I learned years later that what I did was called a database! By the way seeing Windows 3.1 with its multi-tasking feature was kind of a dream or a miracle for me and it was one of the accelerators for me to continue in the field of engineering. By the way, many people tried to convince me to do something more useful and they advised me to go to the medicine school, but I didn’t want to.

Management Symptoms

Also, some management symptoms manifested themselves on me some years ago… I used to gather the neighbor’s kids and assign them tasks while talking to imaginary clients on the phone and committing to virtual deadlines… I was using my grandmother’s sewing machine as a desk!

The Prophecy

My family believed long ago that I will grow up to be a surgeon or a pianist as my fingers were long. I think that they forgot about the typist job, which with some modifications is equivalent to someone using the keyboard most of his day… a Developer than a Project Manager!

Hello “Real” World!

Real world is totally different that dreams and prophecies, when you leave your silo and get in touch with others, you start discovering the truth, and this is usually through shocks and disappointments which arose one after another:

  1. Students in the engineering school were categorized in 2 groups, a group sitting in the garden and a group sitting in the cafeteria… labs were empty!
  2. Some students joined this school because it is prestigious though they are not interested in engineering!
  3. In the world of theory, electrons traverse their orbits in pico and nano seconds… and I have to wait for hours for a bus to drive me home!

Lesson Learned

Windows is only at home not in school labs!

Comments

Ayat Elshami said…
First, is it you who wrote this one? I mean am I missing some reference or something?

Second, if it's you and I didn't miss anything, is it truly about you, or the childhood stories are some brilliant fiction?

Third, why does the end feel truncated... I mean it's like we suddenly jumped to Hello "Real" World, which was totally fine for me, and then, without any sense of approaching the final, I say the line Posted by Mena Mostafa at 12:35 AM ;)
Mena M. Eissa said…
First: It's me who wrote this one.

Second: Yes, it's truly about me, and it doesn't mean I'm a brilliant fiction :D

Third: The end feels truncated because this is what I can remember :$

Popular posts from this blog

The Triangle of Tactics

Sometimes referred to as the Triangle of Horror… where the PM tries his best to maintain his balance while walking on the very thin project rope between this triangle and the Project Constraints Triangle (time, cost & scope). The triangle sides represent: The Team, The Client and The Management Every side of this triangle is obsessed by the sole idea that the other two sides want him dead, i.e. the team thinks that the client and the top management want him dead and vice versa. Usually a good PM gets lost while trying to maintain this triangle in good shape to keep all parties satisfied and happy while making them think they are his first and only priority to get out what is needed from them for the sake of the project. From my perspective, this is a much harder balance to keep rather than maintaining and managing the Project Constraints Triangle… It highly depends on people, their culture, maturity level, and on the PM’s ability to understand this and deal with it in a

I am a Project Manager

I am a Project Manager and I love my job… I am a project Manager and I love doing my work! I am nothing more but a Project Manager amongst many others. I got married to my work (not job) after a great love story which started from early childhood ( coming soon ). I started my career as a Software Developer in the late 90s, then held many positions in the field of Software Development, some were promotions and some were kind of additional assignments due to my performance. Among the positions I held are Developer, Team Leader, Project Manager, Project Leader, Senior Project Manager, Senior Project Leader, Program Manager, Business Analyst… though I was dreaming about becoming an Architect! But seriously the job I loved the most is Project Management. The things I hated the most in my early years were politics and economics/finance, which both became the core of my daily work for some years now! 94% of my experience was built by working in Software Houses as a vendor/provider and

5 Reasons not to listen to a PM (for Managers)

Usually a PM cares about his projects and is keen to develop them as per the planned budget, time and scope. However, managers should not listen to their PMs for the following reasons: 1. PMs are Time Wasters PMs plan… They study and mitigate risks and project issues in proper ways to guarantee the smooth execution of the project. Planning is a bad practice that PMs should stop using and referring to whenever they discuss a project related issue. Plans are not really needed and in most of the times they are useless because no one follows them (all gratitude and respect reserved for PJs). Also, it is preferable to face risks when they fire. Anyways, who really cares for risk mitigation and contingency stuff! Let’s face surprises when they arise and use panic mode to push on teams to solve their issues! 2. PMs Forecast PMs track their projects and use trends, issues, project and client historical data to forecast project status and use corrective actions properly to maintain thei