TL; DR:

• No excuses. No blame.
• Take accountability. Take responsibility.
• Tune into the livestream on Monday, January 27th at 7:00 PM Pacific!

---

Exclusive Article: How To Take Ownership

I wanted to write this article in a slightly different format so that I could share with you some stories. I can't wait to tell you about my most recent screw up that has everything to do with taking ownership -- but first, we'll dive into what this topic is all about.

What Is Ownership And Why You Should Care

Ownership is all about responsibility and accountability. As you're growing in experience as a software engineer, you'll start to hear these words come up more and more frequently.

As more junior developers, we're often working through less complex problems that have a (relatively) understood scope. That's not to say the tasks are easy, but they are often less complex with fewer moving parts in them -- and this way juniors can have a better chance of success.

As engineers work through mid-level and senior roles, the work becomes more complex:

• Partner teams to collaborate with
• Project dependencies
• More unknowns

There are more things that could go wrong, delay, interrupt, or otherwise complicate your ability to deliver on a project -- and this is exactly where ownership comes in.