The strength of Go in the job market 📈, and some stress relief with Carlos Becker 🚀

This show is supported by you. Stick around till after the news for more about that. This is Cupid Go for 02/21/2025. Keep up to date with the important happenings in the Go community in about fifteen minutes or twenty minutes or thirty minutes, sometimes. I'm trying to recall.

And I'm Shay Nehmad. As long as it's time dot duration. Right? Isn't that great that Go has a native duration type?

I like that. Yeah. Yeah. I was recently playing with that. The the log, system I'm using, expects duration to be an integer, and I was sending it, I think, the stream representation, and it was screaming up my log, so I had to change that. Why are you logging durations? For HTTP requests or certain other tasks that happen. It's Oh, nice. Sometimes useful to know, especially when they start to exceed certain thresholds.

I wonder if my microwave implementation uses time dot duration.

Your microwave implementation. I don't know.

Like, someone implemented the the button. Yeah. By the way, don't you feel I don't know if I'm the only one that does this. Do do you use a microwave? I know some people are against it.

Yeah. I use it.

Do you sometimes, like, instead of doing the thirty seconds thing, do, like, twenty seven seconds just to make sure you use all the buttons, you know, on the on the panel to make sure that you distribute the load. Just me? Okay. Moving on. We have a pretty cool show for you today. We have some announcements to do, talk through, talking a bit about the job market.

We sure do. We're interviewing Carlos, the maintainer and and author of Go Releaser and a few other popular open source libraries. So stick around for that.

Very cool. Very cool. If you use Go Releaser, and many, many, many, many, many people do, such including my, like, my previous team.

And including Rust and Zig people, potentially. For sure.

So kick us off.

Yeah. So, first off, we have a couple pre announcements for security releases. We don't know what they are yet, but, on Monday, new versions of golang.org/x/oauth2 and golang.org/x/crypto will be released.

So Nothing scary.

That we know of. It might be super scary. We don't know. Maybe this is like the end of the world stuff, but we won't know till Monday. So as long as the world doesn't end until then.

For sure. So just do I need to put on my calendar to upgrade my crypto packages on Monday?

You should you should upgrade your crypto packages every day.

The I'm wondering how many people do this proactively, like, when they listen to us or they just come into work and, like, depend about this opening a PR and they're like, oh, this rings familiar. Oh, right. They talked about it.

Yeah. Interesting question. I don't know.

Well, talking about people coming to work, like that segue? It's my segue. I follow, the pragmatic engineer, newsletter. I'm actually a paid member.

Oh.

Yeah. I did it by accident.

So I wonder if we have any accidental Patreons for

the show. Well, I I all dollars are green. No problem as far as I'm concerned. But, yeah, the the programmatic engineer is actually, like, unironically, pretty good, like, blog posts, but substack kind of thing Mhmm. With deep dives about various things.

That's interesting. I've I've noticed, an upward tick in in opportunities since the beginning of the year. Although, maybe that's just my very specific niche.

I don't know. So there there is when you look at numbers, there is a low in job listings. That doesn't mean there are fewer jobs or less need. It's just a number. Right?

That surely that depends a lot on on the startup. Like, I'm working with a startup right now where I'm the only back end engineer, and there's, like, three front end developers. But it's a it's a game. So that's I suppose I suppose if you average it out, maybe the majority of startups are not doing

a front end. A VC backed startup game. It's just like a company.

I don't know if it is. It might be a startup back. I I think they've got some VC. Interesting. Yeah. But, I mean, it's it's still pretty small potatoes, though.

This is coming from, like, a a recruitment agency. So I guess this is, like, the average when you average out all the noise in all the companies, this is the average experience you'd get. And another caveat, this is just in The US. Although usually The US market tends to reflect what's happening in the rest of the world, just with higher salary. And, you know, listeners from specific countries, you know I'm talking about you, you know when developers from insert specific country here are the best compared to the you.

Mhmm. Mhmm.

Anyway, so the text stacks for back end, TypeScript is easily the most common. I'm doing TypeScript back end right now, by the way, in my new startup. Very frustrating. That's a fact. It's a type language bolted on to a JavaScript engine, like a browser software.

Yo. Honestly, it's not my my it's not the language that I I find problematic per se. I mean, I I do for other reasons, but that's not what I'm talking about. I don't know why you would choose to build your back end in a single threaded language these days. Mhmm. Because, I mean, all else being equal, chooses choose another simple language that's not single threaded.

So I think people are really sick with Python because of all the tooling issues, but that's getting better with, whatever, Astra are doing. You know, I don't know if you know, but they're doing rough and doing u v. And they're sort of solved the the tooling problem in in Python to the best of their ability. Mhmm. It's a lot better now.

I I think Go is definitely entering the mainstream. Maybe it already has, I suppose, as a way you draw that line. It's younger than either of those two, so it's it's, expected that it would be less popular just by sheer force of of of knowledge, I guess, or whatever. Mhmm. If I knew all three languages equally, well, I can't think of any reason I would choose TypeScript or Python over Go for back end work because Go has that that multi threaded capability.

I think a lot of people have a bad experience with Go trying to model very high level, business stuff that is very fluid from, like, five years ago. Like, if you try to do go for your startup five years ago before, a lot of recent improvements and a lot of, like, five years ago, the comp the language was, like, half its age, basically. Right? We've gotten a lot of experience in the last five years as a community. Right?

Yeah. And and that closely relates to what I was probably the most important aspect of any of these languages, which isn't multithreaded or performance, whatever. It's how easily can you hire developers. And so if you're trying to you know, especially if you're a startup well, I guess, it depends on on your technical expertise. If you are a technical founder and you have the ability to vet your developers, maybe it doesn't matter so much.

Mhmm. The

And if you're if you're at scale up stage, then that's another another situation. You know, can you hire enough Go developers with the experience level you need to to scale your product? Maybe maybe not. Maybe that's easier to do with TypeScript or or Python for the same reason. There's more people in the market.

I definitely think that there's a shift, like, it might have not hit the recruiting, agencies yet, but I think there's a shift to smaller teams with more experienced developers because you can do a lot more with, like, AI tooling automation, blah blah blah. At least that's a promise. Right? There's also another benefit if you're doing, full stack, which is the other 25%. People say you need react like, the common cases you need react for the front end and TypeScript, for both front end and back end.

Mhmm. I don't

know if it's misguided or not, but it it's definitely reasonable. Right? You're building something and you don't know if people even want it or will pay for it. Why care about the, like, multithreaded performance before you know it's ready?

That that that's that's absolutely valid if all else is equal. And that that's what what you know, I made that that comment earlier. Now if all else is equal, I would choose Go over Python or or or TypeScript. You do make a strong argument. If you can only afford one or two developers, maybe you want, developers types of script experience because they can do both front end and back end.

Anyway, so a pretty cool, cool blog post. We don't do a lot of shout outs for, like, other non Go, like, media outlets. Right? Yeah. But definitely, if you're looking for something to read that's not Twitter on the train, Pragmatic, I can definitely recommend Pragmatic Engineer.

I still don't know TypeScript, and I haven't found a reason to learn it. But, I do but do JavaScript.

So Oh, just imagine three v eight engines in a tread trench code trying to behave like a real language. Cool. Let's talk about Go Go.

We should talk about something else now. Let's segue oh, sorry. You weren't done. Go ahead and finish what you were saying.

I was trying to segue.

Yeah. I was trying to segue too.

So let me do

Let's try to segue wait a

minute. Let's do it together. Wait.

We need somebody to to solve this. No. We should we should have tested this before recording, how to do these segues without trampling on each other.

Yeah. But how can we do testing for sync like, things that happen at the same time?

Yeah. I wish we had, had known about testing sync tests before we recorded this program. That was a really clumsy segue. I hope it worked out.

It it definitely, drives home the point that, doing, async and sync things is difficult. What's this blog post about? How can it help me?

Yeah. So, we we we I think we mentioned it last week. We certainly mentioned it before. A new feature, a new experimental feature in Go one twenty four is the sync test package. And, you to enable it, you have to enable go experiment equals sync test on your on your build line. So, like, go, test or go experiment equals sync test, go test is would be how you do that. Right? So it's not there by default. But what does it do? It makes it easier to test, code that is timing sensitive.

I hate seeing sleeps in test though because Of course you do. Why on one hand, like, why do I have to wait? And on the other hand, it always feels kind of flaky.

Indeed. It is flaky. And and and, actually, they talk about that in detail here. So, you know, say say you do ten milliseconds, and then maybe it'll work fine on your local machine, but you upload it to your, your slow overloaded shared CI server, and maybe it takes a second for that to happen. So you had a longer sleep.

Poor old, Jenkins server running on the, like, bottom of the server rack with cobwebs is, like, struggling. The little server are good. So how can we solve this?

Yeah. So the solution no. The the experimental solution here is sync test. It introduces two, functions. One called run and one called wait.

And there are specific use cases here they mentioned, like, testing for network code and IO operations and, like, how how to reimplement this with the sync test. Mhmm. This is experimental. Right? So it means that I don't have this by default.

Right. You have to enable it. And the the API is not guaranteed to be stable. It could change. Of course, that's the whole reason for an experiment is to see how people react with it.

Cool. There's an issue for feedback. So if you do play around with it and find, like, places for improvement or something like that, at the bottom of the blog post, there's, like, the proposal where you can share your feedback.

Indeed.

Very, very cool. How does this I'm wondering. I I I didn't see any mention of it in the blog post, but, like, I'm wondering how this works with, test race. Right? Mhmm. Like, the race detector. It's probably, like I think it should work. I don't know if these features are completely, like, congruent or if you suddenly turn on sync test, it messes up the test detector. You know what I mean?

I would I would expect that it would work fine.

The race detector, I mean?

Yeah. The race detector should work fine with it. It's a good question.

It's it's very hard to to reason about, at least for me. Yeah. It it it's very simple on the surface to explain why you need it because it's very obvious to see the bad implementation and the good implementation, but just a few more mutexes and one more pipe and one more channel, and my brain is like, I don't know if, I'll do it correctly. But it's definitely an improvement of when trying to do it manually. Right?

Absolutely.

Would you use, like, an experimental feature in CI right now if it works well, or would you wait until the release? For, like, a not for a side project, for, like, a client project or a live Yeah. Yeah. That's a good question.

I would probably wait for the general release. Or I you know, one thing I can imagine doing is writing the test twice. Mhmm. Once using the old method, you know, like, rather than rewriting my test, copy my test and then rewrite them using sync test.

Interesting.

I don't know if I would actually do that, but I could it's it's something that comes to mind as a possible solution.

It would definitely be useful for feedback. Yeah. Exactly.

Cool. One, final proposal I wanna talk about. This is one that's been on my radar for years. I'm really excited that it's getting attention again. It is currently and likely accept.

I'll be honest. I I'm probably always, returning JSON. Yeah. Yeah. Or plain text if it's, like Or

plain text.

Or HTML if it's HTML.

So the the whole idea here with content negotiation is something that probably a lot of people don't even realize exist because they just always return the same thing. But HTTP gives you the option for the client to tell the browser what format they want the content in.

Oh, for sure. Yeah. I do use that when I use, WTF as my IP. Because they have WTF as my IP and WTF as my IP dot slash JSON

Okay.

Which sends the same API request and then returns, you know, either an HTML page or a JSON object, which tells you, your IP address with a lot of profanity in the JSON key, which I really like.

So so basically, you can you can the the the client can pass a an accept header that says, here are the content types I can I can consume? This is commonly used maybe for for images. Right? I don't know if it's that common anymore, but certainly, browsers will do this. They'll say, I accept WebP and JPG and PNG or whatever, and they give an order ranking of, I prefer WebP over JPG you know, and so on and so forth.

Okay.

So, you can also use this for text types. So you could have, some I've I've seen some APIs where if you just use curl, for example, it'll return an HTTP I'm sorry, an HTML response that says four zero four. But if you put accept j application JSON, it'll return a JSON representation with the same error message. Same same concept. So this is gonna become part of the center library, or it's likely accepted it will.

Isn't adding things to the HTTP though isn't h HTTP like frozen? Wouldn't you need HTTP v two to add this, like, feature?

I don't think it's frozen. I mean, I I don't think it's anything officially that says it's frozen. It is a little bit bloated, and that there was some commentary on that talking about putting it in a different package. There was a an early suggestion to put it in a subpackage, you know, below the HTTP. I think HTTP util was what they thought of doing initially.

Why what suddenly, I realized looking at this proposal, it's from, like, 2017. What happened to, to to pop it back up?

Yeah. So the most, recent activity started on January 21, just a few weeks ago, when the Prometheus team, was finding more use cases for this. And so they they brought it back up, and brought the attention of the Go team to it. Go Prometheus.

Nice. Well, I hope this, gets merged just to because you seem very excited about it. Yes. Well, we have a lot of very interesting, things to discuss, but we are out of time. So let's do them not a lot of justice in the lightning round. Lightning round. Just two quick projects that, popped into my, onto my radar from Reddit. The first one is, Minecraft. Have you played Minecraft?

I tried once, and I couldn't get into it.

Wow. My wife and I, hours and hours on end. So OG, in fact, that I got it for her as a present on a CD. Woah. Yeah.

Sometimes. Mhmm.

So I I use, Tmuxminator, which, like, creates the sessions for you and you can save them in a file. So whenever you open your PC and your, like, Tmux session might have died or you restarted or whatever, you just go Tmuxminator start, and you have all your sessions and they're named so it's easy to navigate between them. Unfortunately, over the last, like, year or so, I've fallen down the rabbit hole of using terminals with tabs. Started with iTerm and then wrap, and now I'm in Ghosty. And doing both tabs, the terminals, and the TMux is kind of redundant.

Alright.

So, yeah, two cool projects. Awesome.

I think I heard recently that was it Sony? It recently stopped producing writable CD media. Better stock up now before Yeah. For for

if you ever need to save 500 megabytes of of a video. Yeah. Alright. That does it for news this week. Stick around for a short ad break and then an interesting interview after that. Welcome to our ad break. As Jonathan mentioned in the beginning of the show, this show is supported by you. This week, we have a new Patreon member. Thanks a lot to Jay Martin for joining our our Patreon supporters. If you wanna support the show, this is a hobby.

I see it.

I'm so stressed out, you know, trying

to release

my project. I've been crushing this, stress ball so hard. My hands are getting tired. Who can help me release go? Who can help me release all this stress? Oh, hi, Carlos.

Oh, yeah. That's part of me.

Alright. We have, Yogi and a stress anger management consultant. Carlos here on

the call.

Hey. Hello.

Hello, Carlos. So Carlos is, the brains and bronze behind the Go Releaser. Before we dive into it, how would you present yourself to our, beautiful audience?

Okay. Hello. My name is Carlos. I'm from Brazil. I live in Brazil. I've been working with software for over ten years. I don't remember how long exactly anymore. It's enough to a few old. I can say that. And I've been working with Go since Go 01/1943, something like that. And I created Go Reducer and a bunch of other libraries and CLIs. And I also work at Charm, so we do Go there as well. And, yeah, I think that's a good summary of it, I guess.

Cool. Cool. And for people who don't know, what is Go Releaser other than one of my favorite Go projects and the projects we talked about on the show multiple times?

Yeah. I've listened some of them, I think. Yeah. So go Google is there is a tool to help, as the name implies, releasing Go software. Since some versions of Go, it now also releases Rust and Zig and TypeScript depending on which, compiler you're using.

Now that it isn't just Go, does does the name need to change? And if so, I suggest stress releaser.

Yeah. I was thinking about that yesterday, actually, and I already talked about it with a couple of friends a couple of times. I really love the the logo we have right now, so that that's the the only thing holding me back. But I think I'm probably gonna have to change it for two reasons. One of them is the languages that's that's now supports more than one language.

Yeah. Something like that.

The logo is pretty great. It's like the gopher, just riding to the stratosphere on top of a rocket.

Yeah.

So I just wanna say, like, I I've used the I've worked at the Orca Security, which is a a pro license holder of GoReleaser, and we super love the tool. Very useful if you're, like, a company and you have, your thing and you want your customers to be able to use it and you don't wanna be worried about all the release and deploy and all these, like, automating all this nonsense. The thing you said about writing a YAML and it just works, like, yeah. Happy customer here for sure. Jonathan, do you use a Go Releaser for any of your libraries?

I I do. I use it I use it for my KIPOC, package. It's, open source library and a CLI tool. So the CLI tool is built and released to Go Releaser.

Cool. Yeah. Nice to hear you. You sure use it and like it. That's it. Yeah.

It's it's pretty widespread compared to, like, you know, 15,000 stars, and all, all that stuff. So I'm interested in hearing, so you wanna add more languages. What other cool things are, like, on the roadmap?

I have a couple of things I want to do. One of them is related to Docker images, because right now, the configuration is a little bit repetitive because initially, there weren't, like, Docker manifest. It was just Docker images. Now there's manifest, so you have to create the image images configuration, and then you probably have to copy a a bunch of labels from one configuration to the other. So it looks like a big chunk of really similar YAML code, and then you have to wire those into the manifest.

What's the difference between a cask and a formula in in Homebrew? Like, I know I have to sometimes add minus minus cask, but I actually don't know why. I'm just copying the command line of the website and and doing whatever it tells me.

Yeah. If I'm if my memory serves me, I think a cask is is supposed to be used to install pre compiled binaries and apps and things like that. And the formula is supposed to build from servers. So since forever, we've mimicked building from servers, but we actually are installing pre pre installed pre build packages pre build banners, actually. Yeah.

It's

probably going to happen eventually.

Cool.

How much time do you spend on this? I mean, this this sounds like a really ambitious project supporting multiple languages and multiple build targets. And look. You just look at the feature list. It's a lot of stuff. And I I know it's been building up over time, but it still has to be a certain amount of effort to even maintain what you have without adding new features. What what kind of time are you spending

on this? So I'm not very consistent, I think. There are days I don't do anything and other days, like, I that I sit, like, five hours straight or something. So I don't really know how much time, but it's not that much time anymore. In the beginning, it was more because there are there are more missing features, I think.

I'd I'd also like to talk about you have a paid version, a pro version. I don't know how many people are aware of that. I mean, I know a lot I've I've spoken to many people who have heard of and use GoReleaser at meetups and so on. I don't get the sense that the pro version is as well known. Talk to me about that. What let's let's start with this. What's what are the differences between the pro version and the free version?

The pro version has some extra features, basically. It has, the recent features I added there is, like, AI to, change your changelog if you want to do that. There are a couple of extra options regarding Tink MSIs and you can import, rebuild binaries from other sources. And, it's a bunch of small leach things. I think the biggest difference there is that you can actually split the build by, operating system or target and merge it, later to, so you can like, if you use Seagull, for example, you can build like windows on a windows machine and some Linux machine, etcetera, And then do another job, like, merging everything and, like, pushing the images and all that stuff in the the last part.

Yeah. So that that brings up my my next question. If you're willing to share this publicly, I'm curious how many subscribers you have to the pro version, or or if you don't wanna share numbers, just some sort of sense of scale. Is it a lot of people? Is it just a few?

It's about if I'm not mistaken, the last time I looked, it was about 200 subscriptions. So it makes around four k in a row, give it give or take. So it's that's good to go for me running it solo.

For a side project. Yeah. Yeah. It's not a it's not it's not a full salary, but it's a good side project. Yeah.

In Brazil, it actually can be a a a good salary. Yeah.

Could be. Yeah. Yeah. Yeah. That's not your only open source project, though. I mean, I actually recognize your GitHub handle mostly from your e n v package, which I import in almost every project I work on. Is that something that that came out of Gorillaser, or is that completely independent?

I think that's independent. I don't remember starting it from Gorillaser. If I'm not too crazy, I think I was kind of inspired by some Java libraries that I used back in the day. I think there was one too many. I think it was environment variables to Java classes or something like that. And I was like, no, that's a good idea. Did that with Go mainly to learn, like, the the Reflect API and all that that stuff. People apparently enjoy it, and it's on version 11 now. So it's there.

And I again, this is sort of another, going back to, Jonathan's question. I know I use charm. I use gum a lot. Charm basically make, like, very, very good command line tools, and that's what I know, at least. I love the, like, terminal UI frameworks and GUM especially because it's so easy to plug into bash scripts and just have a super nice picker and, like, not worry about it too much, and, that's really cool.

Yeah. So we are working on that. Right now, we are leaving off, investments. So we don't have any any paid products yet, but we are figuring that out. And I can't say more about it for now. So Oh, Okay.

Now I wanna know even more.

Sorry, Shai. You can't know how the sausage is made.

For sure. And what do you do in, Charmer? Because Charmer has a lot of projects. Right? Like, various libraries, animations and Sage apps and style libraries that do you like dabble in all of these projects or is there like one thing that's you?

There are a couple of projects that I created. I think I contribute to pretty much all of them at least a little bit. But I work mostly on Wish, which is the SSH app from your, on mods, which is the AI command line thing. I recently did a lot of things in Grum and, saw bubbles that, are used everywhere else, which is, for those who don't know, bubbles is a component library for, for command line apps. I contribute to Bubble Tea more or less often.

Do you tend to, like, reach for, you know, the the charm things more often? Because, theoretically, you can do command line applications just with flags. Right? You don't really need all these good looking things. Do you think it's a it's a good default, or should should people only reach for charm when they actually build a terminal UI?

You you mean the differences between a a TUI and a, yes, and a CLI. Right?

So the difference between the CLI and and TUI is that TUI is look better, and they're more interactive, and they might have, like, features where you can scroll and enter and they are stateful, etcetera, etcetera. Do you think that the default should like, when you develop a new a new tool, is your default at this point alright. I I want it to look nice and be interactive, first, or is your default still like the Linux mindset of let's just keep it simple and do a CLI first and only do a TUI if it makes sense?

It depends a lot on what I'm I'm building. If it's something that could benefit from being interactive, I I probably do it interactive at least at some point in time. Maybe not, like, for starters, but eventually. But, yeah, I I really like, like, automating things. So even if I do something that works, like, interactively, I also try to make it work non interactively because shell scripts and so on and piping things through through each other and all that good stuff.

I tend to reach for, gum pretty often. Gum is the it allows you to really quickly insert, like, a picker into your scripts and whatever. But then what happens is when I wanna rerun the command really fast, I I find that I can't because I can't just, like, type the command, press enter, and I because I have to go through, like, a interactive segment. And then I'm, like, kicking myself in the in the channel, like, ah, why did why did I implement this interactive part? But some of the TUI's I've been using for, like, when you actually do interactive stuff, they've been really, really, really nice.

Honestly, I don't know. I I think charm is, if not the most popular, but one of the most populars. I I don't know. Like, there's Textual in Python, I think. Protatoo in Rust that are also pretty famous. There is the old one in c, and Persis. Yeah. There's I don't know how to measure popularity either. Like, if it's GitHub stars, probably it's charm. If it's usage out there, I would bet on main curses, I think.

For sure.

There's a lot of old things out there for main curses. So I guess it depends.

GitHub stars are such a weird metric. You have a tool that that measures GitHub stars, right, or or prints them, I think.

Yeah. It tries to graph them, like, over time. It was mostly me being curious about, like, how projects get to, like, 10,000 stars or something. But I don't know if this changes this change it, but when I created it, you couldn't, like, get it exactly build the graph properly because it only returns the stars that are still there. So if someone started, like, I don't know, two years ago and then on star.

I always wonder if it's a vanity metric or if it's a real metric. I love when people star my projects, but, obviously, none of them have been as successful as, something like Go Releaser with 15 k stars. I assume the, like, the paid licenses are a much more meaningful validation of of, like, the work is actually useful or download numbers or or number of issues, things like that are are much more I don't wanna say valid because they're both valid, but I I would say more real or more concrete, like, feedback that the project is actually good than feedback than GitHub stars. Right?

Yeah. I think so. I think the thing with GitHub stars is that we don't really know how everyone else uses them. Some people star anything they like. Some people only star things they use. Some people use it as, like, bookmarks or whatever. So it means someone look into it and, at least felt something, so they start it. But I don't know how good it is. If we think, like, financially, yeah, for sure. The like, the MRR and all those metrics are are better success metrics, I think.

Which I'm happy I'm happy about just to like, I don't wanna I want I don't want you to leave this interview. Like, yeah. Next release of Gorillaser. Everything is behind the paywall.

No. I will never do that. You

only get half the binary. You get 50% of the bytes. You have to pay me for the rest.

No. I would never do something like that.

You remember back in the shareware days when the the free the free version would have, like, a time dot sleep thirty seconds before it would start running?

There are some good stuff from that era, man. I never did this, of course, but a friend told me that you, like, get a a, like, a shared key generator for, like, a software you want to use, and it had the most awesome music and the best artwork on it. Like, you open it up on your Windows, which is like just you click on it. You get a, like, a UID. It's basically a UID generator.

Yeah. Need first piece most wanted to have the key generator like that.

You know what

I'm saying? Obviously, we don't, EA, I don't know who owns is it two k now? Two k, if you're listening, obviously, we're we're just talking about things we saw on our friends' computers. We always paid for our copies fully. Don't worry about

it. Yeah. Totally.

So, Carlos, for the Go Releaser and the other blog post that you're putting out and all your links and whatever, where can people find you if they wanna reach out about the projects you've told us? As you've told us off the record, some things that might be cooking and you're not willing to divulge yet, but maybe people wanna talk to you about.

Yeah. So go redeezer.com for everything Gorillizer related. You can go to carlosbecker.com for my blog and personal site. I'm also on Max and GitHub, as, at carlos with two a's and the numb number zero in them, which is a very bad username, but it's been there forever, so I'm not going to change it. Yeah. I mean, I think those are the the main places. I'm most active on on Max and yeah. I think on Max.

That reminds me of one of the first questions I ever had when I saw your username is why the two a's or why is it Carlos?

So it's a funny story. When I created my first Gmail account, like, I don't know, 2,000 something. I tried to create cardosgmail dot com and then, it already exists. So Carlos one already exists. Carlos zero already exists. And then I just got annoyed and put like another a there and that's it. That that's how I

got it. And it worked. There you go.

It's definitely, definitely better than my, thing where I did, like, [email protected]. And then it was, already taken. And then I did, okay. You know what? [email protected], which is my personal email. And, you know, I've been applying to jobs at, like, super serious places or, like, going to my insurance agent or, like, what's your email? Like, it's d u d e five. And I'm really hoping that they don't spell it out in their head.

I I I have a fix for you. Get the domain and

I do. I do. Yeah. Now I have [email protected] for sure for sure.

Oh, I I thought you were gonna say you were shy at dude five hundred dot com.

I I you know what? The the best, the the the best outcome of this, like, problem is that when my daughter was born I don't know. It's not the first thing. Like, first thing I hugged her and then I cried, but definitely in the, like, five hours after she was born, she already had a Gmail account, which is like, [email protected]. In Google, you can do, like, family account. Like, I took care of that. She's not gonna make the same mistake.

She doesn't have a college savings, but she has a Gmail account. For sure.

That that's a good column. Yeah.

I I didn't buy a car seat. Like, I tied her to the roof, but she had a is a Chivo. No. I'm just kidding. Alright. Alright. Carlos, thanks for, jumping on the interview. We have a stumper question. Anton, you wanna line it up?

Yes. Yeah. So, the the audience, of course, already knows the question because we've asked it a couple of times this year. But the question, who has been the most influential, as you've been learning Go? And I know you've been using Go for a long time, so you might have to think back really hard. But, who in the Go ecosystem helped you the most? Maybe they wrote a book or a blog post or something like that.

So right back during the beginning, I started learning Go because I was working as a site reliability engineer. So I I figured out, like, well, Docker is written in Go. Prometheus is written in Go. Prometheus is written in Go. So I wanted to learn Go to be able to maybe fix issues that I had and things like that.

Mhmm.

And, like, you never know which one is the best. Most of the time there isn't the best ways. It depends on the case and not that. So, yeah, that person that I forgot the name now is is one of the biggest inflation influences on me. Later on also, Mitchell Hashimoto from HashiCorp because of Terraform and all of that line of software too. Yeah. I I think those are the probably the in goal is this true. Yeah.

Yeah. We

should we should, like, set up a hall of, of fame for all these, people. Like, people are mentioning different people as their, you know, influences. I think that's interesting.

Yeah. I think we can all, like, read the same things, but different things resonate with everyone. So everyone turns different conclusions from the same input sometimes. And Yeah. That's beautiful.

Cool. Well, Carlos, it's been a pleasure chat chatting with you. Thanks for all the work on Go Releaser. I continue to use it in in your other libraries and appreciate them. So thank you.

Yeah. And don't forget stress releaser. I think, you know, for a rebrand.

So send me name ideas.

Yeah. Just just imagine just imagine the swag. Right?

It's a good swag idea, actually. Yeah. But, yeah, thank you for for having me here today. It was really

fun. Awesome. Wonderful. That's all we have for you this week. Join us next week. Although, I might not be on the show next week. It might be just Jonathan. And thanks a lot. Program exited. Goodbye. Program exited. Goodbye.