Happy new year!! Hereâs to an amazing 2021 - weâve all earned it, I think
Weâre hitting the ground running here at CTO Craft, with a new series of Bytes events (more to come on that next week), as well as the roll-out of our CTO Craft Labs workshops. If youâd like to take a look, head here for some more info and an early-bird discount:
Weâve been running our Zero to CTO blog series for over two years now, with some amazing leaders - here are some of the most popular interviews over the last year:
With this report, we sought to better understand developer happiness and well-being by exploring four key factors: career, quality of life, social freedoms and community.
Ever thought about what makes some engineering teams highly productive as compared to others? What such teams do differently than others? Can it be due to difference in skills of engineers in different teams?
In this article I will talk about how a high-performance engineering team at Moonpig adapted to a remote working environment, whilst they improved their ways of working, and continued to deliver on improving the experience we provide to our customers.
Googleâs internal management approach has sustained and scaled pretty impressively over the years. Quantitative goal-setting, setting stretch targets â these principles are as evident in the 2020s as they were when I arrived in 2003.
Moreover, numerous studies have found that trust is critical to team success. And, this is most true as remote managers are struggling with trust issues during COVID-10. Thankfully, you can use the following 7 strategies to turn this around.
Moving up the ranks as an engineer is something that many accomplish. From the time I was nine years old, I wanted to be at the top of the technical ladder. My father gave me my first few lessons onâŠ
There has been a lot said about how women have done a better job leading during the Covid-19 crisis than men. According to an analysis of 360-degree assessments conducted between March and June of this year, women were rated by those who work with them as more effective.
Should you work hard? Depending on your definition of âhard,â itâs a controversial question. Letâs assume a baseline level of hardness is roughly 40 hours per week of mostly focused work.
The systems we build are composed of many pieces. From mobile apps, to domains, to user journeys. How should we slice up the system and divide responsibilities among teams in our organisation?
Thereâs this idea that having better programming languages will make software development much easier and more productive. That no doubt used to be true, back when assembly or Fortran came along.
Co-author of the âLean Software Development,â Mary Poppendieck warned attendees of Agile Tour London in an end of day lean coffee that backlogs are a sign of an inefficient team. But thatâs OK.
I worked as a developer using Waterfall for exactly 9 months. I was 22 years old and it was my first programmer job and first corporate environment. This place was old school. Like suit-wearing, personal cubicle type old school.
One of the biggest time costs in software development is understanding how a system works. And the problem may be growing. Systems are getting more complex yet our ability to understand them doesnât seem to be growing at the same rate.
Tweet
Share