text stringlengths 0 2.67k |
|---|
**Justin Garrison:** So our outro... I wanted to talk a little bit about Git again, because Git is just central to a lot of things that we do... And I have been using this packaged version of all of these scripts called Git Extras. I've been using it for more than a decade. I don't remember when I've found it, but I've... |
\[01:06:13.18\] Well, this Git Extras repo and package is all just a bunch of community-driven common commands that you have to do. And it's just like "Oh, we just wanna make a subcommand that anyone can rely on, and it works the same way", and Git Extras is that way of packaging it. |
And the first one that I started using was - they have a git pr. And the pr command will fetch a pull request from an upstream repo, and then check it out locally in a branch and track it. And usually, that's like three commands. It's like "Oh, I've gotta go find what number it is, and then pull it down..." And if it's... |
The other one that I like... There's a few of them. I'm just gonna go over them, because I've been using it so long, and I'm just going to point people to it. One I used to use a lot was git standup. It was the standup subcommand, which is you say your name, so like git standup \[unintelligible 01:07:22.00\] and how ma... |
You can just go run this and say "These are the commits that landed." It's not necessarily all the work you did, but it reminds you of "I was working on this feature", or "This reminded me of something else I did." So I really enjoyed the standup command. Pr's the one I use all the time. |
Git undo... If you want to just undo the last git commit -- like, how many times have I wanted to do that? I'm like "Oh, it's head, with a carrot" and like "Oh, I need three commits ago", you just do git undo 3. And it does that command for you as just -- it's more of like an alias, because it's a one command thing... ... |
It is easier to use than the syntax that I always have to look up... So I use undo more often. But there's a bunch of other ones in here... There's stuff that I would have never thought of or wanted to use, like git scp, where you can literally clone your local state of Git into another place without doing this whole G... |
Get summary is kind of fun, because it just looks at all the history of the commit messages. It says how many commits are there, who's committed the most... I did it on one of our repos for work, and one person has like 40% of the commits in this repo. And it was like "Yeah, they do a lot of work on this repo", and tha... |
\[01:09:06.05\] What was the other one I was looking at...? Setup. That was the one git setup is like a git init, and then a git add, and a git commit. All those three commands. If you're in a folder that has files you're already starting to work on, and you're like "I need this to be a Git repo", you can just type git... |
So I like it. It's just a collection of scripts. You can brew-install it as Git Extras. Again, I've been using it for such a long time... I occasionally -- like, probably once a year I have to go back and look at it, because there's going to be more commands that get added, because it's just open source, and you can PR... |
**Autumn Nash:** I was gonna say, can you open source, like contribute to it? |
**Justin Garrison:** Yup. They do take contributions. A lot of them will be like features that I've seen, where it's like "Oh, I wanted this one thing that works different than what you were doing before." There was another one... Delete merged branches is a great one. It was like "I need to clean up a Git repo." And i... |
**Autumn Nash:** That makes sense. |
**Justin Garrison:** Yeah. So a bunch of like helpful stuff like that, which are usually small-ish scripts, like maybe a handful of commands that are Git-related... You can go to the top of the repo, you can do stuff... But you can use these scripts as other automation, where it's like "Give me--" I have aliases for a ... |
**Autumn Nash:** That's pretty cool. |
**Justin Garrison:** Yeah. Because they're just -- they're things that make your day a little better when you're like "Oh, let's install this one and try these out." And so yeah, I wanted to throw that out there, because this whole episode has been Git, and it's been fun. |
**Autumn Nash:** I really think that it's amazing... At first in my career -- not my career. When I was in college. I was a little scared of Git. But once you start using it and stuff, it's amazing the crazy things you can do with Git. |
**Justin Garrison:** You definitely become familiar with enough of Git that you're like -- again, it's your skill level. My Photoshop level and my Git skill level are like the bottom 30%, 40% of everything that it does. I just don't need most of it. But the things that I know and I'm familiar with, I can work my way th... |
**Autumn Nash:** Yeah. Sometimes you have to just like throw it all away and start over. |
**Justin Garrison:** Thank you, everyone, for listening to the show, and we still enjoy your feedback. If you have people and topics that you want to have on the show, feel free to email us, shipit \[at\] changelog.com, and we will talk to you all next week. |
**Autumn Nash:** Also help me bully Justin into coffee. |
• Influx Data's new cloud dedicated service allows for single-tenant instances of the database |
• The service runs on K3S, with each tenant having its own Kubernetes cluster and instance of InfluxDB v3 |
• Lili Cosic discusses her experience joining Influx and learning about their architecture and technology stack |
• She highlights the benefits of using InfluxDB v3, including high cardinality support and customizability |
• The discussion touches on the switch from Go to Rust as part of the database's rewrite, and its advantages in terms of performance and efficiency |
• Lili Cosic's background with Rust programming and troubleshooting Containerd issues |
• Comparison between Prometheus and Influx as time-series databases |
• Key differences between the two: |
• Prometheus is more specialized for specific time-series metrics format |
• Influx is more general-purpose and flexible |
• Prometheus has a write-ahead log, while Influx does not |
• Use cases for each database: |
• Prometheus: primarily for measuring data at regular intervals, suitable for alerting and rule evaluation |
• Influx: suited for long-term storage of metrics and can handle large volumes of data efficiently |
• Immutable nature of Prometheus data and its implications for auditing and deletion |
• Experience with the TICC stack (Telegraph, Influx, Chronograph, Graphite, Capacitor) and its integration into Influx V2 |
• Puppet infrastructure issues caused by excessive database connections |
• MongoDB security concerns due to default password-less setup |
• Specialized databases vs general-purpose ones like Postgres |
• The importance of expert help and support for databases |
• Experience with Prometheus, OpenShift, and Kubernetes operators |
• Acquisitions in the industry, including Red Hat's sale to IBM and CoreOS's impact on OpenShift |
• Kubernetes operators and custom resource definitions (CRDs) |
• History of CRDs and their shift from third-party resources |
• Origin of the term "operator" and its misuse by some companies |
• Discussion of databases, including CockroachDB and TigerBeetle |
• Lili Cosic's career path and her experiences at various companies, including Red Hat and HashiCorp |
• Open source challenges in management and responsibility |
• Comparison between Red Hat and HashiCorp approaches to open source development |
• Difficulty of integrating open source projects into a business framework |
• Balancing company stakeholders with open source maintainers' needs |
• Managing people who want to build on top of open source projects vs. those who just use them |
• Strategies for growing a career in complex spaces like databases and infrastructure without burning out |
• The challenges of open source development, including the lack of boundaries and expectation of immediate response |
• The impact of corporate funding on open source projects and the influence it has on decision-making |
• The shift towards more restrictive licensing in open source, allowing companies to protect their investments |
• The role of foundations, such as the CNCF and Linux Foundation, in governing open source projects and creating a neutral ground for collaboration |
• The politics involved in open source development, including pay-to-play models and the influence of large corporations on project direction |
• The importance of community involvement and welcoming culture in successful open source projects |
• Discussion of social media presence (Lili Cosic on Twitter as @lilicosic) |
• Lili Cosic discusses her career and work with Influx |
• Guest leaves the show |
**Justin Garrison:** Hello and welcome to Ship It, the podcast all about what happens after you git push. I'm your host, Justin Garrison, and with me, as always, is Autumn Nash. How's it going, Autumn? |
**Autumn Nash:** Good. |
**Justin Garrison:** Good. Just -- it's fall, though. You've got to be a little more excited than that, right? |
**Autumn Nash:** I'm waiting for the coffee to kick in. |
**Justin Garrison:** Well, you should have had it earlier. It looks a skull cup. This is Halloween time now. |
**Autumn Nash:** \[unintelligible 00:04:57.14\] we'll drink out of the skulls of our enemies. And I was "Don't tell that at school, though." |
**Justin Garrison:** I had my hot chocolate this morning after we had a conversation, our last week's conversation with Dave, talking about hot chocolate... And I got a free Starbucks for my birthday, so I went and got a hot chocolate. It was great. |
**Autumn Nash:** Happy birthday, Justin. |
**Justin Garrison:** Thank you. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.