Disclaimer: I work at Anthropic but these views are my own.
51 karma · joined April 23, 2020
Disclaimer: I work at Anthropic but these views are my own.
Sometimes it’s preferable to pay the professionals, especially if you’re not an expert. I’ve recommended LastPass to my grandparents for years because it’s better than using their grandkids’ names as passwords everywhere.
But I love the story. Clever use of time dilation.
I don’t know if there’s a way for the author to disable that. But I think it’s a valid part of the metagame to use that information when guessing. Kinda like how the top geoguessr players use camera artifacts to deduce where the photo was taken.
If so could you use steganography to encode a unique ID into the icon itself, then read it back to retrieve the fingerprint.
GitHub Actions is like a better version of CircleCI. They really cloned a lot of it and improved it. Similar config YAML, similar UI. The points in the CircleCI article largely hold, except for the free mode: GHA does have local runners that are very similar to Conducto's local agent.
Jenkins comment coming shortly.
Okay. From my quick reading, BuildBot is a nice way to run your tests in parallel. It also has Jenkins-like dependencies, where a successful build can trigger another build.
In Conducto, these parallel and serial steps aren't broken apart, they are combined into a single tree. The tree lets you compose these steps to do bigger and more sophisticated tasks, all within a single build. Check out https://medium.com/conducto/cant-teach-an-old-dag-new-tricks... for more details.
This makes it easy to chain together steps like "Build my artifacts", then "Test them", then "Deploy my app", where each of the steps has more detail.
Also, Conducto has a big focus on debugging that I don't see in BuildBot. In my experience, debugging new features is a major productivity bottleneck for developers, and we built Conducto to make it easy to reproduce errors and solve them quickly, even in long-running pipelines.
I'll keep reading, these are my first thoughts.
* CI/CD in Python, not YAML: simple and powerful way to define CI/CD pipelines that is understood by IDEs
* Trees not DAGs: DAGs are messy. If you've ever traced a node's dependencies in a medium-sized CircleCI project (speaking from experience here) you know how frustrating it is to search through a 2000-line YAML file. Trees help your pipelines stay simple as you grow, and they're much more useful to look at.
* Free mode that doesn't suck: Run pipelines on your laptop for free, forever, for you and as many teammates as you want. When you need more scale you can run hundreds of tasks simultaneously in the Conducto cloud.
We're launching today, and I'd like to invite you all to check it out. I want feedback as much as I want users, so please look at it and let me know what you think.