Tuesday, March 22, 2011
Back to Work
work
labor
IT Industry
quality obsession
learn
think
analyze
commitment
early wake ups
drink Nescafe
wait for weekends
count holidays
bank account
monthly salary
money waste
Although it’s a temporary back, a two months contract, but I think they are enough at the meantime.
Monday, May 31, 2010
1 Year & Half
1 year & half, for leaving work, and still I’m using the word “we” when talking about the company I used to work with.
1 year & half, for staying home, and still thinking whether what I did was right or hasty decision.
1 year & half, was going to be full of more experience, more money, more fun!
I don’t know why, recently, I’m thinking so much about my ex-work. I'm really missing it.
Monday, December 08, 2008
Soon ... Unemployed!
Anyway it’s done now!
I have quitted!
Yes I did!
Why!!!
This is what I wanted to do long time ago, I’ve got enough stress, tension, and exhaustion, beside feeling bored toward it.
I need time to organize my life, before having our new member in the family :)
I need to stop running! I need to act in somehow slow emotion.
I need to take care of my better half, my new home, and myself!
I wanna have more time for Allah, I want to go back for memorizing Quran.
I wanna start a new social morning life.
What I wish, is not to feel sorry or regretful about it .
Inshalla this will be on action at the beginning of next year.
1/1/2009 I will be officially unemployed! After 3 years and 9 month in service .
Confession:
I will really miss that routine!
Tuesday, January 09, 2007
Worst Case Scenario
When meetings are boring, full of talking, & time wasting.
Requirements are unambiguous, incomplete, & inconsistent.
Analysis is shortened, infeasible, & incorrect.
Specification document is not written, or unused, & out-of-date.
Assigned tasks are reassigned, & assigned for inappropriate person, or tasks are misestimated, unclear, & changeable.
TTLs (Technical Team Leaders) are busy with team members, releases, & planning.
PMs (Project Managers) are taken up by clients, meetings, & decisions.
Tools are complicated, numerous, & need web services to interact. Machines – computers – are used up, hanged, & broken down.
Coding is puzzling, taking so much time of nights & weekends, & has open issues.
Solution is buggy, with missing functions, & crashes.
Deadline is close, sharp, & fixed.
Still we can deliver the best! This is called adventure, challenge, & risk. With deep there success exists! That makes us alive, & adds taste to our lives!
The problem is I feel like pressing Esc (Escape) button, & quitting my job! I don’t know why I’m not enjoying the ride anymore! I wasn’t so ever! This is not the real ME!
Thursday, December 28, 2006
Sweetest 5arof Ever
Sunday, December 17, 2006
How to Make the Right Decision
To make the right decision, take into account:-
- the situation u r n now,
- the situation u would like to b n, n th future,
- resources available,
- what other people will accept,
- the feasibility of different options,
- the time factor
From book: 30 Minutes ... to Make the Right Decision, by Jane Smith
Sunday, July 09, 2006
World Teams
A player might be entered in the middle of the game, and so does a new team member who might join the project after it has started. In both situations the new member should be ready to be in the mood, by giving attention to the whole game as a football player, or by reading and knowing what the project is all about as a software project member.
A player might leave the game in any time either by red card, or by the coach request. So does a member in a software project; a member might leave whether by himself or herself, or by the project manager decision. In both situations the other team members should be able to cope with this change, it might cause modifications on the plan, and members might change some roles or hold more responsibilities. On the other hand, the leaving member should not cause any noise while leaving.
The playing tactic might change through the match. Also in a software project the overall plan might be changed 180 degree. The manager and the coach are seeing things clearer than the team members. Changing the plan is not easy and it is risky, but for sure the boss doesn't take that decision unless it is needed.
Injuries might occur in a critical time of the match. Also a certain circumstance might occur for a team member. Coach should be able to handle that, and keep the whole team calm, there should be an alternative plan for such cases. As well the manager should be able to manage with the new state, and the whole team should shift to plan B.
Playing alone with the ball excluding the whole football team is a big mistake. Players should do their roles, keeping the sharing sprit and the team work. Each member in the software project has his or her own role, team should be cooperative.
Losing a game is not a one’s fault; it is the fault of the whole team. As for a software project, late and poor delivery of the product should not be thrown upon a developer or a quality engineer, the whole team is blamed.
And the list goes on with situations that are the similar in a football team or a software project team. Out project's deadline is close, and so is the final World Cup match. So good luck for both.
Monday, September 26, 2005
Top 24 Replies by Programmers
24. "It works fine on MY computer"
23. "Who did you login as ?"
22. "It's a feature"
21. "It's WAD (Working As Designed)"
20. "That's weird..."
19. "It's never done that before."
18. "It worked yesterday."
17. "How is that possible?"
16. "It must be a hardware problem."
15. "What did you type in wrong to get it to crash?"
14. "There is something funky in your data."
13. "I haven't touched that module in weeks!"
12. "You must have the wrong version."
11. "It's just some unlucky coincidence."
10. "I can't test everything!"
9. "THIS can't be the source of THAT."
8. "It works, but it's not been tested."
7. "Somebody must have changed my code."
6. "Did you check for a virus on your system?"
5. "Even though it doesn't work, how does it feel?"
4. "You can't use that version on your system."
3. "Why do you want to do it that way?"
2. "Where were you when the program blew up?"
1. "I thought I fixed that."
Tuesday, August 16, 2005
Software Testing Joke
Usually testers report bugs* to the developers to fix them
Bug: A glitch or problem in the programming which causes the software to behave erratically.
Some Software Testing Types:
- Testing Types
- Integration Testing
- Regression Testing
- Acceptance Testing
- Functional Testing
Finally, Here is the joke :)
TYPES OF TESTING WE* WOULD RATHER NOT SEE
WE: Testers
Aggression Testing
If this doesn’t work, I’m gonna kill somebody.
Compression Testing
{}
Confession Testing
Okay, okay, I did program that bug.
Congressional Testing
Are you now, or have you ever been a bug?
Depression Testing
If this doesn’t work, I’m going kill myself.
Egression Testing
Uh-0h, a bug... I’m outta here.
Digression Testing
Well, it should work, but let me tell you about my truck.
Expression Testing
#$(%&#*^#$
Obsession Testing
I’ll find this bug if it is the last thing that I do
Repression Testing
It’s not a bug, it’s a missing feature
Succession Testing
The system is dead. Long live the new system!
Suggestion Testing
Well, it works but wouldn’t it be better if....
:)
Monday, August 15, 2005
\\//\\//elcome ME!
I’m testing -not exams!- ”Testing software” that’s my job,& that's what I'm doing right now, then I took a break to welcome myself between all of YOUs, and to have my lunch outside the office.
The weather is muggy outdoor which is strange here in Amman -where I live!
Any way Russell Baker was right when he said "Ah, summer, what power you have to make us suffer and like it".
That’s all for today, I have to go back to work...