dan_manges

7 ms·

1.
RWX raises $12M as the eng bottleneck moves from writing code to validating it(rwx.com)
5 points by dan_manges 1mo ago|0 comments
2.
Now Available: Depot CI(depot.dev)
18 points by dan_manges 6mo ago|5 comments
3.
Work in Progress Commits Are a Thing of the Past(rwx.com)
1 points by dan_manges 7mo ago|0 comments
4.
What would GitHub Actions look like if you designed it today?(rwx.com)
5 points by dan_manges 8mo ago|3 comments
5.
by dan_manges 8mo ago
I've been working on this problem for the past couple of years. State of the art: - local CLI instead of git push to run - graph-based task definitions with automatic distributed execution, instead of the job/step abstraction - au
6.
by dan_manges 10mo ago
Hey! I'm one of the RWX cofounders. We don't have a self-hosted option yet, but we're interested in opening it up in the future. Our infrastructure is more complex to run than normal self-hosted runners infrastructure, due to
7.
by dan_manges 1y ago
We support anchors in our CI/CD syntax at RWX, but only in a specific `aliases` section. I think this is a nice compromise. aliases: common-env: &common-env key1: value1 key2: value2 tasks: - key: some-ta
8.
Using an MCP Server to Fix Tests That Failed on CI(rwx.com)
2 points by dan_manges 1y ago|0 comments
9.
Proposal for a New Way to Build Container Images(rwx.com)
3 points by dan_manges 1y ago|0 comments
10.
by dan_manges 1y ago
There's a difference between small scale CI and large scale CI. Small scale: a project is almost small enough to run the build and tests locally, but you still want to have a consistent environment and avoid "works on my machine&q
11.
by dan_manges 1y ago
RWX | Software Engineer | REMOTE (US) | Full-time | https://rwx.com $175K – $250K + equity We're a CI/CD platform with an entirely differentiated execution model. Rather than parallelizing jobs on VMs, we provide a ser
12.
by dan_manges 2y ago
GitHub Actions should use a lockfile for dependencies. Without it, compromised Actions propagate instantly. While it'd still be an issue even with locking, it would slow down the rollout and reduce the impact. Semver notation rather th
13.
by dan_manges 2y ago
Checksums are a good use case, where you’re not worried about any sort of forged collisions and you want to calculate the checksum as fast as possible. Although cryptographic hashes are fast enough that there likely aren’t too many use case
14.
by dan_manges 2y ago
We're solving a lot of these problems with Mint: https://rwx.com/mint Key differentiators: * Content-based caching eliminates duplicate execution – only run what's relevant based on the changes being made * Filter
15.
by dan_manges 2y ago
A new CI/CD platform. Local CLI (run without git push), remote debugger, automatic content-based caching, DAG-based definition, and dynamic tasks. It’s taken a lot of work to build it, but I’m really excited about how well it’s working
16.
by dan_manges 2y ago
I don’t understand why any of that indicates that a 70 year old couldn’t have created this, unless you think 70 year old people aren’t capable of doing that.
17.
Designing a Software Supply Chain for Security and Reliability(rwx.com)
3 points by dan_manges 2y ago|0 comments
18.
by dan_manges 2y ago
Solving those problems would be a dream. Although the interface to initiating a CI/CD run can be solved without solving those other parts. Allowing the run definitions to be passed in, and ensuring any data based on the version control
19.
Git Push to Run CI/CD Is a Terrible Developer Experience(rwx.com)
6 points by dan_manges 2y ago|5 comments
20.
The Paradigm Shift of CI/CD as a DAG of Tasks(rwx.com)
3 points by dan_manges 2y ago|1 comments
21.
Underrated Reasons to Be Thankful(dynomight.net)
2 points by dan_manges 4y ago|0 comments
22.
Separating Data and Code in Rails Architecture(medium.com)
3 points by dan_manges 8y ago|0 comments
23.
The Modular Monolith: Rails Architecture(medium.com)
1 points by dan_manges 9y ago|0 comments
24.
by dan_manges 9y ago
Root | Columbus, OH | Full-time | Onsite | $80k-$150k | https://joinroot.com Root is an auto insurance carrier, like GEICO and Progressive. We use data science to identify and insure good drivers, reducing insurance premiums for
25.
by dan_manges 9y ago
We don't right now. We're a car insurance carrier that uses our mobile app to gather data as people drive. Since all of our customers have our app installed, we haven't looked to building a web app version yet. Although we co
26.
by dan_manges 9y ago
We have a 15-person engineering team and converted our mobile app to React Native at the beginning of this year. We do not regret it. Our pace of delivery is much faster with React Native than what we were able to achieve building natively.
27.
Mounting React Native Components with Enzyme and JSDom(blog.joinroot.com)
4 points by dan_manges 9y ago|0 comments
28.
Root Engineering: We Built an Insurance Company – From Scratch(blog.joinroot.com)
1 points by dan_manges 10y ago|0 comments
29.
by dan_manges 10y ago
Root | Columbus, OH | Full-time | Onsite | https://joinroot.com Root is an auto insurance company, like GEICO and Progressive. We use data science to identify and insure good drivers, reducing insurance premiums for good drivers
30.
by dan_manges 10y ago
Root | Columbus, OH | Full-time | Onsite | https://joinroot.com Root is an auto insurance company, like GEICO and Progressive. We use data science to find and insure good drivers, rewarding good driving with the best rates. We&#

More ›