42 karma · joined March 28, 2012
If you use it with OpenAI responses api, there’s not even any need to store input items in your own DB
Atlas has problem where it just gives up and quits after a few minutes, but Claude doesn't seem to have a time limit and will work through a batch of CDP codes successfully.
Native desktop client could utilize the same stack via Electron.
Backend could start with Python using a popular all-in-one framework like Django to begin with, and scale towards micro-service architecture over time as components grow in complexity.
Heroku is a good all-in-one infrastructure service that takes care of dev-ops for the first year.
If there really was patent infringement, then it would be difficult to erase all traces. Similar to the Zenimax Oculus lawsuit where computers were erased, but the verdict still came down against Oculus.
Are they going to fragment the code-base with Java to introduce a desktop client? Are they going to hire another enterprise Java dev, who most likely isn't familiar with the rest of the stack?
The rise of Electron is fundamentally driven by the cost effectiveness of the wide availability of developers and community support.
From personal experience, my hypothesis is that in any organization, there are a handful of high impact but low cost improvements to make. These low-hanging fruits will not be blatantly obvious, and will not be discernible to someone who isn't "awesome" for whatever reason, e.g. lack of curiosity, incompetence, bad business sense, etc... In a startup with sufficient autonomy, it's probably even doable to make a lasting difference in the first week.
This is probably also tied to the idea of a 10x engineer, because they can figure out the right problems to solve and use 100% of their time to provide 1000% value.