Looks really neat! Starred on GitHub!
If you have heard of pg-boss [1], how does sidequest compare to it? I’m about to embark on some « jobification » on some flows and I’d love to have your opinion (possibly biased, but still)!
563 karma · joined December 1, 2014
Based in Amsterdam, Netherlands
benjamin [d o t] ee
If you have heard of pg-boss [1], how does sidequest compare to it? I’m about to embark on some « jobification » on some flows and I’d love to have your opinion (possibly biased, but still)!
Two times a week, the weekly standup is extended by an hour, from 15min to 1h15.
People are welcome to jump in and out of that open zoom that acts as a water cooler corner: any topic goes, from work to personal hobbies, etc
We’re fully remote (US / EMEA / APAC)
From another fellow « pdf’er »
My point is about the need for a spec of this mechanism: without a spec, every company / org will roll out their own and result in 500 flavors of the same concept.
That’s where MCP shines: tool calling and tool discovery is already 1.5 years old (an eternity in ai land).
The MCP spec ensures that we can all focus on solving problems with tool calling rather than wasting time in cobbling together services that re not interoperable (because developed without a common spec / standard)
Many come to HN also for the comments
Excellent write-up and understanding of the current state of MCP
I’ve been waiting for someone to point it out. This is in my opinion the biggest limitation of the current spec.
What is needed is a tool invocation context that is provided at tool invocation time.
Such tool invocation context allows passing information that would allow authorizing, authentication but also tracing the original “requester”: think of it as “tool invoked on behalf of user identity”
This of course implies an upstream authnz that feeds these details and more.
If you’re interested in this topic, my email is in my bio: I’m of the architect of our multi-tenant tool calling implementation that we’ve been running in production for the past year with enterprise customers where authnz and auditability are key requirements.
We're building an enterprise platform to develop, deploy, and run AI agents at scale — from local dev to production. Founded by ex-Hortonworks, Docker, and Cloudera folks, Sema4.ai is a well-funded startup with deep infra and OSS roots.
We're looking for a fullstack engineer to join our platform team. You'll help shape the core infrastructure that powers agent-based workflows for enterprises.
Technologies we use include:
- K8s, Helm, OTel
- Node.js, React
- AWS
- Snowflake SPCS
What we're looking for:
- Strong builder mindset — pragmatic, self-driven
- Comfortable in startup environments
- Clear communicator in distributed teams
- Bonus: experience with observability / infra / developer platforms
If you're interested, reach out to ben@sema4.ai with a short intro and (ideally) your GitHub or past projects.
This is a great way to:
- Have a fail-safe / fallback in case the software does not work as intended
- Allow them to continue training the already immense dataset using real data (as opposed to synthetic data)
Returning a “Result” with union discrimination on the “success” is far superior to throwing in Typescript in my experience
{ success: false, reason: “user_already_exists” } | { success: true, data: { user_id: string }
- Throwing is not type-safe: you cannot know at build time whether you are handling all thrown errors
I've been meaning to add "intelligence" to my Telegram monitoring bot: it couldn't come at a better time!
Thank you for building it!
You can read more in the privacy policy [1]
It can also be embed in any website [2]
Disclosure: I’m the developer behind it
My understanding is that it’s more about trust (Docusign being the leader) than anything else: one can provide certificate signing and verification, but the trust in the owner of the certificate is the crux of the matter
[1] I’m the developer behind SimplePDF.eu
We will be looking to self-host: I’ll start going through your docs, thanks again!
This launch couldn’t be more timely for us:
We’re currently planning on integrating with many oauth-based apps where our end goal is to provide always valid access tokens to end customers (developers), abstracting away the complex refresh mechanism that we take care of.
Is it something we could do with Nando?
The simplified flow looks as follows:
1. Customer logins via oauth in a dedicated portal
2. We have a way to retrieve the access token at any time from Nando via an API
3. We handover that access token to our user for their own calls to the oauth-authenticated APIs
But as you pointed out, other european countries have since caught up and provide the same benefits.
They don’t see money with PWA at this point in time and therefore decided that breaking support was not a big deal.
It obviously outrages everyone on HN, but HN is not your average customer of Apple.
EU is the “important customer”, the users of PWA are “other customers”.
Using your example, you would implement tracking for that important customer (and comply 100% to the requirements as Apple did) but because of this additional bloat, the website would load 2 times slower.
After a discussion with your colleagues, you would realize that:
- Most users won’t care about the slow loading (including the important customer)
- Re-architecturing the website to keep the same level of performance while adding the necessary tracking required by the important customer would delay shipping the tracking by 1 year, past the 2 months deadline required by the important customer.
Back to your desk, you start implementing the tracking that will incur a 2x slower load time.
I imagine that if you’re on HN you are close to developers or are a developer yourself.
And if so, I imagine that you have already had an important customer (to who you cannot say “no”), completely change your plans and architecture with a new feature request while setting an aggressive deadline (ie, you don’t have time to implement everything and must make choices)
Now replace you with “Apple” and “important customer” with EU.
That's why I love HN so much: a helpful answer with a source to boot!
This description helped me put words on the type of people I enjoy working with
> To me, a 51 percenter has five core emotional skills. I’ve learned that we need to hire employees with these skills if we’re to be champions at the team sport of hospitality.They are:
1. Optimistic warmth (genuine kindness, thoughtfulness, and a sense that the glass is always at least half full)
2. Intelligence (not just “smarts” but rather an insatiable curiosity to learn for the sake of learning)
3. Work ethic (a natural tendency to do something as well as it can possibly be done)
4. Empathy (an awareness of, care for, and connection to how others feel and how your actions make others feel)
5. Self-awareness and integrity (an understanding of what makes you tick and a natural inclination to be accountable for doing the right thing with honesty and superb judgment)
[1] https://www.amazon.com/Setting-Table-Transforming-Hospitalit...
I do not have experience running it at a company level, but at a team level (I have been an engineering lead in two companies for the last 6 years).
From all the books I've read (I read a lot), this is the one that was most "spot-on" about treating other humans and making them feel valued and therefore building a team with strong bonds.
> Many of those books are selling well because they are well written and say exactly what reader thinks might work, but if you ask anyone else who worked with the author, the reality can be quite different.
Absolutely agree.
In my experience I resonate most with any books when I have already, unbeknownst to me, been applying what they preach (which has been the case with Setting the table that I'm currently in the process of finishing).
I believe that it requires a lot of introspection to be able to apply new knowledge (ie, if you haven't thought about it or experienced it before reading about it)
EDIT: formatting
- Organising the work and steering it in the right direction
- Ensuring that people work well together, help them grow, deal with "people problems"
If and when both of the above is achieved without a person holding the title "Manager", you don't need them.
This can be achieved by hiring 51%ers for example [1] and by actively monitoring the health of your organisation.
[1] https://news.ycombinator.com/item?id=39333921
[1-1] https://www.amazon.com/Setting-Table-Transforming-Hospitalit...
[*] YMMV: the hardest problem in any organisation is the "people" aspect, there's no silver bullet.
EDIT: Added the link to my other comment about 51%ers
Powered by whisper-timestamped [1] using a model trained by the local tech university TTÜ [2]
And it just… works! (with some tweaks and corrections)
For other colors, it’s in the backlog!
(I’d aiming to automatically provide the correct color by inspecting pixels within the area to redact, to make it as simple as possible)
It’s local only (the document you load and data you fill in never leave the browser) and free
Disclosure: I’m the developer behind it
Please add a donation button to allow us to thank you for your work