0:0041:52

Technical Literacy for Non-Engineering Roles

Irene Yu 41:52 2022

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

Watch on YouTube

In short

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.

Topics

Related talks

Browse the library