Viewing profile — izalutski
izalutski
HN member- Joined
- Tue, Sep 20, 2016, 10:21 AM UTC
- HN karma
- 54
- Public activity
- 32 items
- HN profile
- View on Hacker News ↗
About izalutski
No profile information was provided.
Recent public activity
-
comment
Comment #41330162
The payment processors are, at the core, specialist insurance businesses. They know how to underwrite transaction risk and counterparty risk and FX risk very well, better than gene…
-
comment
Comment #39060121
I believe that doing nothing, on purpose, especially for prolonged time (months, years), especially in solitude, is often _the_ most productive, highest leverage activity of all th…
-
comment
Comment #37398698
Yep, backwards they did (Disclosure: I'm from Digger and OpenTF so am biased) Hashi's biggest miscalculation is that they put Terraform (an open language / ecosystem) into the same…
-
comment
Comment #37089548
Yeah apologies we're in a little bubble here together with Spacelift, Scale, Env0 and Atlantis so starting to assume everyone knows the niche terminology lol Yeah so basically TACO…
-
comment
Comment #37089505
There's a fundamental difference Terraform's "server" was never open-source in the first place So you already cannot pull the move that AWS did with Elastic and Mongo The open-sour…
-
comment
Comment #37089470
Yes indeed a puzzling move from Hashicorp's leadership perspective. Could be a miscalculation; or no calculation at all. It looks like it boils down to being no longer able to "inc…
-
comment
Comment #37089284
Indeed - but the Terraform community appears to be hit the hardest. Because unlike Consul, there's no open-source hostable anything. It feels just an arbitrary restriction for a la…
-
comment
Comment #36660121
Atlantis was a great tool back in the day and still works well in most scenarios. The main issue with it is that it also takes on running the jobs (as in Terraform binary runs on t…
-
comment
Comment #36660084
All valid points! Thank you! We were initially completely backend-less; but then it increasingly became apparent that a central orchestrator is unavoidable. Rationale here: https:/…
-
comment
Comment #36657555
Yeah naming is fun The most fun thing is - Digger + Dagger could be a great combo! We haven't yet explored properly but in theory it shouldn't be anything different from adding ano…
-
comment
Comment #36656942
Thanks!! Great point; for now we're relying on S3+dynamo which many people prefer anyways; but state management is on the roadmap, we'll get to it soon Tracking here: https://githu…
-
comment
Comment #36656864
Indeed we did :) Also blogged about it: https://medium.com/@DiggerHQ/we-rewrote-our-product-in-go-fr...
-
comment
Comment #36656828
One of the founders here You could also use OIDC so no need to share keys https://docs.digger.dev/cloud-providers/authenticating-with-...
-
comment
Comment #32340093
A lot of the problem is gone after realising that productivity has little to do with efficiency and almost everything with prioritisation / focus. As soon as you become aware of yo…
- story
- story
- story
-
comment
Comment #25738211
Developers today have great tools to quickly launch small projects without thinking of infrastructure (Firebase, Vercel, Heroku). But these tools don't work for teams. Big tech com…
- story
- story
-
comment
Comment #25127054
Yes, Digger generates TF files and stores it in the dedicated "main" repository, separately for each environment. You can tweak these files directly, or override the defaults in th…
-
comment
Comment #25126177
Thanks @mz_data!
-
comment
Comment #25125474
With Heroku you are stuck with what they offer, and it quickly gets unreasonably expensive compared to AWS / GCP / Azure. Digger is just as easy to use, but you don't overpay for r…
-
comment
Comment #25125324
Copilot is great! But, it's intentionally only about ECS and a single service. Whereas Digger is operating at the entire stack level, and will support a variety of deployment targe…
- story