It has been rewarding to see QA team members learn and grow in their roles, and it is really satisfying when a software engineer advocates a quality “Test-first” approach.
As a software engineer my responsibilities are primarily writing code and code reviews, some mentoring of more junior team members, contributing to team planning and outside of the direct team I am also involved in the engineering recruitment process.
It's been quite fast paced and challenging at the moment, which I love. But with speed comes tradeoffs and I've been wondering if I've crept into some bad practices. So today, I wanted to see if carving some carrots into a recorder would help me mentally reset and be better at my job.
We replaced a random-meet-up Slack bot with a slim clone we built during hackday. We changed what we
It wasn’t too long though before I got really frustrated with the structured learning at University. I loved Engineering for the creativity and Uni just wasn’t giving me the space.
We recently had a squad shuffle to better focus on getting features to customers fast. So now my squad is smaller than I'm used to but the results have been surprising.
We introduced Vue.js to enable our customers to use a new feature. The framework helped us hit our deadline and write maintainable code!
Research shows that commit comments written on Mondays are more negative than other days of the week. Let's look at how this is calculated.
Technology is constantly changing and we want to stay ahead of the game, but how do we do this in a safe, and more importantly fun way? Hello Hackday!
As engineers, we strive to ship code fast. This comes with a cost we have to pay later. UI and front end are often overlooked in that process, but investing a bit of effort into creating a ready-to-evolve front end can save us time and effort when our applications change.