Mason McLead

We're just saying that's what it is. And it's interesting that that's what the number is versus six hours, eight hours, which is what a lot of people believe about developers.

We're just saying that's what it is. And it's interesting that that's what the number is versus six hours, eight hours, which is what a lot of people believe about developers.

Well, I mean, just to bring it back around to... Ruby stuff since we're on the Ruby podcast. The new version we just launched last week is now a Ruby on Rails app. So it actually, there is Ruby involved in this. Hey, nice. Yeah, it was Node.js backend with a React frontend before.

Well, I mean, just to bring it back around to... Ruby stuff since we're on the Ruby podcast. The new version we just launched last week is now a Ruby on Rails app. So it actually, there is Ruby involved in this. Hey, nice. Yeah, it was Node.js backend with a React frontend before.

And this is something that I'm going to be publishing soon on our blog, but we have, of course, productivity metrics between, for our own team, between the different systems that we've been working on. So I'll be able to do a compare and contrast on our own team's productivity using Node and React versus Ruby on Rails. So like just more fodder for the internet to argue about.

And this is something that I'm going to be publishing soon on our blog, but we have, of course, productivity metrics between, for our own team, between the different systems that we've been working on. So I'll be able to do a compare and contrast on our own team's productivity using Node and React versus Ruby on Rails. So like just more fodder for the internet to argue about.

I mean, I think that's something that we'll be we'll be starting a series on this of the languages that we see, the frameworks that we see, the different technology pieces that our global users have installed, that we can see the differences in their productivity metrics with and without those things. So there will be plenty of interesting conversation about what's the best JavaScript framework.

I mean, I think that's something that we'll be we'll be starting a series on this of the languages that we see, the frameworks that we see, the different technology pieces that our global users have installed, that we can see the differences in their productivity metrics with and without those things. So there will be plenty of interesting conversation about what's the best JavaScript framework.

We're using Stimulus and Hotwire for all of our graphs and everything. So whenever you load the dashboard, all the data is getting pulled async. and loaded through HTML partials that show up through stimulus and hotwire, the whole thing. And we also have a feature where you connect your GitHub and it pulls the last 90 days of your history so you can see stats on that.

We're using Stimulus and Hotwire for all of our graphs and everything. So whenever you load the dashboard, all the data is getting pulled async. and loaded through HTML partials that show up through stimulus and hotwire, the whole thing. And we also have a feature where you connect your GitHub and it pulls the last 90 days of your history so you can see stats on that.

And it's got little loading bars. We wrote zero JavaScript for the whole thing. And it's a completely animated... loading bar that's in sync with all the data that's being pulled through. I had my, usually he, my engineer is, his name's Daniel. Let's see, my engineer. His name's Daniel. He's a person. He hates writing front-end code.

And it's got little loading bars. We wrote zero JavaScript for the whole thing. And it's a completely animated... loading bar that's in sync with all the data that's being pulled through. I had my, usually he, my engineer is, his name's Daniel. Let's see, my engineer. His name's Daniel. He's a person. He hates writing front-end code.

But I got him to do this because he didn't have to write any JavaScript. And he was like, I'm a full-stack developer now. And he was really happy about it.

But I got him to do this because he didn't have to write any JavaScript. And he was like, I'm a full-stack developer now. And he was really happy about it.

I mean, once getting into it was a little bit, you got to kind of shift how you think about building it. But once you do that... it's made developing all of the graphs and everything. And like the first paint on load is really, really fast because all the heavy stuff is coming in async. And it's because it's just replacing the existing HTML. It's not shifting any of the,

I mean, once getting into it was a little bit, you got to kind of shift how you think about building it. But once you do that... it's made developing all of the graphs and everything. And like the first paint on load is really, really fast because all the heavy stuff is coming in async. And it's because it's just replacing the existing HTML. It's not shifting any of the,

The structure around it's come along really nicely.

The structure around it's come along really nicely.

Yeah, so I didn't know that we could pick random physical objects like JB Weld as well. So I'll have two today. First one in the tech world, MaterializeDB. is a real-time streaming database that does transformations with automatically updating materialized views. Super cool. I'm experimenting with our data streams with that now. and really liking what I see. Super, super snappy.

Yeah, so I didn't know that we could pick random physical objects like JB Weld as well. So I'll have two today. First one in the tech world, MaterializeDB. is a real-time streaming database that does transformations with automatically updating materialized views. Super cool. I'm experimenting with our data streams with that now. and really liking what I see. Super, super snappy.