printf (" Software Engineering \n");

My first impression of Software Engineer, when i joined CSE group in my Engineering was that he writes tons of Code.

Though we were taught about OS fundamentals, Software Engineering processess, statistical analysis etc, i thought that knowing how to write a peice of code in C/C++/Java is all that matters. For me, all subjects other than programming language were to be learnt and remembered more for getting marks, but will never be used in the software life cycle.

I never realised during college days that designing UML diagram, use case flow diagram is as important as writing Code. The only thing i gave importance other than the Code is the Flow Chart and psedocode algorithm.

But now i realise it’s not just the Code that we write, but the whole eco system around it. Starting from requirements analysis, Design, Deployment and to production support each stage is as critical as the other in their own respect. When writing code, i am sure may people like me will never keep in mind about different deployment scenarios like the cloud computing and Hosted architecture which are gaining prominance day by day.

The other BIG item which we keep ignoring is, the User experiance. For us, the technolgy we use is more important that what the user expects. I used to feel good, when i crack a piece of complex code, rather than improving the User experiance.

Now-a-days, i realised that unless the End User enjoys using a particular product, its not really doesn’t matter how much effort/tecchnolgy you put in to write it. I really appreciate Google in this, they just make things so abvious that as a end user you dont need to put in much effort to understand what they want to convey.

Though i wrote this long describing various things, i bet myself that i will only look at technical feasability rather than user experiance when some one asks for any new requirement.

Hope, i will be more End User biased rather than techonolgy biased 🙂 .

This entry was posted in Personal. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *