442 karma · joined November 10, 2016
Run the code you want to protect in a cloud function. Cache the user data on the server; modify it on the server, send the diffs to the browser.
</Naive>
<MoreNaive>
Any product that agent can generate from a prompt or reverse engineer will be cloned.
</MoreNaive>
<MostNaive>
Solve problems that make your life better even if cloned.
</MostNaive>
1. figure out how to make money by breaking government in a way no one can agree to fix
2. pay politicians to make it legal
3. run political ads claiming the other side is the villain
4. buy that island you've had your eye on
It is important not to wait for today's AI tech to get to AGI. It is better to exploit the useful things it can do today while waiting for it to get better tomorrow.
Cloning existing software might be useful today. It allows the model to
1) learn from its mistakes
2) mix known solutions (embed product A inside product B)
3) mine value (turn product A into a set of reusable libraries)
etc.
TL;DR Byd is amazing and fatally flawed. The details are too much to place here.
This is the year when solo software firms start to dominate.
Moving my head to see everything doesn't bother me. I also have a setup with 3 32" 4k which I find a little too wide but in that setup 1 monitor connects to different computer.
DeepSeek is a valuable product, but its open-source nature makes it difficult to displace larger competitors. Any advancements can be quickly adopted, and in fact, it may inadvertently strengthen these companies by highlighting weaknesses in their current strategies.
Basically, when network connectivity increases, the "bad" nodes can overwhelm the "good" nodes. The other ideas discussed are really interesting; well worth watching.
into the wallets back to the victims?
from the wallets forward to the others working with the scammer?
1) Don't ask for large / complex change. Ask for a plan but ask it to implement the plan in small steps and ask the model to test each step before starting the next.
2) For really complex steps, ask the model to write code to visualize the problem and solution.
3) If the model fails on a given step, ask it to add logging to the code, save the logs, run the tests and the review the logs to determine what went wrong. Do this repeatedly until the step works well.
4) Ask the model to look at your existing code and determine how it was designed to implement a task. Some times the model will put all of the changes in one file but your code has a cleaner design the model doesn't take into account.
I've seen other people blog about their tricks and tips. I do still see garbage results but not as high as 95%.
I wonder if we can use an LLM to deeply analyze and fix the flaws.
Basically, the user's image prompt is converted to a several prompts to generate parts of the final image in layers which are combined. The layers are still available so that edits can cleanly update one section without affecting the others.
"When tackling a task, experienced people might reflexively tell you 'this is how it should be done,' while those without experience will experiment repeatedly, think deeply about the best approach, and ultimately find a solution tailored to the actual circumstances."
I do not think that OpenAI is out of ideas, but I do believe that large businesses have difficulty overcoming the innovator's dilemma. In addition to big businesses, there are also many small and very smart companies that are using investors' over exuberance to their advantage. Nevertheless, there are enough people trying that some are likely to find a way to develop higher-quality models at a lower cost.