Git, JavaScript, Chrome, Redis etc. what next?

A high quality text-to-speech and/or speech-to-text program that just works out of the box

Challenge: make it require at most (1) opening a website (2) a single packet manager installation (3) a single app store installation

a good speech-to-text would help my hearing-impaired friend understand the world better

and a nice sounding text-to-speech would help me listen to Wikipedia articles

I believe there are already good AI models there that can serve as the core, but they aren't entirely developed (missing features such as "really real time" https://github.com/openai/whisper/discussions/608 and speaker separation: https://github.com/openai/whisper/discussions/264) and I haven't encountered a single good interface for them yet.

I'm also someone who are driven and get excited about working on something fundamental. My recent endeavor is the result of years to figuring out what can be the fundamentals for the web -- Building Blocks for the Internet.

It would be helpful to understand why you feel like version control (git, not github), a programming language (javascript), a browser, a database are all fundamentals? They are not the first in their respective categories, just that they all became popular? I feel like your examples also lean heavily towards developer only tools?

I get the idea you want to work on generic tools. And create a new one unlike anything that has come before? Can you name one of these "problem statements that don't have good solutions yet"?

You need to reduce your problem space. I suggest working on any real-world challenge, like climate change. You will quickly run into problems. Work on the biggest ones you can solve.

I’m assuming your post is related to open-ish source developer tools.

> It seems like all the low (and even medium, high) hanging fruit has been covered

Not at all. In software, fruit grows on top of fruit.

My personal wishlist: a desktop DB client with simple UX, tooling for DB functions, a tool for performance testing in various geographies, and a browser with symmetric encryption.

Look at the products from startups accepted into YC. Few (if any) haven't been done before and the same goes for most open source. Your goal should be to identify something that the others missed.

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.

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.

There is bleeding edge, and there is filling in holes.

Bleeding edge in software is going to be all ML now, mainly in the research of new architecture, and low level stuff to make compute faster.

As far as holes go, this is where things like Redis fall. Nothing about Redis is really that novel, its just a nice package of pretty standard functionality, which has a very common use case.

And there are A LOT of holes to be filled.

Copyright detection. All websites with user generated content will need a filter.