When I mention to my friends who weren't from this field, that I'm a software engineer, they relate me to, well, engineers. Sadly, I'm not. I'm far from being an engineer, I do not get the I.R status no matter how many books I read or write. To be simple, I often tell them I'm a programmer.
The fact that I know I'm not just a programmer but I don't know how to explain what I do because I don't know better.
Today, going for my language class, I came across this dilemma again. I don't know how to say my occupation in the class. I'm tempted to just name it "Programmer" again. But this time, I didn't. In fact, I stick to "Software Engineer" no matter how difficult it is to pronounce it and I was ready to explain what my job does.
See, being a "Programmer" and "Software Engineer" is different. Anyone can code. Anyone can be a programmer. As long as you have the technical skills. A software engineer requires more than that. You need to know how to take and intepret requirements from stakeholder. You'll need to understand the process to develop a solution that fulfils their needs. A good software engineer needs to understand the in and out of the solution and consequences of the development processes. A software engineer would apply the software development lifecycle to appropriate project based on stakeholder's needs so that each process is thoroughly weigh through.
Now, I realize people are starting to know what is software engineering. I'm glad that my teacher did not relate me to any Engineering field, but she knows that I'm dealing with the ICT industry at least.
So I'll proudly say that I am a software engineer when people ask me about it and I will be prepared to explain it because I know my job better now.
No comments:
Post a Comment