What type of engineer are you?

This deck was what I used to deliver the What type of engineer are you session.

Transcript

1. WHAT TYPE OF ENGINEER ARE YOU?
2. E N TE R B O L A JI TH E ME C HA N I C Imagine your car suddenly starts making strange noises and emits smoke from under the hood. You visit a mechanic workshop and meet Bolaji the mechanic. You explain the situation to him and he nods his head in understanding and the following conversation ensue:
3. E N TE R B O L A JI TH E ME C HA N I C Bolaji: What do you want? You: Uhmmm...fix the strange noises and the smoke. Bolaji: I know. But how? Do you want to change the oil, change the water filter, replace the exhaust, replace the engine...what do you want? You: (Very confused) I have no idea. That's why I came to you. Bolaji: Sir, you need to be specific about what you want me to fix. It's your car. You have to tell me what to do about it.
4. E N TER JI MO H THE E N GI N EE R Realising you yourself have no idea what to do about your car, you decide to seek out another mechanic. You drive to another workshop and meet Jimoh the engineer. You explain your dilemma to him and he carefully inspects the engine and its components, and then goes:
5. E N TER JI MO H THE E N GI N EE R Jimoh: Well, it seems your car is experiencing significant engine problems. The very best solution is a new engine which would cost you an average of N800,000, plus workmanship. However, for the immediate issue, I recommend installing a noise cancelling mat/pad. This repair will cost you N50,000 in parts and labor. For an immediate solution if you are in a hurry, you can put this smoke-stop oil each time you change your engine oil. That will be N5000.
6. W HI C H E N GI N E E R D O YO U W A N T TO B E, O R W O RK W I TH ? In today's rapidly evolving tech landscape, it's essential to understand the distinction between being a coder and being a software engineer. The fundamental difference lies in the core focus of each role. Coders primarily emphasize writing code to make things work, focusing on the technical implementation aspect. Coders build what they are told, and make the client do all the hard work. Coders wield the hammer and slam it where they are pointed. Coders primarily work with their hands and churn out tasks after tasks, mark jira tickets as done and move on.
7. W HI C H E N GI N E E R D O YO U W A N T TO B E, O R W O RK W I TH ? On the other hand, engineers approach problems from a broader perspective, aiming to understand the underlying challenges and develop innovative solutions that create value for end-users. Engineers go beyond the code. They take a step back and strive to comprehend the bigger picture, encompassing the business goals, user needs, and long-term scalability. By adopting this holistic mindset, engineers become problem solvers who architect reliable and robust systems. As an engineer, you create solutions, reduce the thinking work, find important edge cases they didn't even think of, and push back when there's issues.
8. THE PA RA B L E O F TH E 3 B RI C K L A YERS I'm laying bricks I'm building a wall I'm building a cathedral According to an interesting article by Swizec: you come upon 3 bricklayers, ask them what they're doing, and get 3 responses. 1. 2. 3. The first bricklayer is the engineer who's a diligent worker, does what they're told, and executes. Picks jira tickets off the board and gets them done few questions asked. They're a great pair of hands, but not a brain.
9. THE PA RA B L E O F TH E 3 B RI C K L A YERS The second bricklayer is that engineer who is lovely to work with. They'll ask just enough questions to keep you honest, help you clarify requirements for a story, and can make a great partner to the right product owner. The third bricklayer is that engineer who companies rush to hire. They focus on user outcomes and will rip requirements to shreds until they find the simplest possible system that gets the job done. Looking 5 steps ahead, this engineer is on an equal footing with the product owner, a true partner. We're building a cathedral, do we really need this wall?
10. C O D E R S They focus on writing code. They just want to complete a task, not minding how it fits into the whole project. Mostly is about ticking off a jira ticket and fixing that bug in production. Is part of the hands in the team and churns out tasks assigned to them. 1. 2. 3. 4.
11. Are problem solvers. They look at the bigger picture. They prioritise quality over speed by employing best practises, investing time in thoughtful design, robust testing, and ensuring,software is maintainable. Take charge and ownership of projects. Are leaders. 1. 2. 3. 4. 5. E N G I N E E R S
12. In essence, software engineering at its core, is problem solving. It just happens that coding is one of the major tools used in problem solving. Hence, by adopting an engineer's mindset, you can transform your role from a mere executor to a valued problem solver. Embrace the challenge of analysing problems, developing innovative solutions, and considering the long-term impact. Strive to become an engineer who not only writes code but also contributes to the growth and success of your organisation, and become an invaluable asset in the ever-evolving world of technology. It starts with a change in your mindset.