The One Question bounty closes Thursday 10 December.

Join in
We Them Media logo We Them Media Support us

Pathway to Continuous Growth as a Developer || Mayowa Tudonu || Alumni Retreat

The picture loads from YouTube. The player loads only when you press Play. Turn on captions in the player if you need them.

Mayowa Tudonu, a solutions architect, tells Web3Bridge alumni that growth as a developer rests on productivity, prioritization and proactiveness. He recommends deep focus on one skill, using AI as an amplifier, and removing distractions directly. He explains sorting tasks by urgency and importance with examples, and says telling a manager early what will slip brings peace of mind.

Not by We Them Media Channel: Web3Bridge. Published Friday 31 October 2025.

A session from the sixth-anniversary Alumni Retreat on building a sustainable developer career through consistency, curiosity and collaboration.

Titles are the owner’s. It plays from their channel.

Transcript

This transcript may contain errors. This video belongs to Web3Bridge. Letters mark each change of speaker.

These are the speakers’ own words. We have not checked their claims.

0:10 A: So today I'm talking about pathway to continuous growth as a developer. Um, this is a very interesting topic in the sense that, um, it highlights the fact that the developer growth is a journey, right? There is no end to developer growth. I mean, ideally, even your growth as a human is a journey. You know, you don't stop growing even when you're older. You still continue to grow. You learn new ideas, you learn new concepts, new ways of talking to people, new ways of interacting. And as a developer in this space, or even as not a developer, you are, you know, doing other things, you are the manager, you are in the finance space, you are in any other space at all, you know, there is a path to continuous growth that you have to take, and there are several what I'll call yardsticks and pointers along those paths. But for today, I'll focus on just 3 core areas, you know, that can help you on your path to continuous growth as a developer. And even if you're not a developer, I've introduced myself, you know, earlier as a Solutions Architect. My core area is solution architecture, designing solution architecture, working on, um, solution engineering as well as, uh, um, solutions operations. Um, yeah. And to keep growing continuously as, as, as a developer, there are, in my opinion, 3 things that matter, right? Productivity, prioritization, and proactiveness. I know this sounds like, uh, what do you call it? Sounds like, you know, soundbites. Yeah, it sounds very nice to say productivity, prioritization, and proactiveness. And I intentionally picked this style of presentation for this particular talk because I'd rather go through like a lengthy talk of what you could do. I think having soundbites handy sometimes can be very useful. If you are productive, if you can prioritize, and if you are proactive, you can go very, very far in your career. So don't think of them as soundbites. Think of them as things that you need to have at the back of your minds every single time, right? So I'll talk about the first pillar, which is productivity. Productivity, as I mentioned here, is not about doing more work, right? Productivity is about doing meaningful work efficiently. Doing meaningful work efficiently. It's very easy to get distracted in the workplace. Or even your personal projects, or while working in, while collaborating with others, it's very easy to get distracted with very interesting things, but those things are not meaningful in the context of the work that you are doing. So as an example, as an engineer, it's very interesting to want to try out a new technology in CK, for example, right? Meanwhile, you can simply use, you know, any other simple cryptographic primitives out there to solve a very simple problem and keep it moving. But you want to explore, you know, the very complicated, the very new technologies. That is doing- you are being productive, yes, because you are researching, you are reading, you are probably writing code as well. But is it meaningful, right? Is it really relevant in the grand scheme of things? Will people use the product? Will your product team appreciate what you're building? If you're working, if you're not working, if you're not a developer, it's important to be productive, but it's important to be productive in a very meaningful way, right? You just don't get productive for the sake of being productive. And when it comes to productivity, there are 3 key things that you should pay attention to. One of them is skill, the other is clarity, and the other one is focus. Um, skill, I don't think I need to you know, um, talk so much about skill. You just need to know what you're doing. It's, it's so important, right? Competence is not something that you can play around with. It's not a, a value that you should, you know, play around with. Um, I think very recently, uh, a fresh graduate from OU- by the way, I'm an OU alumna, very proud one at that- So the fresh graduate from OU reached out to me. He said, oh, he's done now and he wants to go into the blockchain space. What should he learn? What should he do? I asked him if he had a job. He said no. I said, fine. I first recommended him to Web3 Bridge because I know you guys do very good work. But I went ahead to tell him some things. I said, look, this is not the time to focus on trying to get some, you know, weird developer job where you're doing some weird thing and you're making, you know, little bucks. I'm not saying you should not make money. I'm saying if I were you, I would spend the next 6 months to 1 year focusing on learning just 1 skill, right? I told him Rust is there, you can learn it. Solidity is there, you can learn it. These programming languages are very- they are applicable in a lot of blockchains, you know, across the ecosystem. Spend time, learn them. Don't pick on any job, don't take any side gig because you can use AI to do it. Don't do any of those things, right? Don't do that. Just focus, learn. And I said that because I understand the importance of having depth in a particular skill. Like, it's so important. It's so important that depth in a particular skill is transferable to depth in other skills. Go and check people who know a particular topic very deeply are able to easily transfer that skill to every other areas of their life, right? So if they pay a lot of attention to learning a programming language, to learning a financial concept, they extend the same attention to other areas in their life. So it's so important to know your skill. But beyond that, you should leverage the tools of today, right? Use AI as an amplifier. Use AI to amplify your skills. Use AI to be more productive, right? Now you can code. Now you understand how unit tests work. Now you know about design patterns. Now you know about all those programming concepts. That's absolutely fine. Next thing is, how do I become more productive, right? So it's not to try to use AI to be productive before you know them. No, know them first, then be productive, right? Know those concepts, read them, read those books, read those articles, practice, practice, practice. You know, but then be productive. Use AI to be productive. You want to write a simple Node.js server, of course you know how to set it up, but before you pull all the items together, 1 hour is gone. You can just, you know, ask Claude to do it for you. You can ask GitHub Copilot, set up a Node.js server for me. It does that, you know, you move forward within 10 minutes, you are done. You've saved 50 minutes more time to do something else. Clarity is another thing that is important. for productivity. You need to be clear on what you want to do, right? Whether it's personally, whether it's, you know, at your job, you know, or at some, um, some gig with, you know, some clients, whatever it is. But you need to learn the importance of clarity, right? What is expected of me? What do you want as a user? This, this little thing has caused problem. in several places, right? At work, it causes problem. In relationships, it causes problem. In personal business, it causes problem. People tell you, I want this, I want A, you bring B, right? Don't assume what the user wants, ask them. Don't assume what your colleagues want from you, ask them. Don't assume what your manager wants, ask them. How do you want me to be productive? What do you want me to do? These are the things that will get you promoted. These are the things that will get you you know, new users. If you are building a product, you need to be clear on what your users want. You're speaking to users to introduce your products to them, and you're telling the user, oh, it would help you sort your bills in your business. And the users are telling you that- they're not telling you no directly, but they're telling you that most important or their most- the biggest problem in their business is not sorting their bill. but it's actually, you know, paying the bill on time. So these are 2 different problems that are related in the sense that it involves bills, but you are not solving that. You're not solving their problem. You're solving your own problem or your own perceived problem. So clarity is very important in productivity, and it's, as I said, it's applicable to many areas. You just need to be clear on what people want. Someone is telling you how you're making them feel, you know, how you're not responding to them in the way they want. Clarity. Ask them, you know, and clarity comes from asking questions. Ask to understand. It's, it's very important. The final one is focus. It's very easy to get distracted in this world. I swear, it's very easy. It's very, very easy to get distracted. It's very, very easy, and everybody gets- so this is not a, you know, I'm not coming here trying to act like, you know, I don't- I get distracted very, very well. As a matter of fact, my role itself is distracting because in a single day I'm writing code, right? I'm responding to my colleagues, my manager, other managers. I'm responding to users. I'm responding to, you know, questions from other places. And then I am filing tickets. I'm following up with tickets. Like, I'm doing different things in a particular day, right? And I'm still thinking in my head that there is Champions League match in the evening and I want to- what is the latest? Who are we dragging to? Like, this is easy to get distracted, but it's also important to know how to focus. Okay, there are different techniques to get focused. All these techniques are very nice, you know, Pomodoro, Deep Work. But you know what I'll say? I'll say ignore these theories, right? If you need time to focus, remove the- you know, the distraction. Let's not act like we don't know what's distracting us. Let's not act like we need some kind of, you know, Um, yeah, what's it called, some special technique somewhere, you know, to 25 minutes. You know, you know that your phone is distracting you, turn the phone off, go and keep it in another room. You know that TikTok is distracting you, log out. You know Twitter is distracting you, log out. You know, whatever is distracting, just get it off. You know what is distracting you, it's your TV, sell it. Well, don't sell it, but you know. Well, you know what I'm trying to say, you know, turn off the TV, right? Maybe don't sit down in your sitting room. Maybe, you know, if you have a TV in your sitting room, you have a TV in your living room, you know, maybe use one, you know. But point is, you know what is distracting you, remove it. Okay, the second pillar is prioritization. This is important, uh, for growth as a developer. You need to know how to prioritize. Prioritization is one of the biggest indicators of growth as an individual. Yes, I'll say it again, prioritization is one of the biggest indicators of growth as an individual. If I'm interacting with someone and I feel like they don't know how to prioritize their time, I just see them as persons already, right? And that is not a way to dismiss them or discredit them. It's a way to say, I am not going to be helping you manage your time. or manage your, you know, your responsibilities, you need to know how to prioritize, right? What do I need to do first? Now, the interesting part is that there can be multiple competing priorities. That is the most interesting part. Now, when there are multiple competing priorities, what do you do? So there is this, this theory called, or this method called the Eisenhower Matrix. Now, this is a theory that I think is in important. I learned it, I learned about it about 4 years ago when I was working on some company. The manager came in and was trying, you know, trying to like sort us out, and he taught us about Eisenhower Matrix. And since then, I've always applied it. So it's a theory that I think is important. In terms of focus, Pomodoro and co., I think those theories are just trying to highlight to you what you should know. But this is a theory that I think you should at least defer to as an individual when you are growing. It's just so important if you are going to be working in places where there is demand for your attention, like you need to, you need to be locked in at work, this particular tool or model is something that you need to pay attention to. If you are working on multiple projects, you are somebody who is working on, you know, multiple businesses, people like that who love multiple businesses because it gets them going. One business is boring, 3 businesses, that's where they, you know, they perform optimally. You need this particular theory. So It's a theory that says that there is a matrix of 4 boxes and each box has a label and each box tells you what to do, you know, when a task falls into the box. So what you need to do is pick up a task, identify which box the task goes into, which box that goes into, and then decide on what to do. So the boxes are urgent and important, urgent not important, Excuse me. Important, not urgent. Neither urgent nor important. When an item is urgent and important, do it now. When an item is urgent but not important, delegate it. Okay, that is exactly what managers do. The user reaches out to them, this needs to happen, that needs to happen, it's urgent, but to them it's not important. They delegate, they give it to someone on the team to handle. Good. Um, when an item is important, not urgent, what do you do? You plan it. So it's important that you go on a date, you know, with your partner. It's important that you eat. It's important that you sleep. It's important that you do a number of things. But are those things urgent? No. So you plan it, right? You plan for those things. Long-term goals, skill development, system improvements, documentation, You plan for them. When it is neither urgent nor important, you remove it. Just, you know, just shelve it, keep it aside, right? There are things that are neither urgent nor important. You know them. Examples of urgent and important tasks, crucial tasks, you know, production issues, critical bugs, deadlines for deliverables, presentation. Those things are, for example, this particular presentation is important, but but it wasn't urgent. As at the time I was told I was speaking, it wasn't urgent, but it's important, right? So what did I do? I planned for it. I communicated with, you know, Ayo, told him, okay, I'll send you the slides. So I planned, I put down the dates on my calendar. When I could not meet up, I told him I can't meet up, you know, I'll, you know, reach out to you over the weekend. Saturday morning when I woke up, what did I do? I picked up my computer. I knew I was supposed to do this. I looked for an AI tool that could help me. Productivity, right? I don't have the time to sit down and start designing Google Slides anymore. I looked for a tool called Gamma. I put in- I've written down everything. So immediately I told him I was going to plan for it, I started thinking of what I'll talk about. I put them in my notes. I put down all the- everything I wanted to say. I put everything down. I used the AI to generate all these things for me. This is what I want to see. I edited it. That is productivity. That's just it. And I leverage productivity with AI. Within 3 hours, I was done with the entire thing, you know. I shared it with him, that's all, right? But the point is that I planned, I prioritized it during the week. When he told me about it, I was busy with work. I don't have time for it, right? But it's important, so I planned it. So that's how you should, you know, prioritize things. It's just so important. You cannot continue to, you know, drop the ball because you're not prioritized. No. There is a way to handle multiple priorities, right? And this applies to everybody, developer or not. The PM comes to you, this is a feature we need to build. Another PM comes, this is a feature we need to build. Ask yourself, of these 2, which one is the most important? That's the first question. Which one is important? Okay, A is important. Which one is urgent? A is urgent. Okay, I go with A because it's urgent and important. Right? Which one is not important? If it's not important, but is it urgent that it needs to be done? Yeah, it needs to be done. For example, responding to a user is, you know, is urgent and important. It depends on the situation, right? But responding to a user for maybe users asking you for a new feature, when is a new feature going to be available? That task is important, but it is not urgent. important that you respond to the user because you want to be responsive, but it's not urgent. You can respond to them tomorrow. So what do you do? You can either delegate it, you know, or you can plan for it in the future, right? So that's just it. So, um, yeah, that is just what Eisenhower Matrix is about. It's important to know how to prioritize. Um, I have a, you know, a real-world scenario here where it says that, you know, you're working in the product team and a PM comes and says, can you fix this UI follow-up work before tomorrow's demo, you know, and, uh, at the same time your Node services is going down, right? How, how would you, how would you handle this? If I may ask, which is more important and why? Which is more important? I want to see the chats. Which is more important and why? Please put it in the chat. Which is important? Which is urgent? You know, which, which, how would you tell them? Maybe I should go back to the question. So there are 2 things here. There's a demo tomorrow. There's a UI bug. Right now there is a- right, nodes are failing. They're not receiving, receiving requests, or they're not processing requests. How would you- yeah, I know you want to get the nodes up running. I know the node service. I want to know which, like, how are you thinking about it? Which one is- are you thinking of which of them, in which box do they fall in, right? Yes. Yeah. Okay, good. Thank you very much. I like David's answer. He says server is going down, it's important, and it is urgent. Yes, Node service is urgent and important. You cannot play with that. Thank you very much. Which box do we put the second one, the UI bug? Which box do we put it in? Let me go back to the boxes. Which box do we put it in? Are we putting it in importance, not urgent? Urgent, not importance? Which one do we put it in? Urgent, not important. Because it is important. I shouldn't have said that. Sorry about that. Exactly. Yeah, thank you very much. It is important, it is not urgent. Yeah, it's not urgent to enlarge your estate. It's not urgent. So what do you do when it's not urgent and important? You plan it. So you just keep it aside. Maybe when you close at work at night, you can look at it or delegate it to somebody else. What if there's no one to delegate to? What do you do if there's no one to delegate to? What do you do? I want to see in the chat. What if there is nobody? You are the only developer, you are the only alpha and omega of that company. Now only you, they write that code. You're the only one that is doing it. You don't have time. Let's say you don't have time. Let's say you don't have time for it. I say you are the only developer. Say you're the only person, you're the alpha and omega of that stuff. AI, you still have to spend time with AI now. I mean, you say AI can delete your entire codebase, so before you know it, the demo has been deleted. I don't have anything to present. So what do you do? Yeah, now since we don't know, let's continue. Let's continue. Okay, so what do you do? You be proactive. Yeah, you have to be proactive. Okay, yeah, this is, this is the final, this is the final piece of the puzzle that's, you know, that this is another piece that solves the entire puzzle. What if there are multiple competing priorities? What if there is something that's important, it's not urgent, but I'm the only one who can do it? Yeah, it's called a key man risk where you as an individual are a risk to the company because a lot of things, you know, happen around you, right? Key man risk is everywhere, to be honest. CEOs of companies are key man risk. There is a very, there's a very popular example of a key man risk. When he tweets, the stock go down. When he tweets, the stock can go up. He can tweet, they can burn his car company. He can tweet and he can- everybody knows that person. Let's not talk about him right now. Someone said give up. Don't give up. So be proactive, right? And I wrote this quote myself. I said, proactiveness will set you apart in a world of nonchalant developers. See, it is very easy to be nonchalant. I promise you, it is one of the easiest things to do. What does nonchalance mean? You just don't care. It's very easy to not care. As a matter of fact, Nigeria built us to not care, right? How? As a Nigerian, you can buy the most expensive car and drive it on a bad road because you just don't care, right? We just don't care enough. The people who are meant to do things will not do it just because They don't care, you understand? And this- it is- I would say that it is not a fault of, you know, those of us who are like- we were raised in the country because we met the culture there. And it's very hard for such a culture to not permeate your own, you know, personal values, right? We are a product of our environment. And when you realize that you are a Nigerian, a product of the environment, One thing you must always tell yourself is that I am not going to, you know, begin to display the characteristics of where I come from, especially the bad ones, right? Nonchalance is a very- like, it's, it's, it's even in hospitals, okay? In healthcare, it happens there. In payment systems, it happens there. In education, it happens there. It happens everywhere. A lot of people just don't care. But proactiveness is what solves nonchalance. What does proactiveness mean? It means doing things before you are told, right? It means anticipating needs, right, and responding to problems before they even arrive. Now I go back to what I said earlier on where I said, what if you are the only person who can- who is the one who wrote the demo? They are solving load problems. How do you, you know, deal with this request from the PM when you don't even have the time? Because you don't even know if- yes, you could plan it. Yes, we can plan it because it is urgent and because it is important. Not urgent, we can plan it. Fantastic. But the question is, will you ever get to it? Will you ever get to it? You may never get to it. That is just the truth about it. What do you do when you know you can't get to it? You proactively communicate, right? You proactively communicate. I put it here, proactive communication. You tell the PM, I am going to plan for this, right? I can't do this right now because there is a high priority task of solving this. I don't know when this task will be done. I don't know if it is going to be done before the demo tomorrow, but I'm going to plan for it. Now what you've done is you've informed the PM That first and foremost, you have something important they are doing. That thing could take plenty of time. 3, you may never ever get to that particular bug she's talking about, and there is a high chance- sorry, sorry, they are talking about- and there is a high chance that when you guys get to the demo tomorrow, you may be going with that bug. So that will inform the PM that they should go and figure out how to handle that particular bug when it comes up in the demo, because it is important. You see how proactive communication or being proactive resolves all these things. It helps you to look- I, I think it's, if I, amongst all the 3 pillars, in my opinion, it's one of the most peace of mind giving kind of thing that you can do. I promise you, one of the most peace of mind giving kind of thing that you can do when something comes on your table and you say I can't promise you I'll get this done in 3 weeks' time, but I'll try. And the reason is that I have this understanding that you've taken a lot of pressure off your chest. So when people say things like they're under pressure and all whatnot- by the way, pressure is real. I've experienced pressure, okay? But there's also a way to manage pressure. There's a way to manage it, and the way to manage it is proactive communication, you know, and proactiveness. You need to know to be proactive, right? For you to be proactive, you need to anticipate, anticipate that something bad will happen, right? As developers, we do this a lot when you use try-catch in your code. Try-catch is a very, very good example of anticipating that the API you are going to make a request to or the function you're going to call is going to fail. Yes, you are not assuming that everything is going to be fine. You anticipate that it's going to fail, so you prepare for it. If it fails, what do I do? You know, I do these next things, you understand? Because a lot of things are not within your control. That is why you need to be proactive. You know, proactive- when, you know, we grew up hearing Plan A, Plan B, Plan C, all those things is proactiveness. You know, people plan like that. They have 3 plans, 4 plans, just in case one doesn't work, they switch to the next. It's just important to be proactive. Right, to not be nonchalant, you know, not be part of that group that people are saying they're writing code. What if something happens? Like, oh, when it comes, we'll deal with it. It's fine to do that, right? But what if it happens? Okay, so another one is, you know, um, I mean, an example of being proactive is to write documentation before someone asks for it, right? This, for example, is something that I'm suffering from. I worked on something before, you know, I didn't document it because nobody needed it at that time when we worked on it. Now someone needs it. I'm currently the only person in my, like, my smaller team who is, you know, around. Now someone needs documentation. I have other priorities. I'm having to manage all the stakeholders. Okay, so, you know, improvement is also a way to be proactive, right? You anticipate, you document things. These are just examples of ways of being proactive. Improvements, trying to improve on things, okay? Try to improve on things. Don't just look at- think ahead, think ahead. This, the way we're doing this thing, is it good? How I'm teaching this course, is it good? How I'm explaining this thing, is it good? You know, you think through what you're doing. It's just so important, helps a lot. I mentioned earlier on, you know, error handling in development is being proactive, right? You know, A developer that is not proactive is going to be reactive, right? You want to deploy a contract, you just, you don't put any, no checks, no try-catch, nothing. You just write the code, it just runs, right? And then it fails and then you start throwing up and down. It just doesn't work, right? Proactive developers build resilient systems. When you're proactive, it helps to build resilient systems. You can think ahead of things that could fail, right? Things that could go wrong. wrong? What if, what if these things go- what, what if this thing goes wrong, right? What if something happens? What if, what if, what if? You know, you plan ahead. Even an example of being proactive is, you know, arriving early for an event, right? You know that, yes, it's a 30-minute drive away, but what if something happens? What if there's traffic? What if my car breaks down? What if- you plan for all those things. Of course, you cannot, you know, plan 100% for things, but when you are proactive, every single time you will be able to manage things properly, right? And when things don't go your way, you must be able to manage it properly. So this growth framework, in my opinion, for you to continue to grow as a developer, as an individual, you know, working in finance, working in business, working in operations, working in, you know, customer side of things, you just need to be proactive, you know, learn to prioritize. I'm sorry, you need to be productive, you need to learn to prioritize, you know, you need to remain proactive. It's These skills are just so important. If you can master these things, you are productive. You know what to do. You can write code properly. You can use the tools at your disposal. You can prioritize. You know what is urgent and important. You know what is important, not urgent. You know what is not important, not urgent. Somebody tells you- you are working on something, someone tells you that there is some event happening somewhere that does not concern you, is not important, is not urgent, don't even involve yourself. As a matter of fact, There are things that are happening within your company. It's not important. So you- because you get distracted by them, what happens? You are not focused and you don't become productive, right? And being proactive, right? This is just important. This is- being proactive is, in my opinion, you know, senior-level skill, CEO-level skill. This being proactive is- see, if you can master it very well, you can do many, many things. Managing, you know, conversations, managing stakeholders is all about proactivity. Because at the end of it all, the people who would do the work are the people under you, right? Just need to be proactive. Think about it. What is this person doing? What's that person doing? What if they don't know it? What would be my response? How would I manage the CEO? What should I tell the CEO? Like, it's just so important to, you know, to be proactive, right? To be- to know how to communicate properly. You, I mean, some people might have mastered these skills and it's fine. And people are still learning. Myself, I'm still learning, right? Learning how to use skills, how to be productive, how to prioritize. I'm learning from my mistakes, listening to feedback from my manager, listening to feedback from other people, you know. But it's just important to have it in mind that you need to be productive, you need to prioritize, and you need to stay proactive. So I'll finish with this very nice quote. It says, your skill gets you into the room. Yes, when you're doing an interview, your skills is what would, you know, get you into, you know, that room, right? But when you need- when there's- it's not only interview, even when there's a big project at work, you know, and you want to be part of that project. For example, your team wants to ship a feature that will change, you know, the way things are done in finance. For example, let's say you're working at one of the fintech companies I really admire is OPay. You know, I like what they do. I like, I like, I like, I like the product itself, just the truth, you know. And they have a new product for, you know, teenagers and all whatnot. Let's assume that that's going to be a big product. You want to be part of it, you need to be skillful to be part of it, right? But when they get you into it, what keeps you there? Because they can kick you out. The managers of the project can kick you out, right? You need to be productive to stay in the game. You need to be productive, you know, you need to get shit done. You know, how will they always call you back, say, I enjoyed working with Samson, I enjoyed working with David, I enjoyed working with Mayowa, I want to work on- I want to work with him again? It's with proactive. Yeah, proactive. When they don't have to, you know, always quench fires because of what you've done, you know, I always just there stepping in next one, you know, just so, so easy, right? So I think if you do this, it's going to be very helpful. It's very important.

More from this hub

Something wrong, or a video you want off this page? Write to wethem.xyz@gmail.com and it is fixed or taken down within 48 hours.