After Long 6 and half years!!

Writing after almost 7 years now. 

I learned few good things in this time.

Got transitioned between teams. 

• Profiler team(my last blog entry time), 2016 - 2019
• ICS automation team(Short term). 2019
• ICS Performance team (Got pulled by new manager, it pissed off my short term manager) 2020 - 2022
• Learnt a lot in this team. Ruby on Rails, Networking, VPN, 
• After the manager left, got a new manager who pissed off everyone in team by his toxic behaviour. May be he wanted to prove himself too early.
• Now there was a big shuffle and US layoff. The cloud product (ZTA/NSA) team was going to be cut short to 1/4 the of that time's team count. 
• I was chosen for performance testing among those 25 members. 2022 - current

Last year, I started the scaler program.

Now I at least can say I know about the things a software engineer should know.

DSA, SQL, Databases, Low level Design, High Level Design etc.

Now I understand some core things discussed and practiced in our industry. From now, I can understand things and can build my knowledge and wisdom.

I can code, I know basic algorithms and data structures.

Need more practice, though.

On path to become a better software professional.....

Discussions!!

I just started a discussion series around my team for discussion upon general testing. Lets jump directly to the minutes of first discussion:

(BTW it includes 4 testers in team and the manager common to Dev and Testing, Testers experience range in testing is 3-15 years)

1. Me: Start with "WHY this meeting?".
2. Manager: Draw the diagram of your "why". It's pretty difficult. 
3. Manager: Broaden your outlook. We, as testers , are less creative. We are like a cow, just walking in a circle.
4. Tester 1: It was around the "Broaden outlook" point. We always move in same tunnel. never come out and see from outside.
5. Tester2: He was more around Process improvement. Including testers in some decisions. A better test plan. 
6. Tester 3: Share knowledge. Learn something new in each meeting.
7. Tester4(me): Peer feedback. 2 pair of eyes are better than 1 pair of eye. 

I am not sure this are appropriate answers to the questions "Why this meeting?". 3,4,5 look like some good answers, but yeah with these discussions, we can improve in other areas too.

We need to have separate meetings for :

1. "peer feedback" on testing,
2. Share knowledge

After these points, meeting went to random discussions. Like, compulsory automation, etc.

I think meeting was useful in terms of at least starting discussions. Need to put it into effect.

Oh my God!! My second post

Just saw my last post. What have you learned in last 4-5 months.

Is your coding better now? Can not say. Have automated a lot though.

I just changed the title of my blog to "Dumbtester". Because I am a tester and I still feel dumb.

So does it mean that I will blog now for testing purpose?
It can be a general blog. As testing is a personal discipline and there is a blur boundary between a tester's work and life.

More discipline. More deep dives. More meditation. More life. More discussions. More presence of mind.

Yay!! My First post

Yes I feel dumb. After 7 years of graduating in computer science I can not code. I feel like I am not contributing anything to my company. I am a tester by professional and supposed to automate test cases. But I can not say that I am comfortable with any programming or scripting language. But yes, I know that I can learn coding by practice, solving difficult problems, re-arranging my neurons in mind to see a problem from different perspectives.

Yes Start it now! If someone else can do it, you too. Start solving problems. Now or never. Learn it. practice it. Try to see from different angles. Be patient. Do not think much about others.

Record your progress. You have to make it to Google.

No one can stop you.