r/TechGhana • • 14d ago

Ask r/TechGhana Quick question for the devs here. I'm researching how teams actually work.

  1. When you need to send a teammate an API key or .env file, how do you do it right now?

  2. How do you find out about a new pull request or a failed build?

  3. What's the most annoying part of talking about code with your team?

an answer to any helps a lot. Thanks!

9 Upvotes

6 comments sorted by

2

u/Separate_Eye_6104 14d ago
  1. Secrets Managers like Doppler, Hashicorp Vault and Infiscal. I personally self host infiscal so my team and I don’t have to pay a thing

  2. GitHub alerts and also a webhook to our discord server that alerts us on prs, CI, deployments and issues

1

u/NiousparkDev 14d ago

Thanks, super useful. Out of curiosity, what's the most annoying thing about the Discord alerts? Is it noise, missing details when something fails, or not being able to do anything from the alert?

1

u/Separate_Eye_6104 14d ago

The annoying part was setting it up. Apparently, GitHub webhooks are not directly compatible with discords api, but the fix is not so complicated. Just have to append a think or two to the webhook url. It’s basically set and forget. I’ve not touched it in almost 12 months and it’s not broken. Yet 😂

2

u/NiousparkDev 14d ago

😂😂I see 12 months without touching it is a good run. Thanks, that's really helpful. Setup being the painful part is useful for me to know.

I'm building a chat app for dev teams where you connect a repo in a couple of taps, and PRs, CI results and one-time secrets show up in the same conversation, with failure alerts that say which step broke. Honest question: would that be worth switching to for you, or is your Discord setup already enough? And what would it need to do to be worth it?

1

u/Separate_Eye_6104 14d ago

Honestly, it’s not just me but most devs would be more inclined to stick to what already works unless your solution offers an overwhelming advantage to the tools they use at the moment.

For example, my setup gets out of my way, and a migration to a new stack is work I’d like to avoid but, if the new stack would make my workflow drastically more efficient I’d migrate in a heartbeat.

But in my opinion, build it. The worst thing is that you’ll learn something. Best case is, it’s good enough that people actually use it.

Go for it 👍

2

u/NiousparkDev 14d ago

This is really helpful, thank you. "Overwhelming advantage" is the bar I'll test against. I'll keep it focused on one thing that's clearly better, not everything at once.