Work Pattern - Routine vs Innovation - Do you really have a choice
Being part of software engineering fraternity, I always had this introspective phase where I would question the work / development I am presently doing whether it's interesting/innovative or a routine feature development. Few dilemmas and discourses are as follows
1. I am building a product feature which basically requires me to copy paste most of my routine modules like creating similar entities in DB or creating the same services. It really feels mundane and a routine drill work.
2. But let's question first point, do we really have no way to have the innovative spectre in routine work. This is where a proactive engineer has an opportunity to stand out. It totally depends how they bring in innovative sparkle. This contribution may be on any domain be it security, data handling, analytics or UI.
3. So concluding remarks, it's just not the product and it's scale that makes the software engineering enticing but it's also the other way round where engineering can also play a leading role making the product interesting.
Be the change you want to see
1. I am building a product feature which basically requires me to copy paste most of my routine modules like creating similar entities in DB or creating the same services. It really feels mundane and a routine drill work.
2. But let's question first point, do we really have no way to have the innovative spectre in routine work. This is where a proactive engineer has an opportunity to stand out. It totally depends how they bring in innovative sparkle. This contribution may be on any domain be it security, data handling, analytics or UI.
3. So concluding remarks, it's just not the product and it's scale that makes the software engineering enticing but it's also the other way round where engineering can also play a leading role making the product interesting.
Be the change you want to see
Discover More
Curated from across
