A coding class is the least effective way to become more technical
Almost half of all tech company roles are non-technical, yet product managers, sales and customer success teams still sit in meetings where engineers weigh caching, servers and scalability. Full stack engineer and Skiplevel founder Irene Yu, who once tutored an Amazon product manager on questions she was afraid to ask engineers, says learning syntax barely helps. So what does being technical actually require, if not code?
Learn the four technical skills and three ways to build them without taking a coding class
Software engineer and Skiplevel founder Irene Yu argues that being technical and knowing how to code are different skills, and that a coding class is the least effective way for non-engineers to become technical. She lays out four technical skills (awareness of technologies, technical trade-offs, technical communication and the software development lifecycle) and practical ways to build them, including learning breadth before depth, working with a tech mentor and following cloud provider tutorials.
“This is how developers think. And as a non-engineering professional, you also want to be able to think in this way as well.”
“So being able to communicate technically is actually essential to reducing assumptions that may lead to miscommunication.”
What you will learn
Distinguish technical literacy (assessing, acquiring and communicating information about building software) from the ability to code.
Evaluate build options the way developers do, weighing security, maintainability, speed, scalability, fault tolerance and ease of implementation.
Map the six phases of the software development lifecycle to better understand where build time goes and what can go wrong.
Prioritize breadth before depth across core topics such as client and server side, APIs, databases, cloud computing, architecture and deployments.
Use open-ended questions, technical resources and cloud provider tutorials to keep learning from developers without a coding class.
Key takeaways from the speaker
Coding is the least effective way to become more technical.
Being technical is a combination of skills: Awareness of available technologies, Understanding of technical trade-offs, Ability to communicate technically, Understanding of the Software Development Lifecycle
Immediate action items to take to become more technical
Details
Level
Beginner
Format
Talk
Technical depth
Introductory technical
For
Early career, Mid-career, Career changer
Length
41:52
Published
July 2022
Questions this talk answers
Do I need to learn to code to become technical in a non-engineering role?
No. Irene Yu argues coding and being technical are separate skills, and a coding class mostly teaches the syntax of one language, which makes it the least effective route unless you want to become a developer.
What skills make up technical literacy?
Four skills: broad awareness of available technologies, understanding technical trade-offs, communicating with common technical terms and lingo, and understanding the software development lifecycle.
Which topics should non-engineers study first?
Client side and server side, APIs and their components, programming languages and compilation, cloud computing and scaling, architecture such as microservices and monoliths, data structures, SQL and NoSQL databases, the SDLC and deployments including continuous integration.
How can I learn from developers on my team?
Ask for meetings while writing business requirements, bring a technical resource such as a software diagram or API documentation, and ask open-ended questions like what alternative options exist and why certain decisions were made.
How deep should my technical knowledge go?
On a five-level scale of technical depth, aim for levels three and four: broadly understanding what is said, why it matters, what problem it solves and its implications for your product. Level five is where developers are.
About this talk
Having effective technical skills is highly sought after in the tech industry. Most people think being technical means knowing how to code. In reality, coding and being technical are two different things. It's like saying you have to be a basketball player to know what a free throw is! Coding is the least effective way to become more technical.
In this presentation, we'll talk about what it actually means to be technical, the 4 technical skills, what topics to focus on when becoming more technical, and action items to take to immediately become more technical.
Speaker 1: Welcome, everyone, to the second day of the Women's Tech Global Conference and today's talk on technical literacy for non-engineering roles. This is a topic that I am really passionate about, and I spend a lot of my time talking and thinking about. So I'm really excited to share my insights and my tips with you all today.
This talk is going to be perfect for you. If you are interviewing for any role at a tech company that values tech knowledge, so roles like product management, project management, if you're in marketing, if you're in sales, if you're in operations, if you're in customer success, or if you are a non-technical startup founder, or if you have aspirations of being one, it's perfect for you if you work closely with engineering teams. So if you need to communicate with them in any way, collaborate them in.
Speaker 1: And that is just a part of your role. If you write about technology, if you're a technical content writer, and you want to understand technology and software better, this is for you. If you ever have to explain software products from a tech perspective. So for example, if you're in the client facing role, if you're in a customer success role, and you need to be able to speak confidently about the software or help troubleshoot your product. And really just, if you want to feel more confident about your tech skills, because you feel that technology and Speaker 1: Being technical is going to be a big part of your career moving forward, right? And this talk is going to be for you.
Speaker 1: So here's the agenda for today's talk. First, we're going to cover what it means to be technical. So no doubt you've heard the word before used before, and Speaker 1: You will also learn why taking a coding class is the least effective way to become more technical. I'm going to jump into introducing the four technical skills framework for how to think about what it Speaker 1: means to be more technical. And we're going to end with three ways that you can improve your tech skills and your Speaker 1: knowledge, and none of them involves taking a coding class. All right.
Speaker 1: All right. So before we jump into it, here's a little bit about me, I'm just gonna, you know, talk a little bit Speaker 1: about me. So hi, everyone. My name is Irene Yu. I am the founder and the tech mentor at Speaker 1: skipplevel.co. And I help non engineering professionals and companies and teams improve their technology and their tech skills in order to build more confidence in today's tech centric world.
Speaker 1: I'm also a full stack software engineer. I have worked at a very wide array, range of companies Speaker 1: from ad agencies, mid sized startups, large national companies where I was building highly Speaker 1: scalable applications on the front end and on the back end. I want to share with you a little Speaker 1: bit about my story. Throughout my career as a software engineer, I've worked with many, many Speaker 1: non technical product managers. For those of you who are not sure what the PM role is, it is a Speaker 1: role that works very closely with software engineers to plan and to ship software.
Speaker 1: I started tech mentoring a product manager that I worked with at Amazon in 2019. This meant I Speaker 1: was holding bi weekly meetings with her going over technical documentation and answering Speaker 1: questions that she was afraid to ask during engineering meetings. And this was a Speaker 1: really, a really eye opening experience for me. There were many things that I thought were Speaker 1: common knowledge. And for the first time, I realized that they were not actually common Speaker 1: knowledge. And I came to the realization that while engineers have the opportunity every day Speaker 1: to learn technology, that's really not the case for non engineering roles. And in fact, Speaker 1: technical knowledge today is created for developers and it really was not created for the
Speaker 1: non engineering role. So in 2020, I started working full time on skip level where my my my thought is Speaker 1: to make technical skills and knowledge more accessible for everyone and not just that. I'm really Speaker 1: proud to say that since skip level are launched last year, I've helped over 200 non engineering Speaker 1: professionals and teams improve their tech skills and their knowledge, including working with Speaker 1: companies like IBM and Whole Foods and professionals that work at companies like Amazon Speaker 1: and Stripe and Facebook. So with all of my expertise working with and tech.
Speaker 1: I'm sorry. So with all of my expertise working with product managers, Speaker 1: my expertise as a developer, I've put together this talk today to share with you Speaker 1: some of my insights and tips before we dive in some quick housekeeping items before we start. Speaker 1: This is a 35 minute talk about with five minutes of Q&A at the end. So feel free to leave Speaker 1: at any time. But if you stay until the end, I will share with you a special one time offer Speaker 1: for the skip level program that I would love for you to take advantage of.
Speaker 1: You can ask questions at any time in the Q&A box Speaker 1: and please share your thoughts with me throughout the presentation. I really want to hear Speaker 1: your thoughts. Gabe is my team member and he will be on hand to answer any questions. Speaker 1: So, Gabe, you want to just quickly jump on camera, wave to everyone. Just say hi.
Speaker 1: There he is. Hi, Gabe. Speaker 1: Hi, everyone. Speaker 1: Awesome. Thank you so much, Gabe. If there's a question that Gabe cannot answer, Speaker 1: I will go through them at the last five minutes of Q&A. And if we run out of time, Speaker 1: you can always reach me on social media or book a coaching call with me. I'm more than happy to talk to you guys. I love talking to people in the industry. Cool. All right. Now that we have Speaker 1: housekeeping out of the way, let's go ahead and dive right in. So I want to start with what Speaker 1: what does it mean to be technical? In other words, what is technical literacy in the Speaker 1: tech industry? So here's the formal definition. Tech literacy is your ability to
Speaker 1: assess, to acquire, and to communicate information pertaining to the building and the Speaker 1: maintenance of software. So here's a myth about tech literacy. Many people think that coding Speaker 1: and being technical is the same thing. And therefore, many of us try to become more Speaker 1: technical by taking a coding class. In reality, knowing how to code is not the same as Speaker 1: being technical. They are two separate skills. Saying that someone must know how to code Speaker 1: in order to be technical is kind of like saying you have to be a basketball player Speaker 1: in order to know what a free throw is. But you don't need to be a basketball player to Speaker 1: understand how the game of basketball works. Right? And so it's the same concept. You don't
Speaker 1: have to be a developer to understand technology and software and how it works. Speaker 1: So what's the truth? The truth is that taking a coding class is actually the least Speaker 1: effective way to become more technical. Gabe's going to open up a poll and just let me Speaker 1: know if you've taken a coding class before to become more technical and if so, in which Speaker 1: programming language? When you take a coding class, what you're really learning is the syntax Speaker 1: of a specific programming language. Right? So you're learning things like how do I assign a Speaker 1: variable in Python or how do I write a for loop in C++? Right? Taking a coding class Speaker 1: focuses on going really deep into the ins and outs of coding in a specific language, which is
Speaker 1: really not the same thing as knowing how to build an application because so much more goes Speaker 1: into building software than just coding. If your goal is to become a developer, then you will Speaker 1: have to learn how to code. Right? But if your goal is to be technical, then taking a coding Speaker 1: class is going to be the least effective way to achieve that goal.
Speaker 1: So you might be wondering, why is technical literacy important for non-engineering roles in Speaker 1: the first place? After all, since you're not a developer, you don't have a direct role in Speaker 1: building software. Right? So almost half of all tech company roles are actually non-technical Speaker 1: in nature. So non-technical roles include roles like product management, project management, Speaker 1: UX, UI, data, sales, customer success, operations, business development. And while these Speaker 1: non-engineering roles do not build software directly, they all work on software in one way or Speaker 1: another. So these roles either have an important role in the selling of software, Speaker 1: buying software, planning software, designing software, right? That's UX and graphic design, Speaker 1: maintaining of software, working with software teams, or interfacing with software customers.
Speaker 1: Yet despite this fact, 50% of the workforce in the software industry have little to no technical Speaker 1: literacy, and most have never received any training in technical literacy. Speaker 1: And no matter what role you're in, if you work in the software tech Speaker 1: tech space, then having tech skills can only benefit you. It's never going to be a con, Speaker 1: right? It's always going to be a pro. So take the product management role, for example.
Speaker 1: Product and project managers work very closely with dev teams to plan and to build software. Speaker 1: Tech, having more tech skills will help you write better business requirements that help Speaker 1: developers know what to build, and therefore there's less back and forth between dev teams and the product manager. Being more technical also allows product managers to communicate better with Speaker 1: non-engineering teams, which then helps them gain their engineering team's trust, their respect, Speaker 1: and their influence, which is really a very big game changer for product managers.
Speaker 1: The big part of PM's role is also product timeline, right? So having an Speaker 1: understanding of technology and software helps them be able to gauge how long and how much a Speaker 1: feature or product will take to build, right? Along with thinking about the feasibility of a Speaker 1: requirement and what is the scope of work for that requirement that is needed.
Speaker 1: Being more technical is also extremely beneficial for roles in sales and Speaker 1: in any roles where you have to talk to the client, right? For example, being better able to Speaker 1: answer customer questions about a software product, especially if the product itself is Speaker 1: technical in nature, such as a SaaS product or like an API product, right?
Speaker 1: Having technical skills and knowledge also better enables customer success teams to Speaker 1: troubleshoot issues without relying on a dev team. So this saves a lot of time and Speaker 1: frustration for everyone, especially the customer. And then finally, sales and customer Speaker 1: success teams are usually the first to become aware of complaints and customer feature Speaker 1: requests. When you have the right technical knowledge, you're able to better Speaker 1: communicate these customer concerns to product managers and software teams.
Speaker 1: So this is why being more technical benefits non-engineering rules. So let's move on to part two. Speaker 1: Now that we've learned what technical literacy is and why it's important, what other skills are involved in being more technical? We typically think about being more Speaker 1: technical as just one skill, right? In reality, it's actually a combination of four skills that Speaker 1: together make up a person's ability to assess, to acquire and to communicate technical Speaker 1: information. So what are these four skills? The first one is having an awareness, a broad Speaker 1: awareness of available technologies. The second is understanding technical trade-offs. The third Speaker 1: is your ability to communicate using popular technical terms and lingo, which goes for both
Speaker 1: speaking and comprehending technical content. And fourth, having an understanding of the software Speaker 1: development lifecycle. So this is a process of building software. So I'll talk a little bit about these a bit more in depth. The first skill is having a broad understanding, a broad awareness of what sorts of technologies are available out there. In other words, are you aware of the common tools, Speaker 1: the services, the techniques that are used in industry in order to design, to document, to build, to ship and to maintain software? Do you have a fundamental understanding of technology such Speaker 1: that you're able to understand the use cases and the problems that these technologies solve?
This is going to help you in a few areas, but history specifically. First, if you have the skill, Speaker 1: you'll have a general sense, a general sense, kind of like a mental roadmap of what are the capabilities and the limitations of technology? This mental context is really important in order to ask the right questions, well-informed questions, and have a frame of reference during technical discussions. So being able to communicate and to comprehend what is being said during technical Speaker 1: discussions, right? Once you get enough practice in this area, you can then use your mental toolbox to contribute ideas and suggestions during technical discussions on how to solve a problem or build a feature using different technologies. Yes, just because you are not a developer, you can
contribute ideas and suggestions during a technical discussion. It is very much welcomed as long as Speaker 1: you know what you're talking about, right? Here's a quick example of what I mean by having a mental toolbox of tech. So for example, slow browsing and loading speeds for web applications is actually a Speaker 1: very common issue for teams. But there are many techniques and tools that the industry uses to solve latency, right? So slowness. So for example, different forms of things like caching, things like server-side rendering or incremental loading.
Speaker 1: These are all techniques that the industry often uses in order to solve the issue of slow browsing speeds, AKA latency. As someone who is tech savvy, you're able to understand these technologies and know what problems Speaker 1: they solve and how to communicate about them. First, as someone who is not technical, they would not be aware of these different technologies or how to speak about them, and therefore probably have difficulty keeping up during technical, uh, tech talks with dev teams, right? So understanding the fundamental Speaker 1: and how to speak about them, and how to speak about them, and therefore probably have difficulty keeping up during technical, uh, tech talks with dev teams, right? So understanding the fundamentals.
Speaker 1: of technology and the available tools that are out there to solve different problems. That is what it means to have a broad awareness of available technologies. Let's move on to skill number two. Skill number two is having a mental map of what technologies are available to solve what problems. And this helps, um, improve, uh, skill number two is having a mental map of what technologies are available to solve what problems. And this helps, um, improve, uh, skill number two, Speaker 1: which is evaluating technical trade offs. So what are, uh, so are you aware of the common technical trade offs, right? Are you able to evaluate the different strategies for building software based on these trade offs? When we build a product, we can look at it from many different angles, including what are the business goals of this product, right? So that's business. Uh, we can look at it from the perspective of our users. What features do they want? But developers, they look at software from a technical perspective, balancing technical trade offs, and it's
Speaker 1: important to also be aware of this perspective. Uh, here's an example. Uh, let's take this app, for example, right? If you've never used Speaker 1: demo before it is a very popular mobile payment app that allows, uh, people to transfer funds to each other, right? So it, uh, so it includes features like adding and removing friends, sending a payment, transferring balances to, and from your bank.
Speaker 1: Uh, let's say, uh, let's say the dev, um, has a list of these features. They're going to look at these features and they're going to look at the specific recs, right? And they're going to come up with different options for building. Speaker 1: And they're going to evaluate each of these options, these different ways of building based on the technical trade offs to then decide what is the best option to use? What is the best option to build?
Speaker 1: So some examples of the technical trade offs include whether the option is secure. Right? If it's maintainable, this is very important to the long-term health of a software. If it is fast, right? Again, latency. Speaker 1: If it is scalable, right? If your product grows and hopefully it does, um, uh, and having more users, we want to make sure that it's scalable. Is it fault tolerant? When things go wrong? Can we bounce back? And can we bounce back quickly?
Speaker 1: It is easy to implement, right? Because time is very important. So we always want the option that is easiest to implement and many more. Right? So this is what I mean by technical trade offs. This is how developers think. And as a non-engineering professional, you also want to be able to think in this way as well.
Speaker 1: So this is what I mean by technical trade offs. This is how developers think. And as a non-engineering professional, you also want to be able to think in this way as well. Speaker 1: Let's move on to skill number three. Uh, this skill is probably the most obvious, right? So the third technical skill is your ability to communicate technically both speaking ability and comprehension.
Speaker 1: In other words, are you able to speak about a product using today's most common technical terms and lingo, at least the most common terms, um, out there. Are you able to read and comprehend technical content? Speaker 1: So when I say technical content, it can be anything from a software diagram, reading an article to technical documentation to API documentation, um, and to anything that's on the web, right? That's technical content. It's a very broad term.
Speaker 1: I'm going to, uh, um, talk a little bit more about, about this. So being able to communicate technically is actually essential to reducing assumptions that may lead to miscommunication. And this happens very often, uh, with developers and, um, with product managers. Speaker 1: Um, with product managers or designers or customer success who don't have, um, the same technical language, right? A lot of, uh, things are being said. That's kind of being missed.
Speaker 1: I'm going to use the common terminology server as an example of miscommunication. What most people don't realize about the term server is that it's actually a bit of a dual meaning term. So it's meaning changes based on the context. If you're unaware that the term server can refer to many different things, this may lead to miscommunications.
Speaker 1: So let's learn about the term server. The term server can actually refer to either hardware or software, depending on the context. When we are surfing the web, uh, we're actually using our browser to connect to the internet, right? Speaker 1: So whenever you enter a URL into your browser, the browser finds the server that contains the data for the webpage that you want to go to. So this is the physical machine. This is the hardware that is hosting your application.
Speaker 1: When the physical server is found. So this is inside the physical, uh, server, the request is going to hit a software server inside the physical server. Speaker 1: This HTTP server, uh, is a very unique piece of software with special functionality for understanding URLs, storing information about requests coming in, accessing files and returning responses to the browser.
Speaker 1: So the term server can refer to either the hardware or the software, depending on what is the discussion context. Speaker 1: This sort of fundamental understanding about how the internet works and the dual meaning term server really helps give you a fuller context to discussions and prevents miscommunications. Speaker 1: So server is only one example of how, um, having a fuller understanding of technology and software and how it works will help you in communicating.
Speaker 1: Okay. All right. Uh, the final technical skills go number four is that you want to improve, uh, on your knowledge of the software development lifecycle or the SDLC for short. Speaker 1: Right. This is really important. What is the SDLC? Uh, creating software is a very messy and very complicated process. So the tech industry has widely adopted the SDLC in order to give some structure to this very messy process.
Speaker 1: All tech companies and teams use variations of the SDLC in order to build, to design and to ship software products. Speaker 1: So this is what you want to learn. You want to have familiarity with the end to end process of planning, developing and releasing software. Speaker 1: And you want to know the common tools and concepts that are used throughout this process.
Speaker 1: Here's a quick look at the six phases of the software development lifecycle. Um, we go from planning software, right? Speaker 1: So all of my product managers, you guys play a really big role in the planning of software to the technical design. Speaker 1: This is where developers, they take the requirements. They take the features that the product managers want them to build.
Speaker 1: They start thinking about the technical trade-offs and they come up with a technical design. Speaker 1: Then they build it. Once everyone agrees on the technical design, everyone agrees on the requirements. We start building. Speaker 1: Once we build it, we have to test. This is extremely important. We can't miss the step. We test it.
Speaker 1: Then we figure out how to ship the software, which is another really big part in software development. Speaker 1: Hundreds of books written on how do we actually ship software, right? And then documenting, which really should be done throughout all six phases. Speaker 1: But at the end of the software development lifecycle, it's very important that we have our documentation up and, and good.
Speaker 1: Each of these phases involve many tools and processes and is essential to building software. Speaker 1: And it's important for you as someone who is technical to learn about these six phases. Speaker 1: Being familiar with the tools and the concepts you use throughout the SDLC will give you a more intimate understanding of what goes into building software.
Speaker 1: And not only that, but also what could go wrong throughout the process and what to do when it happens and how long each phase takes, which gives you an idea of how long it takes to build software. Speaker 1: Right. So the SDLC is really important product managers that I've helped train. Speaker 1: They, they love the chapter on SDLC. They always say when they learned about what actually goes into software, they're better able to understand time.
Speaker 1: You know, where, where a lot of the time is coming from that those are spending on building software, a lot of things that they didn't realize. Speaker 1: So it's not just the requirement. It's not just the feature. It's a lot of technical back end stuff as well. Speaker 1: So here's a quick recap of the four technical skills that you want to focus on developing broad awareness of available technologies, understanding technical trade offs, your ability to communicate technically and understanding the process of building software with SDLC.
Speaker 1: As you grow. And as you move in your career, you want to take an active approach to improving in these areas instead of focusing on learning how to code. And I'm going to share some tips with you on how to do that coming up. Speaker 1: So here it is. Here are the three practical tips for improving your technical skills and knowledge. The first one is to focus on breath before depth across core software topics. And I'm going to explain what I mean by this. And I'm going to provide you some softer topics to learn.
Speaker 1: The second is to get yourself a tech mentor. I love this tip. I was a tech mentor. That's how I got started. I'm going to talk more about this. And then lastly is to work on tutorials from cloud computing companies instead of taking a coding class. And I'll tell you why this is much more effective.
Speaker 1: So tip number one, focus on breath before death. As you embark on your journey, you want to become more technical. So you want to focus on breath before death. Speaker 1: Focusing on breath before death means learning the fundamentals across core topics in software before diving deep into any of them. So here are some examples. Instead of learning the specific steps.
Speaker 1: Specific steps for setting up a database. Focus first on learning what is a database. What are the different types of databases and what are the pros and the cons of each of them. Speaker 1: Here's another example. Focus. Instead of learning how to code in any specific programming language. Focus first on learning what are programming languages. What are the different types of programming languages that are used on the front end and languages used on the back end.
Speaker 1: And what these different languages are capable of. Right. You don't have to go too deep into the differences in programming languages. It gets really convoluted and not really. Speaker 1: It's not going to be very helpful for your role as a non-engineering person, but you want to be able to know the basics. Right. The fundamentals.
Speaker 1: Here are some topics that you want to focus on instead of learning how to code. These are the core topics in software. The first one is the client side and the server side, which are technical terminologies for the front end. Speaker 1: And the back end. You want to learn about APIs. This is really important because back end developers, they just spend all their time on APIs.
Speaker 1: So understand what are APIs and learn about the different components of an API. This is very important. The components of an API. Speaker 1: Learn broadly about programming languages. As I mentioned, also learn about how the computer actually turns programming languages into a functioning application. Speaker 1: So here's my hint. Read up on compiling, compilation. What is that? Learn about cloud computing and what it means to scale. So I want you to touch on virtualization and technologies, virtualization technologies.
Speaker 1: Learn about architecture and software diagrams. This is so important. Learn about microservices and monoliths. These are the most popular architectural styles. Speaker 1: Usually when you are in a meeting with engineers and they're figuring out, they're talking about different ways of building. They're talking about architecture. They're never going to talk about how do I write a for loop in JavaScript, right? But they're going to talk about architecture. How do we architect this? How long is it going to take?
Speaker 1: Of course, you want to talk about data. You want to learn about data. Learn about the most prevalent data structures. Speaker 1: JSON, strings, booleans, arrays, objects. What are those? Learn about SQL and NoSQL databases. And what is a database schema? What is involved in database schema? Right? Learning about that will also help you learn how to write SQL. Database schemas will help you learn about SQL.
Speaker 1: The SDLC is extremely important as we talked about previously. Also learn about deployments, AKA shipping software. What is continuous integration? Right? Learn about those. These topics broadly will cover most of what you need to know as a non-engineering professional in software and technology. Speaker 1: Right? All right. Tip number two is to get yourself a tech mentor. Tech mentorship is different from what most people think about what you need to know as a non-engineering professional.
Speaker 1: All right. Tip number three is a non-engineering professional. Tip number three is a non-engineering professional. Tip number four is a non-engineering professional. If you're a product or project manager, you can ask for meetings during the phase where you are writing business requirements. I also highly suggest coming prepared to each meeting with a technical resource as a way to facilitate discussion.
This is really important because sometimes when you start a discussion, you don't know where to start. A great way is to bring a technical resource. So, for example, finding software diagrams, asking the dev if they have software diagrams or API documentation or general tech docs, or maybe you were doing your own research and you found these articles online or there's this new service that the team is using and you're reading up on it like data dog or something.
Right. You want to bring that resource as a way to start talking about different topics. Also, the last tip. This is also really important. Please ask open ended questions. This is a great way to improve skill number two in understanding technical trade offs. So asking questions like, what are some alternative options for building the same feature? Why were certain decisions made?
If you ask a developer, if you could rebuild this feature or rebuild this product, what would you do differently? Those are open ended questions. And then based on what they explain and what they say, that's how you kind of learn what are the technical trade offs. The things that are going through a dev's mind and why they make certain decisions.
I wrote a Twitter thread about this, about, you know, different architectural decision and asking a dev about this thing. So I highly suggest you check it out. I also post a lot of other content about product management, tech skills and knowledge and working with dev teams. So please follow me on Twitter. If you have an account, Gabe is going to put up the link to this specific thread.
And from there, you can follow me on Twitter. All right. Let's move on to the last tip for improving your technical literacy. Instead of taking a coding class, work on tutorials offered by cloud computing companies. Cloud computing companies offer lots of really great beginner level tutorials and some more advanced tutorials. But you want to probably start, you know, small to get hands on exposure to many of the areas that we covered in the first step.
These tutorials are meant to be supplementary resource on your technical literacy journey. OK, so you'll still have to look to read up on and learn about the technologies and each tutorial before working on them. Otherwise, you're probably going to be very confused. But these tutorials are a really great way to visualize technical concepts while getting exposure to a wide range of tools and services.
I do have a list of recommended tutorials from different cloud computing companies on the front end, the back end. There's one on the front end, the back end, the infrastructure and databases to sort out with. So feel free to check them out at skip level that code slash resources. There's also a lot of other technical resources on the website.
There are PDF infographics on eight must know terms and three must learn tools on the resources web page. You'll also get my episode on various podcasts where I talk about technology skills and knowledge and product management and technology. So make sure to check out the website. And again, Gabe is going to drop that link in the chat.
All right. Before I jump into the final thoughts and takeaways, please let me know what is your biggest takeaway so far? What have you learned the most that has helped you? Gabe is going to drop the topics that we've covered so far in the chat as a reminder for everyone for what we've covered so far. So please let me know what has helped you the most.
I also write regular content at least once a month about topics like how to work with dev teams and technical topics like Web three. So if you have a medium account, please feel free to follow me at I am I ring you that medium dot com. Again, Gabe is going to drop that link in the chat for everyone.
All right. Here's the final thoughts and takeaways from today's session. If you have taken away anything, first and foremost, with a little bit of time and effort, technical literacy is a skill that everyone and anyone can improve in and develop, even if you're not a developer. Being tech, being more technical will only benefit you in your career.
Right. It's never going to be a con for you. So make an intentional effort to keep your eyes and your ears open to opportunity to improve your tech literacy. Second, remember that your goal is not to remember every technical details. I cannot stress this enough. It is that is not your goal to remember every little detail that is not possible.
Developers don't even do that. It is to get to a place where you feel confident in your ability to learn about technology and software to acquire technology and software and to ask well informed questions. If right now you feel like you're not able to know what questions, what follow up questions to ask, you want to get to a place where you do feel confident in that technology moves so quickly all the time.
There is really no way that you're ever going to remember every little thing or learn every tool. So your goal is to have enough context to be able to ask the right questions to then figure things out for yourself. In other words, when we look at the five levels of technical depth, what you want to aim for is number three and four.
Now, so so if you're at level one where you have no idea what anyone's talking about or to you broadly kind of understand, I want you to work to get to number three and four. At the very least, you should broadly understand what's being said, why it is important, and I would even say what is the problem that this this thing solves and the implications for your product.
Again, super important for product managers. You don't need to be at number five. I don't want you to aim for number five. This is really where the the devs are, the programmers are. It's really, you know, not not needed. But if you if you get there one day, fantastic. All right. Thank you all so much for joining.
That is the talk for today. If you want a recap of today's presentation, all of the links and the skip level offer, just visit skippable.co slash women tech. The link will expire on July 1st, so make sure to visit that soon. If you want to reach out to me directly, you can also find me on social media or you can book a coaching call with me at this link.
Gabe is going to drop this link again in the chat, so please make sure to check it out. All right, it is time for Q and A. I'm going to take a look here. Sorry, I haven't been looking at the chat, but let's see. I'm going to take a look at the poll first. And I'm going to take a look at the Q and A.
Um, so Lauren said. So would it be beneficial to take a? Either a certificate cloud practitioner, or would that be too in depth? Um, I don't know that that would be too in depth. I think that would be okay. Although likely they will go into a lot of details that developers will only need to know. So if you're a non engineer, it might get a little bit too deep.
Um, if you are in a role where you work very closely with, with cloud technologies, then I would say do it, take it. That might not be too in depth because your role is specific to cloud. So you do want to do that. Um, Gargi said, how do you find a tech mentor if you haven't broken into the field?
That is, um, a really good question. Um, so if you know anyone who is a software engineer, um, I would reach out to them. Um, here's the thing about software engineers. They love talking about technology. They love, love talking about technology. Um, they're, you know, software engineers love talking about, about building and what they're working on. So even if you were to reach out to a few people on LinkedIn, um, that maybe you work at a company that you're interested in, seem really nice.
Um, you can totally reach out to them on LinkedIn and let them know, uh, where you are in your career, where you're hoping to get to. Thank them for their time and say, um, looking for a tech mentor. This is what it is. Um, would you, uh, be open to maybe just doing a couple of sessions with me for me to learn more about technology?
Uh, chill. What are some of the best and most effective ways you found to stay up to speed on immersion tech technologies? Yeah, this is, um, a really a good question. I have done a lot of my own research into, um, resources for non engineering professionals and technologies. Unfortunately, I haven't been able to find any good resources.
There are specific newsletters with specific technology. So for example, JavaScript weekly, I know is a newsletter that sends out every, every week about new technologies in JavaScript. I do think that it's a little bit too in depth. I don't know if that's helpful. You can always sign up for it and check it out. I do, uh, do my best with keeping up with new technologies.
Uh, for example, I, I, I wrote a section on like web three. I probably will write one on NFT. And so you can always join my mind and that you can do at skipable.co. You join my newsletter there. Okay. Let's take a look at the chat. Uh, please let me know if you have more questions. You could just drop it into the Q and I, and I can answer that for you.
How are we doing on time? Okay. It looks like we just have three minutes left. So, um, Mercedes, uh, said, I work a lot with servers and APIs. Oh, this thing jumped. Now I lost my place. Uh, yeah, I work a lot with servers and APIs, but do not have a deep understanding of them. I have some more learning to do.
Yeah. Awesome. Mercedes. That is so great. I definitely, um, with APIs, again, learn about the components, what's a get request, post request, the request body, the, the, the, the, um, request body. Uh, yes, just different parts of it. Servers learn about different types of servers. Um, containers are very important as well. If you, uh, so the, the coaching link that Gabe dropped.
So Maria, if you just go to skip level.co, scroll all the way to the end, you'll find a section where you can book a coaching call with me. So skip level.co. Revathi. Oh, I'm so glad that you enjoyed this session. That's awesome. I hope you got a lot from it. Vaji said, what about the program management field?
I assume the same advice. Yeah. Uh, product project and, and program managers. It, those, those three terms, um, depending on the company kind of varies so much, but they're also similar because they work so closely with developers. If you're a project or a program manager, you might have to go even deeper than the product manager. But again, it really depends on the company, but overall it's going to be the same advice.
Janine. I'm so glad this was beneficial for you. That's awesome. Natasha. I am a current graduate student pursuing it. What are good technical skills to be a great project manager? Let's come love the community insights on this. Okay. Um, hopefully my talk was able to give you some, um, thoughts on that. So the four technical skills learned throughout the, the core topics that I covered cloud computing, APIs, et cetera.
Can you please repeat how long the special offer will be? Yeah. It's going to expire on a seven, one July 1st. Eva. Uh, Lauren. That's so strange. I'm so sorry. I didn't realize that cap, uh, cap actually matters, but, um, yeah. So skip over that code slash woman tech, all lowercase. Uh, Gabe, can you make sure to just drop that and let everyone know everything's lowercase.
Uh, Elaine as an engineer, but in a non-development role. I love the other view of tech that was covering this talk. It's not about the details, but working knowledge, a lot of engineers that, um, do focus on one of the other things. Great title today. Awesome. Elaine. So glad. Um, so, so glad that was helpful. Jackie capitalization.
Yeah. So sorry. So glad that was great for you. Thank you for dropping that link. Uh, product management versus product project management. I know that's a big thing. Uh, representing PM tasks for building technical literacy of our team, John, that is awesome. That's a really big thing. We also help teams and companies become more tech learn technology.
So feel free to go to skip level.co and reach out to me if you're interested. Um, there's also skip level.co slash teams just for teams and companies. So we'd love to see you there. Uh, Maria direct zero customer success. This one is brilliant. Thank you so much. So glad that was helpful. Gargi. Yep. Definitely explain technical concepts in simple terms.
This, I would say is something very important to find an attack mentor, someone who, uh, communicates very well and is able to get out of their developer mindset to understand that, you know, not everyone is in that mindset all the time. Uh, Gargi. Uh, Gargi and for ability community. There's a key interview question. Yes. I had a technical interview for a SaaS company.
Yeah. A lot of companies now for product management and different roles are asking more technical knowledge questions. So definitely that helps during interviews. Uh, this is from Jackie with technical abilities. That's a different skill. Understanding what a program does. What's the purpose and goals. Can I understand what it should do? And what is the right? There's a lot more.
Yep. There's a lot more business knowledge and more soft skills required for second self. Absolutely. Man see Google and Microsoft specifically ask if you have a development background. I just gave interview with both. Awesome. Uh, Tracy. Yeah. Check out what Tracy has. She has free learning resources in her posts. That is awesome. Okay. Thank you so much everyone for joining me again.
Please feel free to reach out to me on social media. LinkedIn, um, is I am Irene you Twitter. Same thing. I am I R E N E Y U. You can always reach me on the website, on the website at the skip level website. You can find a coaching call with me. Definitely reach out. Thank you everyone so much for joining me.
Bye everyone.
Transcribed automatically; names checked against the speaker record. Select a time to jump there.
Article based on this talk
Why non-engineers become technical faster without a coding class
Software engineer Irene Yu breaks technical literacy into four learnable skills that product, sales and customer success professionals can build without writing code.
In short
Irene Yu, a full stack software engineer and founder of Skiplevel, argues that being technical and knowing how to code are two different skills. For product managers, project managers, sales, customer success and non-technical founders, a coding class is the least effective way to become technical. What works better is building four specific skills, learning core software topics broadly before deeply, and learning directly from developers.
Key takeaways
Coding is the least effective way to become more technical.
Being technical is a combination of skills: awareness of available technologies, understanding of technical trade-offs, ability to communicate technically, and understanding of the software development lifecycle.
There are immediate action items you can take to become more technical.
Coding and being technical are not the same thing
Irene Yu defines technical literacy as the ability to assess, acquire and communicate information about building and maintaining software. The common myth, she explains, is that being technical means knowing how to code, so people sign up for a coding class. Her comparison: you do not need to be a basketball player to know what a free throw is. A coding class teaches the syntax of one language, such as assigning a variable in Python or writing a for loop in C++, while building software involves far more than code.
She started from her own experience. While working at Amazon in 2019, she held biweekly sessions with a product manager, going through technical documentation and answering questions the PM was afraid to ask in engineering meetings. Things she had assumed were common knowledge turned out not to be, because technical knowledge is mostly created for developers.
Why does this matter? As the speaker cited, almost half of all tech company roles are non-technical, and half of the software workforce has little to no technical literacy. Yet these roles plan, sell, design, maintain and support software every day. Product managers write clearer requirements, earn engineering trust and gauge timelines better. Sales and customer success teams answer product questions, troubleshoot without waiting on developers and pass customer requests to product teams more accurately. As she puts it: "Being tech, being more technical will only benefit you in your career." (31:42)
The four technical skills
Yu breaks technical literacy into four skills.
Broad awareness of available technologies. This is a mental toolbox of the tools, services and techniques used to design, build, ship and maintain software. Her example is latency: knowing that caching, server-side rendering and incremental loading are common answers to slow web apps lets a non-engineer follow the discussion and even contribute ideas.
Understanding technical trade-offs. Business looks at goals and users look at features, but developers weigh options for building each feature: is it secure, maintainable, fast, scalable, fault tolerant and easy to implement? "This is how developers think. And as a non-engineering professional, you also want to be able to think in this way as well." (15:57)
Communicating technically. This covers both speaking with common technical terms and reading technical content, from software diagrams to API documentation. "So being able to communicate technically is actually essential to reducing assumptions that may lead to miscommunication." (17:04) Her example is the word server, which can mean the physical machine hosting an application or the HTTP server software running on it, depending on context.
Understanding the software development lifecycle. Yu walks through six phases: planning, technical design, building, testing, shipping and documenting. Product managers she has trained tell her this is where they finally understand where the time goes when software is built.
Learn breadth before depth, and ask open questions
Yu's first practical tip is to learn the fundamentals across many software topics before going deep on any one. Instead of learning how to set up a database, learn what a database is, the main types and their pros and cons. Her core list covers client side and server side, APIs and their components, programming languages and compilation, cloud computing and virtualization, architecture and software diagrams including microservices and monoliths, common data structures, SQL and NoSQL databases and schemas, the SDLC, and deployments including continuous integration. The reason is practical: "They're never going to talk about how do I write a for loop in JavaScript, right? But they're going to talk about architecture." (24:51)
Her second tip is to find a tech mentor. Much of this section is lost in the recording, but the surviving advice is concrete: product and project managers can ask for meetings while writing business requirements, and should bring a technical resource such as a software diagram, API documentation or an article about a tool the team uses. Then comes the key move: "Please ask open ended questions. This is a great way to improve skill number two in understanding technical trade offs." (28:33) Questions such as what alternative options existed, why certain decisions were made, or what a developer would do differently if rebuilding a feature reveal how engineers reason.
The third tip replaces the coding class with beginner tutorials from cloud computing companies. These give hands-on exposure to many of the core topics, though Yu stresses they are supplementary: read up on each technology first, or the tutorial will confuse more than it teaches.
Aim for confidence, not total recall
Yu closes by setting the goal. "If you have taken away anything, first and foremost, with a little bit of time and effort, technical literacy is a skill that everyone and anyone can improve in and develop, even if you're not a developer." (31:42) Nobody remembers every detail, she notes, not even developers, and technology changes too quickly to try. "So your goal is to have enough context to be able to ask the right questions to then figure things out for yourself." (32:50)
On her five levels of technical depth, non-engineers should aim for levels three and four: broadly understanding what is being said, why it matters, what problem it solves and what it means for the product. Level five is where programmers work, and it is not required.
In the Q&A, she suggests a cloud practitioner certificate may suit people whose roles centre on cloud, recommends reaching out to friendly engineers on LinkedIn to find a mentor, and confirms the same advice applies to program managers, who may need to go even deeper.
Watch the talk
"Technical Literacy for Non-Engineering Roles" by Irene Yu, about 42 minutes: https://www.womentech.net/video/technical-literacy-non-engineering-roles-irene-yu
About the speaker
Irene Yu is CEO & Software Engineer at Skiplevel LLC, a full stack software engineer who has worked with ad agencies, mid-sized startups and large multinational companies, most recently at Amazon building highly scalable, distributed web applications for ad solutions and internal tools. She began teaching and mentoring about technology in 2019 and has helped aspiring and current product managers, directors and startup founders gain confidence and credibility in their technical skills.
Questions this talk answers
Do I need to learn to code to become technical in a non-engineering role?
What skills make up technical literacy?
Which topics should non-engineers study first?
How can I learn from developers on my team?
How deep should my technical knowledge go?
Drafted with AI from the talk transcript. Editor review pending.
Frameworks and ideas mentioned
Four technical skills framework
Software development lifecycle (SDLC)
Breadth before depth
Five levels of technical depth
Resources mentioned
Skiplevel resources page (skiplevel.co/resources) with recommended cloud computing tutorials and infographics
Beginner tutorials from cloud computing companies
Irene Yu's Twitter thread on asking developers about architectural decisions