I love this - it's very similar to what the book Shape Up (https://basecamp.com/shapeup) calls "appetite". I've been using this method even before I came to read this book for years, it works great! Estimates otoh, really don't.
Similarly, my father had a delicate CV issue recently (he's fine now!). We were only able to do the best research on risks, best approaches, etc with the help of LLM deep research. We would be mostly flying blind-trusting the first doctor we talked to.
I was like "Have I ever actually heard that?" and the answer turns out to be "No" so now I have (it's a Metallica track about suicidal ideation, whether it's good idea to listen to it while writing Go I could not say and YMMV).
My vote is for Elixir as well, but it's not a competitor for multiple important reasons. There are some languages in that niche, although too small and immature, like Crystal, Nim. Still waiting for something better.
yeah, if the requirement is "makes it pretty straightforward to write reliable, highly concurrent services that don't rely on heavy multithreading", Elixir is a perfect match.
And even without types (which are coming and are looking good), Elixir's pattern matching is a thousands times better than the horror of Go error handling
We’re seeking a Senior Engineering Manager to lead and scale the engineering team behind Topps.com (https://topps.com), our global e-commerce platform built on Shopify. This high-impact role focuses on maintaining platform reliability, accelerating innovation, and delivering outstanding customer experiences to collectors worldwide.
[Key Responsibilities]
- Site Reliability: Ensure 24/7 uptime, performance, and scalability of Topps.com for global users.
- Product & Engineering Innovation: Lead the development of high-quality features with speed and rigor. Guide technical strategy, ensure system security and compliance, and champion engineering best practices.
- Team Leadership: Manage and grow engineers and engineering managers. Foster a culture of accountability, mentorship, and rapid iteration. Use data to guide decision-making and continuous improvement.
- Cross-Functional Collaboration: Align closely with product, design, operations, marketing, customer support, and external platform partners to drive business impact and streamline execution.
- Strategic Roadmapping: Translate business needs into a long-term technical roadmap. Balance near-term priorities with future-facing innovation.
- Platform Ownership: Own the technical health of our Shopify architecture and identify areas for optimization, extensibility, and performance improvements.
Yes, right now we're ranging from 0.75-3 seconds for the translation to start, and we're hoping to move the average time lower with our next updates. There will always be some limitation to how fast we can translate (different languages have different sentence structures and phrasing), but for livestreaming usually you'd have even a bit more wiggle room for the latency.
Also in case you're interested in the logistics of using us for livestreaming: If our current platform won't work for your use-case and you need to use OBS + a virtual camera, it's on our roadmap.
This is fantastic! Interestingly, I was one of the early engineers at Maginatics [1], a company that built exactly this in 2011 - and Netflix was one of our earliest beta customers. We strived to be both SMB3 and POSIX compatible, but leaning into SMB3 semantics. We had some pretty great optimizations that gave almost local disk performance (e.g. using file and directory leases [2], async metadata ops, data and metadata caching, etc). EFS was just coming out at that point (Azure I think also had something similar in the works).
