Felienne Hermans recently gave a marvellous talk which relieved one of my lingering insecurities almost immediately – she told me that it was OK to spend time reading code, and that it was in fact a necessary precursor to being able to write code effectively.
I’ve recently joined Cogent as a Lead Developer and before that, I worked on Data related systems as a Data Engineer and as an Architect. I’d like to bring some of the knowledge and experience from these domains to the Cogent community and so I thought that cross posting this article (that also appears on my personal blog), would be a good way to start.
A co-worker and I were writing tests for a hook we’d created and we kept running the same warning. So we decided to dig a little deeper and work out what was really going on. What resulted was a wild ride through the inner workings of hooks, testing utilities, and how asynchronous events are handled in JavaScript. If you’re curious too, then keep reading.
High-performing cross-functional teams don’t happen all by themselves – they require work, a focus on empathy and a lot of trust.
Here’s what I’ve learned about looking after a team of software people during the rollercoaster ride that’s been 2020.
In March 2020, the shift from workplace to home office was as swift as it was sharp – there was hardly any time to prepare for what would become the globe’s greatest remote working experiment.
We acknowledge the traditional custodians of the land on which our offices stand and we pay our respects to elders past and present. We acknowledge the sorrow of the stolen generations and the impacts of colonisation on Aboriginal and Torres Strait Islander peoples. We also recognise the resilience, strength and pride of the Aboriginal and Torres Strait Islander communities.
We are inspired by Aboriginal and Torres Strait entrepreneurs, past and present.
Copyright - Cogent 2022
Level 1,673 Bourke St, Melbourne, Victoria, 3000