Derrick Reimer
speaker
327 appearances
2 recordings
1 series
first heard Sep 2024
last heard 15 Sep
Derrick Reimer’s voice in public audio — every appearance, attributed to the second.
Trend
recordings per month · last 12 monthsRecordings per month over the last 12 months — 1 in all, peaking in Sep 2026 with 1.
Appearances
wanting to integrate our two products together. Here's what we're seeing. Are you guys seeing anything similar? You know, and just like start the discussion on like, have you heard anything? Oh, that's interesting. You want to do a test? You know, like we get the ball rolling on conversation for good reason and not just like cold outreach.
Oh, yeah, there's no notion of quarterly planning in my flow. And I think that's probably the case for a lot of startups.
We generally have a sense for what the next four to six weeks looks like. I'm not a religious follower of shape-up. I think that's a pretty popular methodology from the Basecamp folks that people have latched onto as a way to budget your time as a team and say, what are we going to let's fix the time budget and then get done whatever we can on what we set out to do and flex the scope as needed.
And I think that's kind of generally, folks have kind of coalesced around that as a good way to kind of shape your work. And I think it scales down to to pretty early stage as well. You might want to keep the cycle a little shorter.
Six weeks feels kind of long for a super early stage, but when you get to a place of product maturity where you're really just kind of incrementally improving it, I've seen that be a pretty helpful time range.
The goal there is to try to say, we're going to build this thing and we're going to build whatever version of it we can get done within our time constraints so that you don't let projects just run away on you.
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.
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?
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.
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.
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.
So it's just designed inherently with that in mind of many, many processes that shouldn't crash each other. And this works really well for WebSockets use cases where you have a bunch of people potentially on your site and you want to keep an open channel via WebSockets to be able to stream data back and forth. over a channel.
So channels are the mechanism that Phoenix has for basically opening WebSocket connections and then sending data up and down that pipe instead of going through old school HTTP requests, which are a little bit slower. And then the presence feature, this is actually a tricky computer science problem to solve.
When you're active on a browser window and you want to show that that person is actually present there, keeping that state synchronized with the server is kind of tricky. And you kind of just get that for free from Sockets. So, yeah.
Am I hired?
Showing 301–320 of 327 · page 16 of 17
← Previous
Next →