Kaash..

हॉल ATT एक हॉल ही तो है जहाँ किसी सस्ती चाल की तरह आवाजें आती रहती है…हर कोई दो-दो monitors के सामने बैठा US भक्ति में लीन है…कानो में headphone चिपकाये अंग्रेजों की चप-चप सुन रहा है….सामने टीवी चल रहा है…चाल की तरह कुछ लड़के ठहाके मार के हंस रहे हैं..बीडी अन्दर निषेध hai वरना उसका शौक भी यही पूरा कर लिया जाता … पान – gutka लोग चोरी चुपके खा ही लेते हैं…
हाँ चाल की तरह एक- और चीज़ हो रही है …कोई लड़की जब कहीं से निकलती है तो कुछ छिछोरे कमेन्ट भी मार लेते हैं और आँखें भी ठंडी कर लेते है.

हाँ चल की तरह यहाँ भी सब अपनी छोटी सी खोली में घुसे हुए रहते हैं … जागते हुए ये सपना देखते हैं की एक दिन हमे कोई cubicle मिलेगा …कभी तो इस जगह से निकल कर किसी सही जगह पर जायेंगे …कभी तो किस्मत अच्छा मौका देगी…कभी तो किस्मत support से हटा कर development में लाएगी…

सब मजदूर हैं - मजबूर हैं काम करने के लिए : Mainframe वाला वेरिफिकेशन कर रहा है …डेवलपर वेरिफिकेशन कर रहा है…किसी का platform फिक्स नही…
Knowledge और Talent की धज्जिया उडी पड़ी है… सब सोच रहे है की काश……….

Abused as a "Fresher"

In a meeting when I expressed my views an experienced senior said "You are a fresher, you don't know anything about industry, you don't know
how to work and you should do any thing that is given to you, we are experienced and we shall do only standard work"

This is about what I felt and just don’t want to keep inside। Discussions leads to stronger b0ndings that is what I believe।
People with years of experience are coach and guide for beginners। That's why they deserve respect.

But I am very depressed and hurt by the word "Fresher" they use. What is the meaning of fresher?
Does the word fresher means have no common-sense? Does the word fresher means immature?

We all are working on the same company in same projects though and in the same team.
Are experienced guys doing something special in the project?
I believe all are doing same thing. Odd behavior towards freshers only shows what mindset people have.

Is every experienced person was born experienced … they were fresher some years ago but they groomed themselves to be respected professionals.
Just want to point out one thing...we respect the experience, knowledge and age of our seniors.
We know they are experts in their fields but being a fresher do not mean we have no knowledge and field of our choice.

We are also experts in one or the other fields but haven't got a chance to work on that.
We do have some plans of our future in some field...we also plan our future in the industry.

Every year new technologies come in market and every fresh face will be equipped with a fresh thing that the
experienced people might not even have heard of.

We are here to soothe ourselves. We are here to learn, that's why we generally accept all kind of work.
We also know that experience counts but being called a fresher in such a way is hurting.

I request all the respected seniors to please do not raise this type of excuses to assign any work to the person who is new.
I don’t know on what basis work is assigned but this shall not be the reason to state when some low level task is to be assigned.

This will divide the team into groups and will not be beneficial for the project. And will such comments gain any respect?

I believe something positive can come out of this. Friends comment on this article.

CS11-An Inspirational way

CS11 is a bunch of best talent hired…in which everyone is good in one or the other thing…You guys remember Core Java days…the assignments…

Can you remember how many ways we used to write code for a single problem…

Achin had a different approach … Rahul has another … Anay has third and Sagar had a different….

I just want you to think of this …

We all have one goal…success…we define it one or other way…as per our perception…
We make a plan to achieve it. ( Everyone has a different approach to ‘code’ ). That code is yours …your variables …constants …naming convention and algorithm...you know that this code it yours and what output will be because you wrote the code…

Decision is nothing but a point where you decide to commit or not …you have options to compile the code and see what the output is and not to compile it being afraid of compilation failure…you know if someone writes a perfect code that compiles in one go is a lucky genius…and lucky because even genius miss that in one go most of the times.

And until you compile how you do know you coded right? It is simple…until you take a decision and move ahead how you can decide whether you are right or wrong….to write a perfect code is impossible but good code is something you can write by having a clear picture of what is required…and its your decision to write code on algorithm made by someone else or on your own algorithm….whichever gives your clear picture.

Native algorithms may fail but if succeeds it’s a new discovery…

Have you tried understanding code written by other? No one likes that…similar is to see life of others …its complicated…for the one who had made it will feel it simple and others will beat their heads to understand…and its not a good idea…until you do the job of code review.

Guys if you understood what I wanted to say its good…and if its complicated then I am sorry to code it that way….rest you all can co-relate your life with principles of software engineering…

And remember Time is the ultimate master of everything…code or don’t code…impact depends on time…and the moment where you decide to compile…and see the output…premature compilation will always produce complex errors and warnings and mature code will just be a few syntax errors or so….