Onboarding

What does a day in life of a software developer look like

Chenosis
POSTED 3 months ago

A developer’s nine to Five in a nutshell, in the morning:
Getting a coffee cup,  snoop on other devs, get some online shopping done.

Blog 1.png 315.82 KB


During the day: Furiously typing on laptop, getting more coffee, celebrating at laptop.

Blog 2.png 333.72 KB


Later on in the day
Talking in meetings, working on a bus/train, saving worlds!

Blog 3.png 346.4 KB
 


It’s more than just coding! Here’s what to tell that aunty who thinks you can fix her PC…
 
The image of a figure in a hoodie hacking away in a dark garage corner is long outdated. By now, the digital life we’ve come to embrace has shed some light on the world behind the apps we rely on and love. Everyone may not know the terms behind the tools they use, but everyone knows who Mark Zuckerberg is and it’s common knowledge that twenty-somethings make millions off apps. Those who take it a step further, making the digital world their own, learning the languages that program the software we interact with everyday, they know more. They know that the future will be powered by the people who code.
 
Developers aim high and work hard to earn a place as an architect of the digital world. Often, they arrive at agencies or corporate companies to a bustle of marketing people barking sprint deadlines, creatives demanding innovation, HR asking IT questions and other developers who would gladly say hi if they had a minute to look up from their screens.
 
Active State compiled a survey pre-pandemic which features data about what developers do most of the time when they aren’t coding (read it here). Take a look:
There may not be time to clarify the details around typical office terms they didn’t teach in varsity. This list will help to make your first few days slightly less confusing.
 
Software design/architecting
Described best by medium.com, software architecture focuses on developing the skeleton and high-level infrastructure of software. Software design concentrates on code level design.
 
This part of the job is all about building a strong foundation for your application so your team can thank you later.
 
Stand-up meeting
Stand-up or standing meetings come from a way of working known as Agile. Usually set at the beginning of the work day, team members literally stand during these meetings because they’re supposed to be short. Be prepared to tell the rest of the team which tasks you’ve completed, what you’re currently working on and what you plan to work on next.

Stand-ups are a great way to keep everyone accountable for their work and squash potential stumbling blocks before they trip up the whole project. (source: kanbanize)
 
Testing
Straightforward as it may seem, it’s important to understand the different types of tests and the reasons we perform them. IBM lists 8 different types of software tests, including acceptance testing to verify whether the system works as intended and stress testing to see how much strain the platform can take before it fails.
 
A developer that takes testing seriously saves companies time and money in the long run.
 
Resolving Bugs
Even digital ecosystems are prone to bugs, so developers are also exterminators! Bugs are common in every digital platform and it’s the developer’s job to squash them before visitors notice and flee to another website. According to techopedia, a bug fix is also called a program temporary fix (PTF).  
 
Other team members and the clients you built the platform for will log a ticket if they spot an error or glitch so you can be made aware and solve the problem.
 
Performing maintenance
Once a solution has gone live, the developer needs to keep making improvements to provide a great user experience. This involves increasing site speed, resolving bugs and ensuring optimal functionality across the platform. According to Thales, software maintenance is also about modifying and updating the software to keep up with customer needs.
 
The extent to which maintenance is performed will depend on your client’s budget and their vision for the future of the platform.
 
Investigating security issues
Save yourself and clients from future disasters by making security a priority from day 1. Security is a major concern for individuals and businesses that rely on digital services to keep private information private.
 
According to research gate, security risk assessments should be integrated into each phase of software development.   


Socialising ideas
Part of a developer’s role involves getting colleagues and/or clients to buy in to an idea or way of working. This goes beyond just communicating the idea; it’s about getting other people involved so you can gather feedback and additional ideas.
 
A successfully socialised idea will take on a life of its own. The team at Vable have some tips to help you get it right.  
 
Creating new instances
The programs you build are objects and instances are copies of that object. Techopedia explains an instance as an occurrence of anything where the basic structure stays the same but the attributes differ.
 
In the case of web pages that use the same structure but the details differ, creating instances can save time and make testing easier later on.
 
Did we miss a term you’re unsure about? Comment and let us know so we can help you understand!