Understanding business priorities as a software engineer

Understanding business priorities as a software engineer

I've come to realize that the expectation junior developers have about the workplace is vastly different from the reality they meet and sometimes this arises as a result of lack of information about the realities of being employed to code.

I was observing the conversation in a group chat I'm on where a couple software engineers were complaining about senior software engineers and how senior devs are resistant to change and don't know or use any new frameworks.

At that point I felt the need to share my perspective. I believe senior devs (unlike junior devs) are tasked with more than code, they're constantly interfacing with the client and have to maintain a business view as well as an engineer's view. Clients in established businesses are quite wary about changes, the average belief is that if it's not broken don't fix it.

You typically get more innovation from senior devs in software solution companies and senior devs in startups. I also believe senior devs ought to communicate their priorities to their team members. A lot of junior devs are excited to prove their skill and are sometimes disappointed when they don't get to pull all those stunts they practiced. It's a hard reality for them that sometimes your company doesn't want any gymnastics from you, all they want is a stable and secure system.