hookdeck-cli VS sourcegraph

Hookdeck | https://hookdeck.com| Remote- CAN | Backend DevOPs

We are seeking an experienced Backend/DevOps professional who has a passion for working with and optimizing databases, and who has hands-on experience with high concurrency and high throughput systems. We are a small team of 9, operating completely remotely and without a schedule.

We help developers spend less building and troubleshooting issues with their webhooks to focus on their products instead. We offer a complete infrastructure to develop, test, receive, distribute and monitor webhooks and asynchronous events.

If you are looking to be part of an early founding team, fully leverage your knowledge & talent, have an impact and work on hard scaling and concurrency challenges then this might be for you.

We are offering competitive compensation & generous stock options. Here are the roles that are currently open:

- Backend/ Dev OP (must be in Canada)

Hookdeck | Growth Engineering Team | Remote | https://hookdeck.com/

Hookdeck is building out the Growth Engineering team to help us improve the user experience across the entire funnel. We are a small team of 9, operating completely remotely and without a schedule.

We help developers spend less building and troubleshooting issues with their webhooks to focus on their products instead. We offer a complete infrastructure to develop, test, receive, distribute and monitor webhooks and asynchronous events.

If you are looking to be part of an early founding team, fully leverage your knowledge & talent, have an impact and work on hard scaling and concurrency challenges then this might be for you.

We are offering competitive compensation & generous stock options. Here are the roles that are currently open:

- Growth Engineer

Hookdeck (https://hookdeck.com) | Product Eng, Growth Eng, Backend Eng | Full-Time | Remote (World)

Hookdeck is an infrastructure to consume webhooks simply & reliably. Incoming webhooks are challenging because they require a well-built (and often complex) asynchronous system. We help developers spend less building and troubleshooting issues with their webhooks to focus on their products instead. We offer a complete infrastructure to develop, test, receive, distribute and monitor webhooks and asynchronous events.

If you are looking to be part of a early stage team, fully leverage your knowledge & talent, have an impact on the product experience and implement features from scratch then this might be for you!

We are offering competitive compensation, generous stock options and liberty over your geo & schedule.

We are looking forward to hearing from you! Email me at [email protected]

Shameless plug: if you like the development experience of webhooks at Stripe we offer the same experience on our platform at https://hookdeck.com/ which you can drop in to help you add reliability and a better developer experience to receiving webhooks from anywhere.

This is a fantastic resource! Thank you to the folks at ngrok for putting this together! As this site makes clear: webhooks are harder than they appear. Even just consuming webhooks it's easy to get bogged down dealing with issues around rate limits or recovering from bugs that cause missed events! Missed events being particularly painful with platforms that don't offer replay / retry.

Disclaimer: I work at https://hookdeck.com/ & I shamelessly plug our tool for giving you an awesome developer experience working with webhooks and helping deal with some of the concerns brought up on webhooks.fyi.

And if you are interested in webhooks at large a couple more resources worth checking out is the awesome-webhooks[1] list and the r/webhooks[2] subreddit (I just got ownership of the sub and started dusting it off this week after being neglected for the past few years! Please, come join!)

[1] https://github.com/realadeel/awesome-webhooks

[2] https://www.reddit.com/r/webhooks/

and then went throught the codebase: https://github.com/hookdeck/hookdeck-cli

Might I recommend Hookdeck as well?

https://hookdeck.com/

Very very useful for handling webhooks and making working with them including locally a pleasure.

Sourcegraph | REMOTE | Full-Time | Machine Learning Engineer, Developer Advocate, Enterprise Product Manager, Technical Advisor | https://sourcegraph.com

Sourcegraph is a code AI platform that makes it easy to read, write, and fix code–even in big, complex codebases.

We are building Cody, an AI coding assistant that uses code search and code intelligence to help devs quickly understand what's happening in code and generate new code that matches the best practices in your codebase. Cody supports AI-enabled autocompletion, fixing bugs, refactoring, test generation, code explanation, and answering high-level questions. You can read Steve Yegge's post on why Cody's code context engine differentiates it from the fast-moving field of AI dev tools: https://about.sourcegraph.com/blog/cheating-is-all-you-need.

Apply here: https://grnh.se/0572f98b4us

That's pretty much what https://sourcegraph.com/ are selling, is it not?

Despite their shitty rug-pull <https://github.com/sourcegraph/sourcegraph/pull/53345>, I do really like Sourcegraph and one doesn't (currently?!) need to be logged in to use it: https://sourcegraph.com/search and they have a handy rewrite pattern such that one can just plug the repo path into the URL for quick searching e.g. https://sourcegraph.com/github.com/JetBrains/intellij-commun...

- https://sourcegraph.com is pivoting and building a copilot application (named Cody). This is pretty good, since sourcegraph is great at understanding your code

While a readable Dockerfile can work as documentation, there are a few caveats:

* the application needs to be designed to work outside containers (so, no hardcoded URLs, ports, or paths). Also, not directly related to containers, but it's nice if it can be easily compiled in most environments and not just on the base image.

* I still need a way to notify me of updates; if the Dockerfile just wgets a binary, this doesn't help me.

* The Dockerfiles need to be easy to find. Sourcegraph's don't seem to be referenced from the documentation, I had to look through their Github repos to find https://github.com/sourcegraph/sourcegraph/tree/main/docker-... (though most are bazel scripts instead of Dockerfiles, but serve the same purpose)

We use Sourcegraph, which is a tool that searches through code in repositories. We leverage this tool in order to understand the adoption curve of our components across all of Reddit. We have a dashboard for each of the platforms to compare the inclusion of RPL components over legacy components. These insights are helpful for us to make informed decisions on how we continue to drive RPL adoption. We love seeing the green line go up and the red line go down!

SourceGraph: https://github.com/sourcegraph/sourcegraph/pulls?q=is%3Apr+a...