izalutski

7 ms·

1.
by izalutski 2y ago
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 generalist insurers, in part thanks to their scale. So these &qu
2.
by izalutski 3y ago
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 that an individual can be doing. The reason is that our subcon
3.
by izalutski 3y ago
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 bucket as Vault and Consul, which are hostab
4.
by izalutski 3y ago
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 TACOS are ci-like tools / control planes for Terraform
5.
by izalutski 3y ago
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-source part of Terraform is the CLI, the com
6.
by izalutski 3y ago
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 "incorporate the source code or embed or distribute ne
7.
by izalutski 3y ago
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 language + CLI; the terms of the licence can be viewed as
8.
by izalutski 3y ago
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 the same VM it runs). Which makes it similar to Jenkins and o
9.
by izalutski 3y ago
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://diggerdev.notion.site/Why-digger-introduces
10.
by izalutski 3y ago
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 another CI provider; we already support GitHub Action
11.
by izalutski 3y ago
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://github.com/diggerhq/digger/is
12.
by izalutski 3y ago
Indeed we did :) Also blogged about it: https://medium.com/@DiggerHQ/we-rewrote-our-product-in-go-fr...
13.
by izalutski 3y ago
One of the founders here You could also use OIDC so no need to share keys https://docs.digger.dev/cloud-providers/authenticating-with-...
14.
by izalutski 4y ago
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 your "attention flow" (what your attention span
15.
Show HN: Digger.dev – Autogenerate infrastructure for your code(digger.dev)
2 points by izalutski 5y ago|0 comments
16.
by izalutski 6y ago
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 companies that can afford dedicated platform teams tend to
17.
Show HN: Digger – get instant URLs and Terraform for your microservices on AWS(dggr.dev)
2 points by izalutski 6y ago|1 comments
18.
A better way to build on AWS(izalutski.medium.com)
2 points by izalutski 6y ago|0 comments
19.
by izalutski 6y ago
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 the templates. So unlike black-box PaaS you retain f
20.
by izalutski 6y ago
Thanks @mz_data!
21.
by izalutski 6y ago
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 resource and if you want something more custom
22.
by izalutski 6y ago
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 targets, including other AWS services, other cloud providers
23.
Show HN: A CLI to set up container environments in AWS(alpha.digger.dev)
15 points by izalutski 6y ago|8 comments
24.
Heroku experience in your AWS account. Never run out of free credits(digger.dev)
3 points by izalutski 6y ago|0 comments
25.
Digger – easy to use dev environment for entire stacks(digger.dev)
2 points by izalutski 7y ago|0 comments
26.
Junk brain food diet(medium.com)
1 points by izalutski 8y ago|0 comments
27.
Productive procrastination(medium.com)
1 points by izalutski 8y ago|0 comments
28.
Your life is a hedge fund(medium.com)
2 points by izalutski 9y ago|0 comments
29.
How to make your principles work(medium.com)
1 points by izalutski 10y ago|0 comments
30.
My path to not drinking(medium.com)
10 points by izalutski 10y ago|2 comments

More ›