4 ms·
> Have you bought something that you had to scrap and build yourself anyways? Yes, but that hasn't meant it was a mistake -- 'buy-then-build' can be a great st
by nodoodles 4y ago
> Have you bought something that you had to scrap and build yourself anyways?
Yes, but that hasn't meant it was a mistake -- 'buy-then-build' can be a great strategy. Often the 'then-build' never happens, but going into a decision with the mindset readiness for 'then-build', you can learn from existing products, hit their limits and understand what is the custom version of it you'll need in your context. Recent examples are on smaller scale, though - using a library that speeds work up early, hitting its limits, and replacing or extending with DIY that does less things but goes deeper for my use case.
> What are services/products that you built and wished you had bought?
The most annoying recurring version of this has been being just a little too early - building something, then discovering a few months or years later a public product that does the same, but better. At that stage, rebuilding to use has low ROI, and one ends up maintaining a legacy monster. There was a period when public offering of supporting backend infra was maturing, ie things like secrets/configuration management, logging, observability, monitoring, a/b tests, a bit earlier even basic web frameworks (ie building anything on PHP before Laravel came out meant you built your framework first; iirc worse than the frontend framework landscape in 2022).
- jeremy_k 4y agoI 100% agree with your second point. Case in point, my previous employer built an in house development platform to create ephemeral environments and run deployment pipelines for production. At the time, around 2016, there weren't many (or any? I wasn't part of the research time) options to buy this type of software. Today, there are more than a handful in this space. I wonder at what point companies would finally bite the bullet and swap to buying? Maybe cataloging the feature set of the internal software, seeing what is a necessity, and seeing which vendors can cover those requirements?
- bruce511 4y agoTime travel, time travel, wherefore art thou time travel. When it comes to build versus buy, there are only right answers with hind-sight. >> Maybe cataloging the feature set of the internal software, seeing what is a necessity, and seeing which vendors can cover those requirements? Feature set is part of it. Longevity is another. (been relyinb on Google Reader lately?) Cost us part of it (internal is usually more expensive, but not always.) Flexibility is another - building up the knowledge and expertise helps morph the system to your needs, not the other way around. I'd say it's mostly better to buy, you'll likely get much more for much less, but it comes at a cost beyond just money. Beware of things on your critical path, to which you are beholden to outside "partners". All that said, I think developers err on the build side way more than they should.
- 411111111111111 4y ago> Today, there are more than a handful in this space. Really? I was a DevOps engineer a few years ago and can't really imagine a useful tool in that category so I'd appreciate a few names I could check out. While I've switched to frontend development, I'm still interested in CI/CD and just can't imagine any tooling being able to make it easier then what we had back then too (ephemeral envs using docker-swarm/k8s and pipeline triggers, basically)
- lukev 4y agoInfrastructure automation tools like Pulumi or AWS CDK make this relatively straightforward... just deploy a new stack (or use the APIs to automate a deploy/test/destroy cycle.) It's even possible with good old Terraform, used correctly.
- ninjha01 4y agoVercel, netlify, aws amplify, google app engine come to mind. Not sure if they’re strictly better than the setup you describe, but easier to get started.
- deathanatos 4y ago… interesting. So we went the "build-then-buy" route with Netlify. AFAICT in hindsight, what we built was more stable than Netlify, and had the same interface for devs, basically. (… and might have been operationally cheaper.) (It's all moved to an -and-buy-another-different-thing-for-no-real-reason-other-than-different-people, now.)
- jeremy_k 4y agohttps://releasehub.com/ https://releasehub.com/ (Disclaimer, first listed because I work here) https://www.quali.com/ https://www.quali.com/ https://www.withcoherence.com/ https://www.withcoherence.com/ https://webapp.io/ https://webapp.io/ https://www.uffizzi.com/ https://www.uffizzi.com/ https://www.qovery.com/ https://www.qovery.com/ https://www.devzero.io/ https://www.devzero.io/ These exist in the B2B space (and isn't an exhaustive list), there are a ton more in the B2C space
- chaos_emergent 4y agoCan you list some of the solutions that are out there now? I'm considering using one of them so I can have preview environments!
- jeremy_k 4y agoI replied to a sibling comment with a list of a few. https://news.ycombinator.com/item?id=34166459 https://news.ycombinator.com/item?id=34166459