Summarized using AI

Making the Leap into Teach Leadership

Tanaka Mutakwa • June 09, 2021 • online • Talk

In the talk "Making the Leap into Tech Leadership," Tanaka Mutakwa, VP of Engineering at Names and Faces, addresses the challenges developers face when transitioning from individual contributor roles to technology leadership positions. He emphasizes that, while technical skills may contribute to a successful engineering career, they do not fully prepare individuals for the varied responsibilities of leadership.

Key points discussed include:
- Different Roles in Tech Leadership: Various titles such as CTO, engineering manager, or VP are explored, highlighting their responsibilities including team management and delivering on projects.
- Common Mistakes New Leaders Make: Mutakwa outlines frequent pitfalls, such as:
- Falling back into Coding: Many new tech leaders default to coding rather than focusing on team management and coordination.
- Centralizing Decisions: Assuming they must make all technical decisions, leading to bottlenecks and preventing team empowerment.
- Neglecting Team Culture: Failing to cultivate a positive team culture hinders team collaboration and morale.
- Poor Communication: New leaders often struggle to communicate with non-technical stakeholders, missing the need to explain technical terms in simple language.
- Time Management Issues: New leaders often overcommit, leading to burnout.
- Assuming They Need All the Answers: This mentality can lead to stress, as effective leaders should facilitate a collaborative environment.
- Isolation: Many leaders find themselves feeling isolated due to the nature of their roles, emphasizing the need for peer support.
- Ignoring Individual Differences Among Team Members: Acknowledging that each team member has unique needs is crucial for effective leadership.
- Lack of Seeking Feedback: Unlike coding, where feedback is immediate, leadership requires consistent feedback mechanisms to gauge effectiveness.

Tanaka underscores that despite the challenges, tech leadership can be rewarding. Successful leaders positively impact team dynamics and contribute to individuals' career growth. He encourages aspiring leaders to prepare prior to stepping into leadership roles by engaging in mentorship, learning from current leaders, and seeking resources.

In conclusion, Tanaka stresses that successful tech leaders foster a nurturing environment and facilitate their team's growth while also seeking support and feedback for themselves. Leadership is a substantial role that, when approached with dedication, can yield significant fulfillment in one's career path.

Making the Leap into Teach Leadership
Tanaka Mutakwa • online • Talk

Date: June 09, 2021
Published: unknown
Announced: unknown

Taking on a technology leadership role is a tough transition for any developer, because only part of the skills and experience you had as a developer prepares you for the expectations of a new role. In this talk I will share common challenges new tech leaders face and how to tackle them.

This talk was delivered at EMEA on Rails, a virtual mega-meetup which took place on June 9, 2021.

EMEA on Rails 2021

00:00:18.320 thank you so much for the intro uh as was said in the intro my name is
00:00:23.680 tanaka i work as a vp of engineering at a startup called names and faces
00:00:30.880 in fact we basically build a simple visual employee directory for companies
00:00:37.920 so that employees at their own companies can know uzu at their own organization and figure out where everyone fits in
00:00:45.920 it's a sas application so anyone companies buy the product from us and
00:00:51.280 then we set up a directory of all their employees for them
00:00:56.399 today i'm going to be talking about making the leap and to take leadership which is a topic all about
00:01:03.840 people who are moving from an individual contributor role in software engineering and
00:01:11.360 stepping up into a technology leadership role and a technology leadership role can
00:01:16.880 really various companies into what it actually is yeah i'm showing a couple of titles that
00:01:22.400 someone could have when they are acting in the capacity of a technology leadership role so most common is
00:01:28.640 usually cto so you're really at the top of the organization but people such as engineering managers director and vp of
00:01:35.360 engineering even sometimes senior engineers or senior developers are doing a lot of
00:01:41.119 leading of their teams and they're working in these roles it's really a role where you now have the
00:01:46.720 responsibility of the team that you work with and their delivery and depending on
00:01:52.320 your role sometimes that also comes with people aspects to it so for reporting into you and you doing their career
00:01:58.560 growth management and also administrative management such as approving leave and
00:02:04.960 motivating to get salary increases and things like that um
00:02:10.560 so yeah this is sort of the typical route in which engineers end up in a
00:02:16.879 in a tech leadership role um you you grow very well in your in your
00:02:22.400 individual contributor software engineer career uh you're really good at what you do from a technical coding side and
00:02:29.280 people senior management your company notices that a lot of people come to you and ask
00:02:35.519 questions around how to do things and get out from a technical perspective and
00:02:41.440 management decides that perhaps this person should lead this team so they call you up one day and they say
00:02:48.720 well you're promoted you're now the tech lead of this team or the engineering manager of this team
00:02:54.000 because we've noticed that you're really really good at coding and hopefully that that change and the
00:03:00.800 title or anything comes with an increase in responsibility and and your salary
00:03:06.159 and most people accept the role and not quite sure what they are what they're getting into
00:03:12.000 but a lot of people would do go through this route quickly realize that
00:03:17.280 there is quite a significant difference between the or the skills that got you
00:03:23.280 and that got you really good at your engineering and the skills that i needed in sort of managerial or tech leadership
00:03:29.840 role there are some things that cross over but there is a lot more things that come
00:03:35.280 across when you're now in the tech leadership role that deals with like managing people conflicts between people motivating
00:03:42.239 people caring about people's career growth those are less individualized skills but
00:03:47.760 more about you thinking about a whole team versus about yourself as an individual and growing
00:03:53.519 so a lot of leaders who get promoted because they're really good at technical skills and they get into tech leadership
00:03:58.879 role usually end up getting frustrated that they they're not really good at
00:04:04.080 this tech leadership thing and they really prefer what they were really good at before
00:04:10.000 and in some companies you would be fortunate enough to have been prepared beforehand like as your
00:04:17.600 lead as you're growing in your individual software individual contributor career you get prepared for
00:04:22.639 these tech leadership roles so that by the time you get the position you're ready for it or sometimes as soon as you
00:04:28.400 then get promoted into that role or selected to be a tech leader they put
00:04:33.919 you through training to help you sort of grow in the managerial side of things but a lot of people don't get that so as
00:04:40.320 i say they get frustrated in the role and the people who they're leading also get frustrated because those people
00:04:45.840 quickly notice that their tech leader doesn't really have the leadership skills even though they have the
00:04:51.360 technical skills so in this talk i'm just going to share
00:04:57.360 quite a number of common mistakes that new technology leaders make when they get
00:05:03.199 when they start acting up in that role as a way to sort of prepare people who are stepping up into those roles for
00:05:10.160 things to watch out for and things to address when they get into those tech leadership roles
00:05:17.199 so the first common mistake is coding full-time this is the most obvious one because you
00:05:24.479 do get really good at coding while you're an individual contributor it is the reason you were noticed it's the
00:05:29.759 reason you ended up getting promoted so it's your default place where you find satisfaction because you know you're
00:05:36.000 really good at coding so you end up defaulting to going back to that and not
00:05:41.039 concentrating on anything else that i'll take leadership responsibility requires
00:05:46.320 so this is one of the first common mistakes and i think it's important as soon as you become a tech leader to realize that you're not measured on your
00:05:53.039 output alone anymore you actually measured on your full team's output so even if you are doing well on the coding
00:05:59.280 but the rest of your team is not delivering you're actually failing as a as a tech leader so that's something to
00:06:04.720 be aware of and to be very careful about just falling into the trap of coding full-time
00:06:11.919 another mistake is because now you're a tech leader thinking you and who has to make all the
00:06:17.199 technical decisions yes you are promoted because you are really strong and you're really good at the
00:06:23.199 technical side of things but it doesn't mean because you are the tech leader now you are the master of all and no one
00:06:29.680 else in the team can make technical decisions and everything has to go through you for multiple reasons one is you quickly
00:06:36.080 become a bottleneck if all the technical decisions have to go through you because the whole team has to wait for your availability all the time before they
00:06:42.880 can make decisions the second problem is if you are making all the technical decisions then how are you empowering
00:06:49.360 your team to grow if if other people don't get to sort of learn from what the decisions they make
00:06:55.360 the mistakes they make and the positive decisions that they make for the company so to empower people you need to be able
00:07:01.520 to release a bit of that you need to be able to guide of course and still remain technically strong but
00:07:07.599 you're not responsible for making all the technical decisions
00:07:12.960 and then another common mistake is forgetting about cultivating team culture and not taking care of your
00:07:19.360 people uh leaving problems to someone else as an individual contributor often
00:07:25.440 things get sorted out by someone else either whatever is your team lead or your manager or sometimes it's even your
00:07:32.080 talent team or team or your hr department that sorts out a lot of people issues and cultural issues in
00:07:37.759 your team but as a leader you are responsible for setting the tone you're responsible for building a
00:07:43.919 positive team culture and helping your team grow and helping your team jowl together and collaborate well together
00:07:50.479 you're also responsible for taking care of your people making sure their careers are growing uh supporting them making
00:07:56.160 sure they're happy as the company and where their problems you are supposed to be the one who steps in there and make
00:08:01.680 sure you unblock people and help resolve any conflicts that occur it's once you
00:08:06.720 are in that position you can't just sit and leave it to someone else because in the past you used to see problems get
00:08:12.479 sorted without you stepping in
00:08:18.400 then there's also talking only tech as an individual contributor software engineer you're often in a team with
00:08:25.840 other software engineers and your discussions often center around technology and you go you can go very
00:08:32.159 deep in your discussions around tech and you don't need to sort of bring your discussions a level higher
00:08:38.800 for people that are not technical but once you get into a tech leadership position you are sort of the face of
00:08:45.040 your team to the rest of the organization and sometimes you will end up speaking to
00:08:50.399 people who are not technically or not technical or not tech savvy
00:08:55.600 work from other departments but need information around what you're building or when things will be delivered and
00:09:01.519 you're supposed to be able to communicate technical things in a simple understandable way so you shouldn't
00:09:08.399 default to only speaking to tech people and only speaking the technical language
00:09:13.680 you want to learn how to communicate with the rest of the company and also being able to communicate with clarity
00:09:20.000 and bring technical concepts to a level in which everyone can understand them
00:09:28.480 time management also is very critical it's also a common mistake in that
00:09:34.240 people who've just become tech leaders say yes to everything they're constantly reacting their key of work is always
00:09:41.040 full and i think it's important when it comes to time management to be able to
00:09:46.320 to figure out what are the most important things that you really have to work on yourself and prioritize
00:09:52.560 what things can you delegate to other team members so that they can help you spread the
00:09:58.000 load and then on the final note and very important one is what things can you say no to right now that you can always pick
00:10:04.240 up later because not everything needs to be addressed right now a lot of noise does come through to you as a tech lead
00:10:10.800 you can wake up and there's lots of bugs that people want fixed there's requests on like what's going on with the
00:10:16.240 features that are getting built why are they delayed um someone might come in the morning and
00:10:22.000 tell you they want they've got an offer at another company and now you need to sit down and convince them to stay at
00:10:27.360 your company for different reasons and that's a lot that can happen and you might get lost with all the although all
00:10:34.000 that constant pressure and if you don't manage your time correctly then you won't be able to it's not sustainable
00:10:41.279 you either burn out or you really be frustrated in the role
00:10:49.040 and then another common mistake is assuming you need to have all the answers
00:10:54.959 so it's not embarrassing it may appear like it's embarrassing if you are the leader
00:11:00.560 of a team and someone asks you a question but you actually do not know the answer but that this is the point in which you
00:11:06.320 actually need to be vulnerable enough to show your team that you can be honest and open to say i actually don't know
00:11:12.160 the answer on that does anyone else know or should we investigate and try and understand
00:11:18.079 how to solve that assuming assuming that because you know the technique that you need to have all the answers is also another recipe for
00:11:26.320 for either not being as honest with your team or always appearing stressed out
00:11:31.680 because you need to know everything and trying to understand everything again possibly leading you to burning out because you're trying to have a handle
00:11:38.560 on everything that is going on so it is okay in fact if anything if tech leader you want to be able to
00:11:45.600 build a team in which everyone around you eventually at some point can get better
00:11:52.399 than what what you were or what you are right now that that is a sign of a good leader so if you ever have to leave you
00:11:59.120 know you've left that team in a very good space so you don't need to know all the answers
00:12:04.480 and you need to be able to be open and vulnerable enough with your team
00:12:11.519 tech leadership can also be very lonely you can easily isolate yourself
00:12:17.040 if it's a small company you might be the only tech leader and because you don't spend
00:12:22.399 you're now in a different role and you don't spend all your time with the rest of the individual contributing software engineers you can easily end up
00:12:29.200 isolating yourself and you don't have someone else to communicate with about how to solve sort of the leadership
00:12:34.639 problems you're facing so that's something to be careful of if if you are in a better in a bigger
00:12:40.000 company where there are multiple tech leads or multiple engineering managers uh try form a team together and
00:12:46.639 and always help each other when you're dealing with different issues on your team and chat together if you are in a smaller company you can always
00:12:54.079 chat with other tech leaders from other companies and identify meet people at different
00:12:59.120 meetups or something and and i and always you can always meet up outside or jump on calls or have coffee
00:13:05.920 and just chat about the problems you're experiencing so that at least you've got some support i would also suggest getting a
00:13:12.639 leadership mentor and the leadership mentor does not necessarily have to be someone who comes from a technical
00:13:18.560 background it can be any because leadership is something you find across the world despite it being um it's not
00:13:25.200 only a technology thing so you can't get a mentor who's even in another space but understands leadership and understands
00:13:31.440 people well and they can guide you and help you with some of the issues that you'll be dealing with the key thing to
00:13:36.560 remember is just not to isolate yourself and feel like everything you're doing you have to figure out by yourself
00:13:46.240 another common thing is thinking mistake again is thinking people are the same
00:13:51.440 so as engineers we we like to we
00:13:56.720 we all know about the single response principle so we do like to to write something once and that can be
00:14:03.199 used many times and a mistake you can make when you get into a tech leadership role is assuming
00:14:08.800 that all the people are the same and the solution or a suggestion that worked with some of the past will always work
00:14:14.560 with another person but individuals are very different they've got different motivations they've got different goals
00:14:20.160 with their careers they've got different things that can frustrate them and it's important to understand each of the
00:14:26.720 people that you work with as a tech leader to understand what what what motivates them what frustrates them and you'll be
00:14:33.839 able to current solutions as depending on the individual so it's important to have
00:14:39.760 consistent check-ins with people understand their backgrounds understand where they're trying to take their
00:14:44.959 career and you'll be able to motivate correctly depending on each individual
00:14:53.360 and then not seeking feedback from your team about you is also a common mistake and
00:15:00.399 it can also end up frustrating you a lot as a leader because leadership feedback takes a long time to
00:15:08.079 come back as a software engineer if you wake up in the morning and you
00:15:13.360 pick up a ticket and you write some code and you release that code you get immediate feedback because you know the
00:15:18.880 work you did that day and perhaps you got into production on that same day and people are already using it so your feedback loop is very quick whereas a
00:15:25.920 tech leader it can take months or sometimes even longer before you see the impact of the
00:15:31.920 changes you're making sometimes the changes you're making are around how does our team work what are the processes or how or helping someone grow
00:15:40.000 their career helping a junior engineer develop their skills that can take time and sometimes you're not even sure if
00:15:46.560 everything you're suggesting is the reason behind that person growing so one of the best ways to actually
00:15:52.880 see how well you're doing is to ask your team constantly for feedback around your leadership like
00:15:59.600 could i be doing something better how am i doing how am i supporting you am i supporting you well is there something i
00:16:05.680 could have done better and that's the best way for you to not end up feeling
00:16:11.120 the pain of no feedback and not be quite sure how well you are doing as a leader
00:16:19.120 so having heard all those sort of challenges that a tech leader can face by taking up this
00:16:26.240 role a number of you may be wondering why anyone would ever want to step into this
00:16:31.920 complicated space as opposed to just continuing in their journey as a software engineer
00:16:37.680 i understand it is complicated but at the same time it is very fulfilling when it works
00:16:43.680 really well if you imagine scenarios where perhaps a team was not really performing
00:16:48.880 well and you stepped in as a tech leader and managed to get the team collaborating working well together and delivering high quality
00:16:56.000 solutions frequently that can be really fulfilling to know that you are able to achieve
00:17:01.279 that it's also very fulfilling when you're able to grow someone's career and you see them thriving in their future
00:17:07.120 roles and you know you had an impact in their career so as much as it can be challenging i
00:17:12.799 think with the right learnings and with the right knowledge and doing it very well you can have a
00:17:18.000 massive impact in software engineers careers
00:17:23.280 and if anyone's listening who is not yet a tech leader and has thoughts in their heads of being
00:17:30.160 one in the future this is actually the perfect time for you to start practicing and learning about tech leadership
00:17:36.960 as i mentioned earlier in the talk usually people only start doing that once they get into the raw and they're
00:17:42.799 already starting to get frustrated but it's better if you're well prepared before you even get into that role so
00:17:48.080 there's quite a lot of things you can already start doing now before you are officially given the title
00:17:54.160 to start practicing and preparing yourself to be a good tech leader in the future suggestions could be mentoring
00:17:59.760 some engineers at your company setting up a whole internship program at your company so you get a whole
00:18:06.400 perspective on how to recruit how to market the company once the interns are in how to onboard
00:18:12.160 them and then how to off-board them when they leave there's so many things in that space there's also a lot of resources and things you could start
00:18:18.559 learning from and just getting a mentos already a tech leader and learning about what their day-to-day looks like so
00:18:24.720 there's a lot you can do in preparation for getting into these roles
00:18:30.559 and for existing tech leaders there's always a lot of more material out there that you can use to learn
00:18:38.240 and keep growing in this tech leadership journey i've i've added a couple of examples
00:18:44.320 just so people know what where else you can look for these sort of tech leadership learnings and what resources
00:18:50.880 you can sort of use so there's newsletters and podcasts there's quite a number of technology
00:18:57.280 leadership newsletters and podcasts out there now the newsletters are usually released either once a week or once a
00:19:03.280 month and usually have curated content on good tech leadership material that's been found
00:19:09.600 and you just need to subscribe to get access to them there's also quite a number of podcasts that also invite guests who are in the
00:19:16.559 tech leadership spaces and they discuss different approaches they use to motivate and manage people in their tech
00:19:22.960 space and their journey isn't to take leadership so a lot to learn in that space so
00:19:28.160 you can always do a search if there's some here that i've listed but can always do a wide search for
00:19:33.200 technology leadership podcasts or newsletters there's always books one of the best
00:19:38.240 ways to learn so just reading books that talk about technology leadership these
00:19:43.360 are some of my favorite books the ones i've read um that also teach you again about like
00:19:49.120 different examples of how people have set up a culture at their companies how people got into a tech leadership
00:19:55.600 role from their software engineering background um and yeah and what sort of
00:20:02.240 practices you can have in place to motivate your team and everything so books are also a very good
00:20:07.600 knowledge space and then finally i would encourage people to also look
00:20:13.039 out for in their communities for meetups and conferences that are geared towards technology
00:20:18.880 leadership there's always there's always there's always a lot to learn and good
00:20:25.440 people to meet who've got the same interests in those technology leadership communities
00:20:31.679 we've got a tech leadership meet-up in cape town which we used to do in person until the pandemic but now we actually do online
00:20:38.320 so anyone can join from anywhere it's on the first tuesday of each month and you can find out details around it if you go
00:20:44.640 to leadership x on twitter the lead developer conference is the lead dev they have a website and they've
00:20:51.679 got lots of in-person and videos and blog posts and for supporting
00:20:57.440 tech leadership that's one of the best communities out there a couple of communities that are that have slack
00:21:03.919 communities where people can just chat and there's lots of channels around technology leadership that you can step into
00:21:12.720 and then i just thought i'd note that with technology leadership
00:21:18.080 if you're not if it's something you're not interested in as a and you are one of those software engineers who's more
00:21:24.240 interested in the technical route and going deep with technology don't feel the pressure to jump into a
00:21:30.799 technology leadership role or management role specifically just because
00:21:35.840 of the money um in the past years maybe there was a bit of a skew that people get into those
00:21:42.080 roles got paid more but now a lot of good companies have created parallel tracks for those who are not going to
00:21:48.640 sort of a management role and those who want to step into a deeper technology role so
00:21:56.320 it's it's always best for people who are interested in technology leadership and interested in people and know they'll
00:22:02.400 that's what they prefer and they would really like to be good at that to step in the roles uh the motivation should
00:22:08.400 not be about trying to earn more money to get into those roles
00:22:15.280 and just to close off i'm sure some of you have heard these sort of sayings
00:22:20.640 so people actually don't leave bad jobs they they leave bad managers and leaders
00:22:26.400 so it's important for us if you are in a tech leadership role you're interested in getting into one in the future how
00:22:32.320 you show up can really set the tone for how your company does and then another one is there's a high
00:22:38.799 chance no one will remember the feature you built in 20 years but people do remember their managers
00:22:44.640 especially those who mentored them at the start of their career so again bringing back that idea that tech
00:22:50.559 leadership can be fulfilling and you can have a massive impact on people's careers
00:22:58.720 and that's it from my side again i said earlier my name is tanaka
00:23:05.440 i work as a vp of engineering at names and faces if you want to chat
00:23:10.720 i'm on twitter as at general mutakwa always keen to connect with different
00:23:15.919 people in the tech community and i also occasionally write on my blog here at mutacoi.com
00:23:23.440 thank you
00:23:31.039 thank you very much for excellent talk we have about 10 minutes for
00:23:38.159 questions so i want to thank the chat
00:23:44.799 uh do we have any questions
00:23:58.960 so i guess maybe i can start off um
00:24:05.679 other kind of differences in doing tech leadership i guess in africa south africa
00:24:11.440 as compared to say other parts of the world um any advice you have in that
00:24:16.799 area i think it's
00:24:21.840 i think it's mostly similar i mean leadership is quite universal that's why i even said
00:24:30.799 even outside of technology you can get mentored by someone who's leading a team at
00:24:36.240 at a company and they're doing they're not doing technology because i think the principles of
00:24:41.679 helping people grow their skills motivating people understanding and building trust with
00:24:47.919 your people all remain the same i think what may differ as you go across
00:24:54.320 the world and going to different places might be cultural approaches to things which obviously you have to be aware of
00:25:00.240 and conscious of um if in certain places there's a way to sort of speak or a way you you motivate
00:25:07.679 that maybe it's different in a different country that's maybe the things that one would
00:25:12.960 want to be aware of and learn but generally from the material i have learned from
00:25:19.360 and and looked at some of it as a lot of it has actually
00:25:24.880 not been from south african leaders but it applies to
00:25:30.559 the teams here in the same way that some content that's created by people who are in the leadership space here in africa
00:25:37.919 can be used by someone who's outside i think mostly there's quite a big
00:25:43.360 overlap except i think the one thing to keep an eye on is any cultural differences and nuances that you want to
00:25:49.120 learn about
00:25:55.440 thank you uh any other question
00:26:04.799 also feel free to just unmute yourself because we're not so many and i can ask in person
00:26:32.559 so in terms of your writing um
00:26:38.799 is this something that you think people should do is it a good way to communicate with the broader world
00:26:44.480 uh has it enabled you to grow as
00:26:50.840 well yeah i think there's many
00:26:56.799 benefits of writing and it depends what you're trying to to achieve
00:27:02.720 at the very basic i think just writing to be able to cr create
00:27:07.840 clarity of thought in your head is important and be a massive benefit so
00:27:14.400 you might not publish it with the goal of looking for hundreds of thousands of readers on your material but then when
00:27:21.600 you write something and you put it out in the world you usually have to have a
00:27:27.200 a sort of a set of thoughts that you are committing to and sometimes you might need to research a
00:27:34.159 bit more to understand something fully before you write it down which is where the learning comes in or sometimes just
00:27:39.520 in outputting it out of your head you and you're writing it in a way in which someone who doesn't understand the
00:27:45.440 concept can learn from you so you have to distill the topic into such a simple way
00:27:51.760 that it makes it even clearer in your head the way you understand it so
00:27:57.200 i think that's one of the biggest benefit of just writing is just that bringing that clarity of thoughts especially if there's like lots of
00:28:02.559 different ideas that are in your head and you're not quite certain which direction to go then of course there's for
00:28:09.600 for education purposes where you've got some deep knowledge in a particular area and you want to help the
00:28:15.679 rest of the community or the rest of the world um understand that topic and that's also
00:28:21.760 very beneficial like i mean now we are we we know the internet is like widely
00:28:27.679 spread now and it's a quick way in which i can be in south africa and write something and people across the world
00:28:34.399 can read that material as soon as i published it so this is obviously opened
00:28:40.080 up that that ability for you to to share any deep knowledge you have and and all other people out there who are also on
00:28:47.039 the same journey perhaps you you are on a few years back um
00:28:52.240 get up to speed so i think those are the the main benefits it also helps you build your profile as an engineer
00:29:00.080 when people are recruiting they will perhaps look at what else do you do what's your profile like online and if
00:29:07.120 you do show the interest in sharing the stuff you do it can help them understand you a
00:29:13.279 bit more but it also shows that you you are open to helping the the rest of the developer community
00:29:20.080 so yeah so lots lots of benefits to writing i would i would always encourage people to to try it out just even if it's just
00:29:27.440 a case of they're not really trying to share it too far out publicly
00:29:35.600 thank you
00:29:47.600 so we have another five minutes or so and then uh
00:29:53.200 i have a session where uh can meet people in different meetups
00:30:00.000 um so if there's questions feel free to ask
00:30:08.799 i'm curious you said that uh you of course have to maybe cut back on a little bit of
00:30:14.559 uh keeping up with technological developments how do you balance that
00:30:19.679 um i mean even as a dev you can't really know everything um
00:30:25.679 so that's always a limitation uh but i guess one still maybe has to have fear or
00:30:33.520 what might be good or bad technical decisions um and those
00:30:39.120 maybe you're not doing as much active development or any active development
00:30:47.840 yeah i think that's that's a good question um i think
00:30:53.120 as a start the answer i'll give to that is it's
00:30:58.480 when you're growing in your software engineering career it's good to have a good understanding of just the software
00:31:05.200 development fundamental principles because a lot of things sit on top of those so
00:31:12.640 maybe back in the day api calls used to be made using soap and then
00:31:19.440 the rest came and everyone's like oh race is better then graphql is now
00:31:24.960 people are talking about graphql there's another option but at the end of the day what you need
00:31:31.120 to understand fundamentally is what's what's the purpose of these api calls and
00:31:37.120 and what are the things that define a good api and regardless of which one version
00:31:44.480 you're using or which type you're using something like good documentation is still
00:31:49.919 important so as you step away from the the idea where
00:31:56.000 i'm going with this is as you step away from the sort of day-to-day coding but now you're
00:32:02.159 also still involved in helping the direction of the team and everything there are people who are now going to be
00:32:08.240 in your team who are going to be the sort of underground coding experts but when you chat with them and you try
00:32:15.039 understand whether they're making the right calls and everything you've got the right sort of questions you can ask
00:32:20.559 so how are we doing documentation how easy is it you want us to move to this new technology how easy is it for us to
00:32:26.159 to do documentation with it um how do we handle errors and how do the errors get
00:32:31.360 surfaced and things like that so that's the the fundamental principles
00:32:36.559 will really help you in in the long run and then it also help you quickly evaluate
00:32:43.679 decisions and technologies that your team is making despite you not being like actually writing the full lines of
00:32:50.159 code that uh that are getting used and then the other one is obviously using your team
00:32:55.679 to gain as much context as possible that's why you want to constantly check in with your team
00:33:00.880 they'll help you they'll be explaining to you why do they want to do things or how they're approaching things and
00:33:06.399 you'll be looking at it from the lens of are they any risks in the way things are getting done
00:33:11.440 and you actually can learn a lot from that um so you don't only of course if you had
00:33:17.519 to then go and write that code yourself it might take you longer because you need to fully understand and learn the
00:33:22.960 syntax or how things are getting done but at the higher level if you're able to explain
00:33:28.960 how your team is doing things and why choices they made and you're able to influence a certain direction if you see something
00:33:35.440 is a bit off so what you just need to sort of let go of a biz
00:33:40.880 if you had to do it yourself uh how long would it take you it's
00:33:46.080 probably not going to take you as quick as someone who's coding every day and i think that's the sort of trade-off
00:33:52.640 of leadership is as you step up in the leadership ladder
00:33:58.159 and your responsibilities become more about driving strategy and direction
00:34:03.519 you let go of being able to execute on the ground and like do things
00:34:08.960 on the ground yourself but you've got more leverage
00:34:14.560 because if you imagine someone who leads a 100 developer team
00:34:19.599 the amount of work that 100 developer team is doing is the impact they are making
00:34:25.280 versus if they stayed and continued doing the work of one developer because
00:34:30.480 they wanted to continue writing code even though their leadership potential then the impact they have is up to
00:34:37.679 the amount of code they can do and they can make within their one team out of those hundreds engineers
00:34:44.159 so it's also a perspective thing like what really drives and motivates you it can also be that maybe you want to
00:34:51.280 stay and continue coding that's why i think i spoke about let's not do
00:34:57.200 let's not have tech leaders who are motivated by just the idea that they'll earn more money if they go into the role
00:35:02.960 you really have to be excited about people and supporting them and growing them and being in a leadership space
Explore all talks recorded at EMEA on Rails 2021
+4