1. X
  2. Hatchet
Log inSign up
Hatchet
238 posts
Hatchet profile banner
user avatar

Hatchet

@hatchet_dev
The orchestration engine for teams who ship. 🚀
hatchet.run
Joined February 2024
16
Following
575
Followers
AffiliatesAffiliatesRepliesRepliesMediaMedia

Log in or sign up for X

See what’s happening and join the conversation

Continue with phone
or
Log in with username or email
Terms·Privacy·Cookies·Accessibility·Ads Info·© 2026 X Corp.
  • Pinned
    user avatar
    Hatchet
    @hatchet_dev
    Aug 26
    We hold this truth to be self-evident: not all tasks are created equal. 📢‼️ Our new Slot Costs API lets tasks consume different amounts of slots on workers, which can be used as a proxy for allocating memory or weighing some runs on workers more heavily than others.
    Image
    00:00
  • user avatar
    Hatchet
    @hatchet_dev
    Aug 25
    We're really excited to unveil Hatchet Embedded, now available for TypeScript, Python, and Go! 🔥🚀 Hatchet Embedded provides a lightweight way to run a full Hatchet engine inside of your workers, useful for local development, end-to-end testing, and CI.
    Image
    GIF
  • user avatar
    Hatchet
    @hatchet_dev
    Aug 13
    🪓 Announcing support for batch tasks: easily buffer multiple payloads into a single task, configurable based on interval or max size. Batching can be an unreasonably effective strategy to increase throughput and perhaps more importantly, save 💰💰💰 on downstream APIs (*cough
    Image
    00:00
  • user avatar
    Hatchet
    @hatchet_dev
    Aug 12
    important clarifying detail: bufo is not pepe, pepe is not bufo.
    user avatar
    Alexander Belanger
    Hatchet
    @abelanger5
    Aug 12
    I'm not one for theories on software management (just hearing "scrum" makes me want to barf), but this one I feel strongly about. This is the most impactful cultural change we made on our engineering team in the past 2 years.
    Article cover image
    Article
    Your team needs an andon cord
    One of the most important engineering decisions we made this year was sending the following emoji in our company Slack channel. If you'd told me that 2 years ago, I probably would've quit on the...
  • user avatar
    Hatchet
    @hatchet_dev
    Aug 11
    Extremely niche and technical blog post incoming ✏️
    user avatar
    Alexander Belanger
    Hatchet
    @abelanger5
    Aug 11
    I've spent nearly 3 years on this problem with @hatchet_dev. From what I can tell, our approach is entirely novel and solves the drawbacks of each of these solutions (shuffle-sharding, per-tenant queues, and throttling). To frame the problem: the simplest "fair scheduler"
Advertisement
Advertisement