Live data from Hacker News

Ask HN: Git, JavaScript, Chrome, Redis etc. what next?

news.ycombinator.com

11–15 of 15 posts

Re: Ask HN: Git, JavaScript, Chrome, Redis etc. what next?

#12
I think continuous integration is pretty terrible compared to what it could be. The problems I see, at least with GutHub Actions and Azure DevOps:

* Generally rebuilds everything from scratch, which get slow on large projects. Reducing overbuilding requires lots of manual work. * Hard to test, often you have to push a commit. * No flakey test detection and management.

There are some companies working on productionizing Bazel-based CI systems, like BuildBuddy, but there might be other ways of approaching this problem.

Re: Ask HN: Git, JavaScript, Chrome, Redis etc. what next?

#13

Then you're not looking deep enough at problems that people have or you haven't been in the field long enough. There are tons of issues out there, and I wish I had a department full of me's who could work on all of the problems I want solutions to.

This.

I wish I were a multi-millionaire so that I could hire programmers to help me build all of the things that I believe should exist in the world!

Post reply on HN