Derrick Reimer

I know the notion of quarters is very normative in sales, in the realm of sales. Sales organizations often think in terms of quarters, probably even more so than product development teams. But I wonder, do you have a sense of when does that normally kick in? Is it 20 to 30 team size-ish? Or when do sales teams need to start running on quarters, basically? Yeah.

I know the notion of quarters is very normative in sales, in the realm of sales. Sales organizations often think in terms of quarters, probably even more so than product development teams. But I wonder, do you have a sense of when does that normally kick in? Is it 20 to 30 team size-ish? Or when do sales teams need to start running on quarters, basically? Yeah.

I would venture to guess that, again, speaking a little bit from ignorance here, but that product teams, even when you're a $10, $20, $50 million company, I'm not convinced that a product development team should ever lock themselves into something that rigid.

I would venture to guess that, again, speaking a little bit from ignorance here, but that product teams, even when you're a $10, $20, $50 million company, I'm not convinced that a product development team should ever lock themselves into something that rigid.

Maybe sales, but depending on when you bring in the adult supervision and people who know what they're doing from large company sales orgs, maybe that's the right way. But I would be very leery about ever trying to apply that to kind of a product development cycle.

Maybe sales, but depending on when you bring in the adult supervision and people who know what they're doing from large company sales orgs, maybe that's the right way. But I would be very leery about ever trying to apply that to kind of a product development cycle.

And we were like pushing code every three days. Some kind of version thing applied to SaaS, which is like, why?

And we were like pushing code every three days. Some kind of version thing applied to SaaS, which is like, why?

Okay, a concern in Rails. And this is funny, too, because my Rails knowledge is about five years outdated. So... But I think a concern is basically a mix-in. It's a way to abstract some logic into a separate, my terminology's all messed up because I've been in functional land. It's like a separate, it's not a class. Is it a module? Do you have modules in Ruby? I think it's a module. I love this.

Okay, a concern in Rails. And this is funny, too, because my Rails knowledge is about five years outdated. So... But I think a concern is basically a mix-in. It's a way to abstract some logic into a separate, my terminology's all messed up because I've been in functional land. It's like a separate, it's not a class. Is it a module? Do you have modules in Ruby? I think it's a module. I love this.

Yeah, so it's more like functional paradigms. I haven't written object-oriented code in a while. It was funny, I was doing a podcast episode with Ben Orenstein recently who was also a Ruby Rails expert back in the day.

Yeah, so it's more like functional paradigms. I haven't written object-oriented code in a while. It was funny, I was doing a podcast episode with Ben Orenstein recently who was also a Ruby Rails expert back in the day.

And I was trying to explain how something would work in Ruby land, but I was using all the wrong names for the active record accessors because I was just so used to the naming conventions from Elixir.

And I was trying to explain how something would work in Ruby land, but I was using all the wrong names for the active record accessors because I was just so used to the naming conventions from Elixir.

Totally. Yeah.

Totally. Yeah.

We'll just skip the Rails one. We don't have to do five, let's do a couple. Wait, on the concerns, was I right? What did ChatGPT say? I actually didn't say.

We'll just skip the Rails one. We don't have to do five, let's do a couple. Wait, on the concerns, was I right? What did ChatGPT say? I actually didn't say.

This is actually one of the cool benefits of Elixir because it's built on Erlang, which has all of this very real-time capabilities built into it because it was built by Ericsson back in the day for running text message infrastructure. Think of all of these gazillions of processes that need to be running and they're all in parallel and they don't necessarily need to affect each other.

This is actually one of the cool benefits of Elixir because it's built on Erlang, which has all of this very real-time capabilities built into it because it was built by Ericsson back in the day for running text message infrastructure. Think of all of these gazillions of processes that need to be running and they're all in parallel and they don't necessarily need to affect each other.