What's your job about?
Saab Australia is primarily a maritime software defence-based company, but I am aiding their venture into contributing more within the space industry.
My current work mainly consists of software development. Generally when I start my day I know what my work is and how it fits in the scope of both the project and the team. This is because my team discusses the team’s scope every fortnight. Specific tasks include: task refinement; code development; code reviews; and documentation.
Before any code development is started, a refinement must be done. This is where the task’s context is outlined, preferences discussed, and options weighed. This way, when I start writing code I already know what is wanted by the team and project stakeholders.
Once done, which could take a between a day to a fortnight, the changes I made must get reviewed. Some of my team will look over the changes and makes sure it both works and meets the task’s requirements. It is also a great time for knowledge sharing and refining the code. Other team members also add me to do their code reviews.
When the team is happy with my changes, I make them part of the main code and add them to the bigger system, and there they can be used by everyone. This is when I might need to do some documentation. This aids company-wide understanding of the project and/or work I have contributed to and can help stakeholders understand how their requirements are being met.
What's your background?
I grew up in Adelaide, but spent my holidays in the Mallee; bonding with my family and helping with farming; but mostly running around and creating epic adventures in my head.
During high-school I found I could excel in advanced subjects and enjoyed pushing my limits. The truth is, I had no idea what I wanted to do after school, so I focused on what I did well.
Eventually, that time came when my friends started applying for university. I never had an “ah-ha!” moment seize me and it hurt that my life after school was still a huge mystery. In hindsight, that “not knowing” kept my eyes open, and later, seeking “is this for me?” led me to adventures in China, Singapore and France.
At the time, I only knew how to be a student, so I went to university. Having done all the prerequisites, I picked engineering. Whatever an engineer did, I had no idea, but my teachers were supportive and robotics sounded fun.
Parts of the degree were definitely fun, but it was the aspects outside the degree’s core which were most beneficial. The opportunities (read uni emails!), the side-projects, and the mentors. Studying part of my degree overseas opened my eyes to new cultures and gave me a sense of independence.
When I returned, I knew I didn’t want to further my studies yet. I wanted to work and apply my insights in industry. So when I found my current graduate opportunity at Saab, I applied, and since then I have been building a year’s worth of experience in software development.
Could someone with a different background do your job?
Very much so, yes! In fact, the more diverse backgrounds the better. I mean this all contexts: cultural, career experience, gender, life experience, etc. At the end of the day, I have come to understand engineering (in all its disciplines) to basically translate to “problem solving”.
Of course having technique knowledge in the relevant field helps, but it is only a stepping stone and can be acquired in many ways.
More people with diverse perspectives and ways of thinking through problems, increases the likelihood that different solutions can be discussed, and ultimately increases the likelihood that the team can devise the most appropriate solution.
What's the coolest thing about your job?
I really do enjoy that moment, after the often lengthy and tiresome refinement and/or estimation process, when I can actually start writing code. After all the research, investigations, and discussions; I can sit-down and start developing code with a full understanding of what and how I am going to do it. With this understanding (and sometimes some good music), it can be so easy to “get in the zone” and the hours just fly by.
What are the limitations of your job?
Things go wrong. Code never just “works”. It’s frustrating when you just want it fixed, but nothing you are trying works. Despite five years of study and a year on-the-job; I am still learning and refining the best systematic approach to debugging code. Sometimes things break after you’ve added changes to the system; it’s not always major, but it is your responsibility to make sure it impacts system users as little as possible. Proper reviews and testing make this event rare, but things do slip through the cracks. Being able to think on your feet and manage emotions during crisis is extremely helpful.
3 pieces of advice for yourself when you were a student...
I want to tell my student self to relax. Don’t stress about finding the “perfectly right” way to do things. Getting anxious about what everyone else does and what one “should” be doing helps very little (if at all). But while I know she would listen, I know she would not know how to stop looking.
Instead, I would tell her “It’s ok to not know what you really want”. One of the best ways to find out is to simply give-it-a-go. Internal theories and looking outwards only goes so far. Focus instead on experiencing what you can.