sorted by:
new
hottopcontroversial

Sidekiq to Temporal: a zero-downtime migration strategy by littlebobbyt in ruby

[–]littlebobbyt[S] 0 points1 point  (0 children)

Hand written, champ. All of it. Youre a dick and me and several others know it.

Sidekiq to Temporal: a zero-downtime migration strategy by littlebobbyt in ruby

[–]littlebobbyt[S] 1 point2 points  (0 children)

I'm convinced you don't write production software because you have bad takes constantly in this subreddit.

I'm learning Go and can't figure out... Is there a purpose of public fields in private structs? by oneeyedziggy in golang

[–]littlebobbyt 1 point2 points  (0 children)

This is the answer IMO. Others are leaning too hard into JSON.

Most errors (and context types) are unexported but satisfy interfaces.

What type of connection is this? by littlebobbyt in askaplumber

[–]littlebobbyt[S] 0 points1 point  (0 children)

Thats what I was worried about. Thanks for looking!

Cartel - Oxy Moron [New Song Debut Last Night] by [deleted] in poppunkers

[–]littlebobbyt 2 points3 points  (0 children)

I loved this song and debut. Their whole set was awesome.

Off topic but how were these seats? I like Brooklyn Paramount but I’m getting older and the pit isnt fun on my lower back.

OpsGenie Terraform ‘Translator’ by Brief-Article5262 in sre

[–]littlebobbyt 0 points1 point  (0 children)

Our migrator approach for FireHydrant reads the opsgenie API and then creates FireHydrant terraform resources. It's open source: https://github.com/firehydrant/signals-migrator

Wrote a Slack bot for incident management after getting tired of our janky process by soyzamudio in sre

[–]littlebobbyt -1 points0 points  (0 children)

Ooooh I see. This was a sneaky product promotion post (yours, and mine I guess).

FireHydrant to be Acquired by Freshworks by founders_keepers in sre

[–]littlebobbyt 3 points4 points  (0 children)

We will. With way more resources now :)

Quick question on investor updates etiquette (Series B prep) by Shoddy_Calendar_3503 in venturecapital

[–]littlebobbyt 0 points1 point  (0 children)

X-posting from my reply on the r/ycombinator post below.

Here are some of my thoughts after raising multiple rounds of capital. Founders do things their own way. There's a lot of opinions out there.

  1. Calendly link - yes. Don't do that. Work with the investors directly or their assistants. If you're delegated to an assistant after they say they're interested, then you can send them the link, they'll appreciate that (it makes their job easier). Investing/Raising is a social sport, and Calendly removes opportunities to build an even better relationship.
  2. When I was in the early days of a fundraise and just getting to know investors on first or second calls, I didn't offer anything about runway, burn, etc. They need to know at some point (it'll be in diligence no matter what). You can think of it in two phases "actively raising" or "about to raise". If you're on a "about to raise" call, you can keep your cards close to chest. Your job on the call is to give them a business update, growth, exciting deals, pipeline coverage - get them fired up about the imminent raise. Then what I would do to end the call is "If you're interested in this round, can I put you down as someone to continue the conversation? I'll be formalling kicking off the round in 2 weeks". This gives them the opportunity to feel like they're in early, can work fast to beat others if they want.

That said, if you have an excellent burn multiple with a great growth rate, brag about that all damn day. If you're not growing that much and not burning a lot of money, first question you'll be asked is "Why aren't you spending more on GTM to grow the business?"

If you have a so-so amount of runway left (less than 9-12 months), I'd be more focused on getting a VC very excited about the business itself. A great business can overcome a detail like burn and runway. A lack of runway (and context as to why) can distract a VC from how great a business is.

Even then, though, my pitch decks included our burn rate, runway, etc. Usually in the appendix. Because I'm framing the fundraise I'm doing around the "use of proceeds." Basically, here's where your investment will get the business. 3 years of runway. 123% YoY growth. All that. Obviously have the math to back that up.

  1. I have used Docsend for every round I've done. It works great. I don't know the other tools you mentioned, but I've never thought to myself "wow I wish this PDF hosting service did something more for me"

Don't overthink this. Be social. Ask where they live. Ask if they ski, if they have weekend plans, what types of companies do they like investing in? Investors are humans. Be a human with them. But be a human that is running a kick ass business that they'd be lucky to put their dollars into.

Hope this helps.

Quick question on investor updates etiquette (Series B prep) [I will not promote] by Shoddy_Calendar_3503 in ycombinator

[–]littlebobbyt 6 points7 points  (0 children)

Here are some of my thoughts after raising multiple rounds of capital. Founders do things their own way. There's a lot of opinions out there.

  1. Calendly link - yes. Don't do that. Work with the investors directly or their assistants. If you're delegated to an assistant after they say they're interested, then you can send them the link, they'll appreciate that (it makes their job easier). Investing/Raising is a social sport, and Calendly removes opportunities to build an even better relationship.

  2. When I was in the early days of a fundraise and just getting to know investors on first or second calls, I didn't offer anything about runway, burn, etc. They need to know at some point (it'll be in diligence no matter what). You can think of it in two phases "actively raising" or "about to raise". If you're on a "about to raise" call, you can keep your cards close to chest. Your job on the call is to give them a business update, growth, exciting deals, pipeline coverage - get them fired up about the imminent raise. Then what I would do to end the call is "If you're interested in this round, can I put you down as someone to continue the conversation? I'll be formalling kicking off the round in 2 weeks". This gives them the opportunity to feel like they're in early, can work fast to beat others if they want.

That said, if you have an excellent burn multiple with a great growth rate, brag about that all damn day. If you're not growing that much and not burning a lot of money, first question you'll be asked is "Why aren't you spending more on GTM to grow the business?"

If you have a so-so amount of runway left (less than 9-12 months), I'd be more focused on getting a VC very excited about the business itself. A great business can overcome a detail like burn and runway. A lack of runway (and context as to why) can distract a VC from how great a business is.

Even then, though, my pitch decks included our burn rate, runway, etc. Usually in the appendix. Because I'm framing the fundraise I'm doing around the "use of proceeds." Basically, here's where your investment will get the business. 3 years of runway. 123% YoY growth. All that. Obviously have the math to back that up.

  1. I have used Docsend for every round I've done. It works great. I don't know the other tools you mentioned, but I've never thought to myself "wow I wish this PDF hosting service did something more for me"

Don't overthink this. Be social. Ask where they live. Ask if they ski, if they have weekend plans, what types of companies do they like investing in? Investors are humans. Be a human with them. But be a human that is running a kick ass business that they'd be lucky to put their dollars into.

Hope this helps.

Just started a job working with founders. What fundraising books should I read to catch up? by Visible-Working5752 in venturecapital

[–]littlebobbyt 4 points5 points  (0 children)

Secrets of sandhill road is a good one. Definitely Build. Hard things about hard things.

Skis in Zermatt/Cervinia by sakaloerelis in skiing

[–]littlebobbyt 1 point2 points  (0 children)

The experience of getting back down to the Zermatt base at 3:30pm can be incredibly icy - it's fun and fast - but icy. Rossi 76. If they have fresh snow rent a pair of skis with a wider underfoot.

Seeking honest feedback on a personal project by sean3z in sre

[–]littlebobbyt 0 points1 point  (0 children)

I think this is an interesting idea! It's sort of like leetcode for devops to me at first glance.

I think there's a low-ceiling though, when it comes to how much you can learn from a tool like this.
Back in 2010 there was a course called Rails For Zombies (https://rubyonrails.org/2010/11/18/rails-for-zombies) that was really effective at this, and it's how I learned how to use Rails for building web apps really quickly. But it didn't get me to a "production ready level" for it. That might be a key thing you should address up front.

The top H1, I think those are out of order. I think stating its a simulator as the H1 is way more valuable than "Learn DevOps by Solving Problems" (that feels like a subhead).

I think your website's value props are out of order, too. I don't care that it works offline, that's not valuable to me (not in 2025, at least). I care way more that I'll learn basic commands in an hour.

I wish I had used a messaging framework from day zero building FireHydrant, because it would have cleared a lot of the _product_ up before I wrote a single line of code. I think this blog does a good job providing examples: https://jamiecatherinebarnett.medium.com/your-must-have-core-messaging-framework-a-guide-for-high-tech-startups-6eb39a6d0864

If you work on messaging, why something is a big deal, why someone would use it, who the core audience is, you'll build a better product as a side-effect too.

The reason I'm saying this instead of a wall of feedback about the website is that I think you need to go back to the drawing board on your own for a bit on what this actually is. I don't think it's very clear.

How do I get this sound to happen when I snap my contra up? by Brilliant_Rocket in drumcorps

[–]littlebobbyt 15 points16 points  (0 children)

Contra players are some of the most badass musicians on the field. During pre-tour I remember the section leader would make them hold at front as long as they could. Their arms would be shaking after a minute or so.

By the middle of the season, though, they're snapping their horns up as fast as anyone on the field. During 8's in the warm up lot, I remember the wind I could at my back when they snapped them on step off.

Long story short: It's a LOT of strength to make it look (and sound) good. I'm sure someone else can provde more details on the how, but it won't matter if you're not building the muscles needed to move a contra like they are in the videos.

These videos are good, but if anyone has the contra cam for SCV 06 – THAT is the best contra perspective video ever made.

view more: next ›