147

I'm working on a GitHub + Slack bot to let organizations customize and get notifications on Slack from GitHub.

I've tried using the official GitHub Slack integration (https://github.com/integrations/slack) but found it limiting and unmaintained by GitHub. For example, at the companies I've worked at, we want to get notifications sent to a specific channel when there are deploys to the "production" environment on GitHub. The official integration doesn't let you filter events by environment, so it's all or nothing. Your Slack channel for production releases will be filled with staging and qa notifications.

I designed it so users can filter on essentially any field of any event - deployment environment, branch patterns, file paths, PR labels, commit authors, etc.

It's at chivesbot.com as a hosted service, however, the signups are disabled right now as I'm working on some core features, but here are a couple of screenshots of the filter creation: https://imgur.com/a/pSiolWu

I'm looking for early beta users and feedback, so if this problem resonates with you, my email can be found in my profile.

This infamous one: https://news.ycombinator.com/item?id=9224

I'm in the early stages of working on a Kubernetes cost monitoring solution.

The current solutions out there are too expensive and not self-serve.

If anybody else has this problem, I'd love to chat with you.

I'm sure somebody can provide a more comprehensive history, but I'm pretty sure it started with Microsoft being cargo-culted. Then when Microsoft stopped being as cool, everybody started copying Google and how they did interviews.

Microsoft did brain teasers like "How many ping pong balls fit on a bus?" questions. Then Google copied that to start. Google later realized that performance on these questions didn't predict performance on the job and developed a more data-driven approach that you see today (leetcode style) that other companies copy today.

I'm in the camp that interviewing loops all have tradeoffs, but if you're a smaller company you can't afford to copy how big tech giants interview candidates. Their funnels are much larger, and they can afford to skip on potentially quality candidates.

I'm working on https://chivesbot.com/, a GitHub Slack app.

I was frustrated by GitHub's official Slack integration and the lack of certain customization and filtering capabilities. For example, I wanted to be able to send all production deployments to a specific Slack channel, but I couldn't.

I've always wanted to do mechanical refactors and recently ran into the problem the author ran into where tree-sitter can't write back the AST as source. Is there an alternative that is able to do this for most programming languages?

Instantly hire a world-class infrastructure engineer for $7,500 a month:

Are you a small team that doesn't have enough DevOps resources? I will augment your team, dive in, and start delivering fast. I'm well-versed in AWS, terraform, kubernetes, docker, etc. I can help you build repeatable pipelines, documentation and provide a smooth hand-off to your team.

Rules:

- 1 active request at a time

- No recurring meetings

- Cancel any time

Money-back guarantee: If you're unsatisfied within the first three weeks, just let me know, and I'll refund you.

In the past, I've:

- Saved a company $500k a year in CI infrastructure costs.

- Worked with several hundred engineer organizations to migrate from Jenkins to GitHub Actions.

- Introduced configuration as code and GitOps best practices to teams.

- Built dynamic review environments triggered on a pull request.

Contact me at hn [at} builds.dev for more details.

Infrastructure Engineer As A Service: $7,500 a month:

- 1 request at a time

- Cancel any time

Contact me at [email protected] with any questions.

I’m an infrastructure engineer who can help you scale your company’s DevOps processes. I’ve been the first infrastructure engineer at a unicorn startup and have helped the team scale from a couple dozen engineers to over 70 engineers.

I have extensive experience with AWS, Kubernetes, Terraform, and more.

In the past, I've:

- Saved a company $500k a year in CI infrastructure costs.

- Worked with several hundred engineer organizations to migrate from Jenkins to GitHub Actions.

- Introduced configuration as code and GitOps best practices to teams.

- Built dynamic review environments triggered on a pull request.

Infrastructure Engineer As A Service: $7,500 a month:

- 1 request at a time

- Cancel any time

Contact me at [email protected] with any questions.

I have extensive experience with AWS, Kubernetes, Terraform, and more.

In the past, I've:

- Saved a company $500k a year in CI infrastructure costs.

- Worked with several hundred engineer organizations to migrate from Jenkins to GitHub Actions.

- Introduced configuration as code and GitOps best practices to teams.

- Built dynamic review environments triggered on a pull request.

Infrastructure Engineer As A Service: $5,000 a month:

- 1 request at a time

- Cancel any time

Contact me at [email protected] with any questions.

I have extensive experience with AWS, Kubernetes, Terraform, and more.

In the past, I've:

- Saved a company $500k a year in CI infrastructure costs.

- Worked with several hundred engineer organizations to migrate from Jenkins to GitHub Actions.

- Introduced configuration as code and GitOps best practices to teams.

- Built dynamic review environments triggered on a pull request.

I've struggled with perfectionism procrastination. For example, I've tried in the past to start a weekly newsletter for my blog but was never consistent with it.

In the middle of November, I started a daily (M-F) newsletter on topics related to DevOps. I've been consistent with it ever since.

The strategies the article outlines that have helped me the most are breaking things down into small pieces and starting small.

Also, by making my newsletter daily, it took a lot of pressure off me. I didn't feel like I had to have a "hit" every article like with weekly or monthly cadences. If the article sucked, then tomorrow is a new day with a new article.