Jaana Dogan Avatar

Jaana Dogan

San Francisco, CA · Twitter · GitHub · Website

Jaana Dogan Medium

What did I forget by working for the same company?

Jaana Dogan, now working at AWS, reflects on her (long) time at Google:

My time was up for one exact reason. I no longer had no clue what the life outside Google felt like. My actual superpower was gone. I remember sitting in meetings only bringing insights from what I hear from customers without truly understanding how things worked outside of our bubble end-to-end.

Thoughtful reflection is a powerful tool in your life. Sharing that reflection with others, like Jaana does here, can be a powerful tool in other people’s lives. 💪

Go Time Go Time #146

Hits of the Summer

This episode is different than what you’re used to. We’ve been clipping highlights of the show for awhile now to share on Twitter and YouTube. A side effect of that effort is a bunch of awesome clips just sitting on Jerod’s hard drive collecting digital dust. So, here’s a beta test of a “best of” style clips show covering the summer months. Let us know if you like it!

Go Time Go Time #132

The trouble with databases

Databases are tricky, especially at scale. In this episode Mat, Jaana, and Jon discuss different types of databases, the pros and cons of each, along with the many ways developers can have issues with databases. They also explore questions like, “Why are serial IDs problematic?” and “What alternatives are there if we aren’t using serial IDs?” while at it.

Go Time Go Time #127

WebRTC in Go

The gang discusses WebRTC with Sean DuBois, creator of the Pion project and author of a pure Go WebRTC implementation. What exactly is WebRTC? Why is it so popular for video chatting? How does it work under the hood, and how does it compare with other real-time communication options?

Jaana Dogan Medium

Things I wished more developers knew about databases

Jaana Dogan started with a draft and this tweet and ended up laying down some serious knowledge on databases.

A large majority of computer systems have some state and are likely to depend on a storage system. My knowledge on databases accumulated over time, but along the way our design mistakes caused data loss and outages. In data-heavy systems, databases are at the core of system design goals and tradeoffs. Even though it is impossible to ignore how databases work, the problems that application developers foresee and experience will often be just the tip of the iceberg.

Go Time Go Time

It is Go Time!

This is THE podcast for diverse discussions from around the Go community.

Go Time’s panel hosts special guests like Kelsey Hightower… (clip from episode #114)

picks the brains of the Go team at Google… (clip from episode #100)

shares their expertise from years in the industry (clip from episode #102)

and has an absolute laugh riot along the way… (clip from episode #110)

It is Go Time! Please listen to a recent episode that interests you and subscribe today. We’d love to have you with us.

Go Time Go Time #113

Go at Cloudflare

Jaana, Jon, and Mat are joined by John Graham-Cumming, the CTO of Cloudflare, to discuss Go at Cloudflare along with John’s unique involvement in Gordon Brown’s apology to Alan Turing. How did Cloudflare get started with Go? What problems do they use Go for and when to they turn to other languages? And how exactly did John’s petition for an apology to Turing get so popular?

Go Time Go Time #108

Graph databases

Mat, Johnny, and Jaana are joined by Francesc Campoy to talk about Graph databases. We ask all the important questions — What are graph databases (and why do we need them)? What advantages do they have over relational databases? Are graph databases better at answering questions you didn’t anticipate? How is data structured? How do queries work? What problems are they good at solving? What problems are they not suitable for? And…since we had Francesc on the hot seat, we asked him about Just for Func and when it’s coming back.

Jaana Dogan jbd.dev

Production readiness

Have you ever launched a new service to production? Have you ever been maintaining a production service? If you answer “yes” to one of these questions, have you been guided during the process? What’s good or bad to do in production? And how do you transfer knowledge when new team members want to release production services or take the ownership of existing services?

0:00 / 0:00