What Can You Expect From Developers?

As a technology company, the most important thing we do is deliver real capabilities that solve our clients’ business problems quickly. This is the value they are looking for. As the year 2020 kicks in, it makes sense to pause and consider what are the key expectations Developers face on a regular basis. We’ve learned a lot and gained a wealth of experience in the IT industry over the years – and now we want to share it with you.

Always be ready for work and proactive

We have to deliver – that is what the business development and sales expect us to do. Yes, we use deadlines because they influence results. Achieving personal goals plays a role, too. Don’t be that person waiting for something to happen! Throw yourself into work and ask for more problems to solve, difficult tasks to crack, or additional User Stories.

Recognize the problem, get to know the client, understand the product

It’s crucial to understand the problems you are working on. That way you become a genuine part of the solution. Apply yourself to really master the product you are working on, inside and out. Finally, invest time and energy into communicating with the client – otherwise you’re simply not doing enough to understand the problem.

Production problems have the highest priority

‘We’ll get it done later’ is absolutely unacceptable. If your system is leaking data or production levels drop, then place this issue at the top of your queue and keep working on it until you find a way out. It may be painful at that very moment, but trust me when I tell you that esprit de corps and the sense of accomplishment that you and your team will feel after getting over the finishing line will be worth it.

Think like a lazy person

This one may sound weird – it’s not about being lazy when working but about the way in which you’re troubleshooting. Automate and optimize not only the product you’re building, but also your work environment, test configuration, toolchain, etc. Some of the best devs out there are quite lazy and are always looking for the most automated way to get the job done.

Learn to ask for support

Software development is a team sport – you slow the entire process down the longer you avoid asking for support. Attempt to figure it out yourself first, by all means! But learn to recognize when asking for support helps the team move forward.

The code must be testable, scalable, and efficient

Do you have a unit test at the ready? Are the test cases easy to execute? Have you used feature flags? Do you hard code CSS or is it configuration driven? Have you considered how the service will perform in low, medium and high load? Make sure you address questions like the ones above when coding. Go through your checklist before getting down to work. Always bear in mind that code which only works under certain restricted conditions is useless.

Everyone is responsible for code maintenance and quality improvement

It takes experience to learn and accept this way of thinking. Code is not the project – don’t ever think otherwise. You need to remain open to criticism and ideas from others. It’s your responsibility to improve previously unseen parts of the codebase when you interact with them for the first time.

Your code must be functional, easy to read, and perform the task at hand

Developers engage in massive debates concerning code reviews and what should be included in a pull request, even including the use of semicolons. However, it all makes sense: the code must be readable (i.e. easy to understand when accompanied by fitting comments) and must execute its function. Sure, these are absolute fundamentals but you should always keep them in mind.

Write code documentation in order to explain – then read it in order to understand

Yeah, you’ve got to do it. As you make strides in your career, you begin to spend more time on ensuring that your design and project intents are communicated properly. It’s also one of the best ways to onboard new team members efficiently. Writing and reading code documentation is part and parcel of your job. This way you’ll quickly get up to speed when joining a new project or learning a new technology – and avoid making common mistakes, too.

Put solutions above problems

Become part of the solution. If you identify problems regarding requirements, codebase, processes, or the team dynamics, then don’t ignore them and offer solutions. People appreciate it and are much more willing to take action when solutions are put forward as the problem is identified. Challenge yourself in a constructive way and be open to constructive feedback.

Your team is your responsibility

Be proactive, share ideas, support others. Your feedback must be constructive at all times. Feedback is crucial – it helps to grow and become better at doing one’s job. Although, in order for it to count, feedback must be conveyed in a way that improves work rather than the individual. A healthy debate is key, but try to engage in them within a well-oiled team that trusts and respects others. Nobody wants to work with someone rude, so be self-aware and avoid being that person.

Never stop learning

Technology keeps evolving and you need to keep apace with it. Never stop learning and never rest on your laurels. Challenge yourself and improve your competences. Share your experiences with your team.