Think Like A Dev
2 Weeks
·Cohort-based Course
Stop wondering what being a software engineer is like, ditch the imposter syndrome, and learn the skills to think like a developer.
Think Like A Dev
2 Weeks
·Cohort-based Course
Stop wondering what being a software engineer is like, ditch the imposter syndrome, and learn the skills to think like a developer.
Course overview
Most people think they need to learn the right programming language...
But what you really need is to learn how to solve problems with code!
Programming languages come and go, but we'll take a deep-dive into what it means to use code to solve problems, how to structure your code for change, and the best way to approach learning new languages.
Who is this course for
01
You enjoyed HTML and CSS but you feel like JavaScript is just too difficult.
02
You’re stuck in tutorial hell, but you want to be able to build a project of your own.
03
You can program logic, but you don’t understand how or why to structure your functions, files, and apps.
What you’ll get out of this course
You'll write code confidently that solves problems
Lack of confidence in your programming comes when you have an understanding about the language you're programming in but either the problem or the solution isn't clear.
You'll develop the ability to learn new languages
One skill that makes an engineer flexible is the ability to learn new languages quickly. We'll use TypeScript and learn the basics over the duration of this course. But more importantly it'll teach you how to effectively learn new languages in the future.
You'll collaborate with other engineers
One of the key pieces overlooked in learning to program is that you don't often get exposure to working with other software developers. Learning how to be a helpful and constructive member of a team is essential to your job as an engineer.
You'll break down big requirements into small iterative solutions
In software development it's essential to have a vision for a large feature but to write small iterative pieces of code that you can release frequently.
You’ll debug complex problems using a proven framework
Debugging is complex. But by bringing a scientific approach and using The Debug-Experimentation Cycle, you will feel more confident and in control when it comes to tackling tough bugs.
Think Like A Dev
%20(1).jpg&w=1536&q=75)
The main reason for imposter syndrome is a lack of confidence in the skills and abilities you've learned.
Fight it head on knowing you've joined a group of other engineers that have learned the foundational pieces of what it means to be a software engineer.
The main reason for imposter syndrome is a lack of confidence in the skills and abilities you've learned.
Fight it head on knowing you've joined a group of other engineers that have learned the foundational pieces of what it means to be a software engineer.
Meet your instructor
Eddie Hinkle
Engineering Manager @ Glassdoor, Program Advisory Council Member, Mentor, and Podcast Host
More than 15 years ago, I experienced all the same challenges you face today as you work to break into software engineering.
Over the years working in the tech industry I've seen some engineers thrive and I've seen others stumble and fail.
The difference between those who succeed and those who fail all comes down to a mindset. You are building a system rather than writing code.
I love seeing new software engineers thrive, and can't wait to help you break into tech!
What people I've worked with have to say
Dan Cole
Mashell Rodriguez
Kimberly Vandiver
Kaila Kaltrider
Course syllabus
01
What’s In a Language?
As a software engineer you’ll learn a lot of new languages! We’ll use TypeScript in this course because it’s similar to JavaScript but it flexes your muscles to learning a new language.
In this module you’ll learn how to scaffold your own learning for TypeScript in order to learn new languages in the future!
02
Big Problems Need Small Solutions
You’ll always be asked to deliver large projects in short amounts of time. It’s a constant challenge that is being a software engineer.
We’ll discuss how to break big problems into small, iterative solutions. As well as use the Product-Delivery Paradox to communicate with Product and Project Managers about the right trade-offs for any project.
03
The Scientific Method for Debugging
Let’s be real, debugging is hard. And you’ll spend a large chunk of your time debugging. You’ll debug your developer code. You’ll debug your production code. You’ll even end up debugging the code of someone that isn’t at the company anymore!
You’ll learn how to use the Debug-Experimentation Cycle to move from a haphazard approach of debugging.
04
Programming is Collaboration
There are memes of the ninja software engineers who sit in a dark room with a hoodie and kick out amazing code. It’s a myth.
Real engineers are great at collaborating with other engineers. The main way we do this is through pair programming and through pull requests and code reviews.
Course schedule
4-6 hours per week
Tuesdays & Thursdays
12:00pm - 1:30pm EST
Live classes are every Tuesday & Thursday for two weeks.
Timezones:
- 9:00-10:30am PT (GMT-8)
- 12:00-1:30pm ET (GMT-5)
- 5:00-6:30pm GMT
Live Class Dates are: December 6, 8, 13, 15.
Office Hours (Mondays)
9:00pm - 10:00pm ET
Every Monday, I’ll hold office hours later in the day for those where it’s more convenient.
Timezones:
- 6:00-7:00pm PT (GMT-8)
- 9:00-10:00pm ET (GMT-5)
- 2:00-3:00am GMT
Office Hours (Wednesdays)
12:00pm - 1:30pm EST
I’ll have office hours every Wednesday, the same time as our Tuesday/Thursday class.
Timezones:
- 9:00-10:30am PT (GMT-8)
- 12:00-1:30pm ET (GMT-5)
- 5:00-6:30pm GMT
Specific questions, ask anytime.
Always available for questions and support through the online community.
Pair Programming
Part of this live course is the ability to work together. Each week you’ll want to pair program with each other for 40 minutes. You’ll want to record this session so I can give you each private feedback on how you can improve.
Not ready yet?
Sign up to be the first to know about course updates including future cohorts.
Learning is better in community
Learn with a cohort of peers
We don't work on our own or in groups of hundreds. The size and structure of this course is intentionally built to mimic working with co-workers on the job.
Experience being an engineer
There is a difference between learning and experiencing. Watching some videos will allow you to learn code. This course is designed to help you experience being an engineer.
Build your portfolio
One of the keys to getting a job in tech is a portfolio. This course will result in you having a collaborative project that you can share as part of your portfolio.