Menu
Sign In Search Podcasts Charts People & Topics Add Podcast API Pricing

Jesse Spivak

👤 Person
234 total appearances

Appearances Over Time

Podcast Appearances

Ruby Rogues
Exploring Tech Choices and Team Dynamics with Jesse Spivak - RUBY 669

And when that doesn't work, which it almost never does, I have to like get into this like very focused, I'm making this one change verifying state. It's almost like the cartoon Avatar going into your Avatar state, if you guys know that amazing cartoon.

Ruby Rogues
Exploring Tech Choices and Team Dynamics with Jesse Spivak - RUBY 669

And when that doesn't work, which it almost never does, I have to like get into this like very focused, I'm making this one change verifying state. It's almost like the cartoon Avatar going into your Avatar state, if you guys know that amazing cartoon.

Ruby Rogues
Exploring Tech Choices and Team Dynamics with Jesse Spivak - RUBY 669

Avatar and the Last Airbender. I think it came out like 10 years ago, 15.

Ruby Rogues
Exploring Tech Choices and Team Dynamics with Jesse Spivak - RUBY 669

Avatar and the Last Airbender. I think it came out like 10 years ago, 15.

Ruby Rogues
Exploring Tech Choices and Team Dynamics with Jesse Spivak - RUBY 669

He's got an arrow.

Ruby Rogues
Exploring Tech Choices and Team Dynamics with Jesse Spivak - RUBY 669

He's got an arrow.

Ruby Rogues
Exploring Tech Choices and Team Dynamics with Jesse Spivak - RUBY 669

it getting into that really focused state, actually that costs something, right? It takes like a little bit out. You can't maintain that state forever. There's like a mana pool almost of how long you, how long for me I can be in that extreme focused state.

Ruby Rogues
Exploring Tech Choices and Team Dynamics with Jesse Spivak - RUBY 669

it getting into that really focused state, actually that costs something, right? It takes like a little bit out. You can't maintain that state forever. There's like a mana pool almost of how long you, how long for me I can be in that extreme focused state.

Ruby Rogues
Exploring Tech Choices and Team Dynamics with Jesse Spivak - RUBY 669

And I think that when there are times where I look at a problem and I'm like, do it like, I almost like ask myself, do I need to be in this highly focused state to get this thing accomplished? And more often than not, the answer is yes, but my initial answer is no. And so I end up wasting time by not doing things as systematically as they need to get done. Am I alone on this?

Ruby Rogues
Exploring Tech Choices and Team Dynamics with Jesse Spivak - RUBY 669

And I think that when there are times where I look at a problem and I'm like, do it like, I almost like ask myself, do I need to be in this highly focused state to get this thing accomplished? And more often than not, the answer is yes, but my initial answer is no. And so I end up wasting time by not doing things as systematically as they need to get done. Am I alone on this?

Ruby Rogues
Exploring Tech Choices and Team Dynamics with Jesse Spivak - RUBY 669

Nobody else goes into Avatar State when they code?

Ruby Rogues
Exploring Tech Choices and Team Dynamics with Jesse Spivak - RUBY 669

Nobody else goes into Avatar State when they code?

Ruby Rogues
Exploring Tech Choices and Team Dynamics with Jesse Spivak - RUBY 669

Yeah, I love that idea of a naive implementation. And I think the Akka microservice was our naive implementation. We didn't consider the scale at all. We didn't consider the makeup of the team changing.

Ruby Rogues
Exploring Tech Choices and Team Dynamics with Jesse Spivak - RUBY 669

Yeah, I love that idea of a naive implementation. And I think the Akka microservice was our naive implementation. We didn't consider the scale at all. We didn't consider the makeup of the team changing.

Ruby Rogues
Exploring Tech Choices and Team Dynamics with Jesse Spivak - RUBY 669

And as a result, when we went back to fix the naive implementation, when we wanted to get rid of the double loops or whatever, we ended up moving to Java, so from Kotlin to Java and from Akka to Camel. And the reason that those tools made sense is because they were very common in our company. And we didn't have to reinvent the wheel.

Ruby Rogues
Exploring Tech Choices and Team Dynamics with Jesse Spivak - RUBY 669

And as a result, when we went back to fix the naive implementation, when we wanted to get rid of the double loops or whatever, we ended up moving to Java, so from Kotlin to Java and from Akka to Camel. And the reason that those tools made sense is because they were very common in our company. And we didn't have to reinvent the wheel.

Ruby Rogues
Exploring Tech Choices and Team Dynamics with Jesse Spivak - RUBY 669

We weren't seeing errors for the first time in the entire company. It was sort of a knowledge base to draw from. So the current state is that we have Java Camel Spring microservice talking to the Rails monolith. It's very stable. It's performing super well now.

Ruby Rogues
Exploring Tech Choices and Team Dynamics with Jesse Spivak - RUBY 669

We weren't seeing errors for the first time in the entire company. It was sort of a knowledge base to draw from. So the current state is that we have Java Camel Spring microservice talking to the Rails monolith. It's very stable. It's performing super well now.

Ruby Rogues
Exploring Tech Choices and Team Dynamics with Jesse Spivak - RUBY 669

And, yeah, I mean, getting... I guess a question I have is like, how can we speed up the process of getting from our naive solution to the more learned solution?

Ruby Rogues
Exploring Tech Choices and Team Dynamics with Jesse Spivak - RUBY 669

And, yeah, I mean, getting... I guess a question I have is like, how can we speed up the process of getting from our naive solution to the more learned solution?