If the system is rigged heavily against you, relying on it to affect change does feel like a losing strategy.
The fact that such a large part of the population supports literal murder could also be considered a political statement. One that would not have been expressed so strongly without what happened.
So much of this madness could be resolved with a simple income cap. Musk’s wealth grew by $1 million per minute over the past year. Who can seriously argue that this is fair and balanced?
CodeMerger: https://codemerger.nl
I've never liked the lack of control I feel using agents or tools like Cursor or Antigravity. I found myself having much better results simply pasting full source code in free chat, so I built a tool around that philosophy and I've been exclusively developing with it for a year now. It includes a Project Starter and code architecture analysis tool.
Presentable: a photo library sorter with Ai powered organization assistance, a compare canvas with various viewing modes and customizable folder sorting shortcut templates (wip).
AlwaysWhisper: a tool that let's me attach STT to my entire OS, with custom wrappers for different programs, adding theoretical voice control to any software (wip).
ScreenLoader: an Electron based tool that can load any web source as a kiosk app, full of useful features like keep-alive, covering multiple screens and tracking output logs.
Inputboard: a unified all-inputs hardware board, that transfers input data to any prototype I want to work on using an optocoupler, so I won't have to fiddle around with setting up clean and reliable inputs from cheap Chinese components every time I just want to test something.
Squire: an agentic board game helper, that can ingest a manual and will hopefully help decrease the time spent on endless discussions about seemingly conflicting rules. It should also be able to help me play a game when I don't fully understand the rules myself yet (wip).
NodeRunner: an agent that plays the WikiGame, focusing on speed, efficiency and token usage (the result of a fun competition with a colleague).
Sonic Bloom: more of an experiment than a tool. It's a wireless piece of custom hardware, that listens to conversations, sends data to an LLM through fast STT and returns a color choice that matches the topic being discussed to the hardware, which then controls an LED ring. It also has a small display that explains the logic behind the color choice.
Image-to-story: a VLM tool that kickstarts a written story using an image and has some rudimentary tools to expand on it based on user instructions (wip).
At-work-or-not: and Android app/website where colleagues can check if I'm working from home, if I'll be at the office or if I'm not working at all. Also doubles as a private record for tracking transport expenses.
SharedMaps: a Maps based website where groups of people can share custom categories of geo locations and drop comments on them.
VMG: an image format that includes audio with images and offers TTS input to easily add narration.
Who wants Coffee: a small Android app to help me remember who wants to drink what when I go for a round at the office.
And a pile of Python scripts for smaller useful tasks.
A random experiment I made a few weeks ago does something similar, but it only uses the real cursor position for now: https://2shine.nl/demo/mousemaze/
Adding a deadline to a disclosure of a vulnerability of this nature is standard practice. Every day it's not patched is a day data could be compromised. Any halfway competent lawyer should be fully aware of this.
Disclosure without a deadline WILL be ignored.
It does not matter if it's Google or your local boyscouts club, any organization requiring users to provide information that can be abused in the wrong hands takes on a responsibility to handle such data responsibly.
That sounds cumbersome and even more wasteful than my own method of simply dumping a fixed selection of project code in Gemini for each set of requests. Is there any benefit to pruning?
This is exactly how I feel about it. The cognitive load of starting a new project is so small now. It's also made it very easy to switch between projects, something that took way too much headspace to do on a whim in the before times.
We'll get to the point where we can mass moderate core knowledge eventually. We may need to hand out extra weight for verified experts and some kind of most-votes-win type logic (perhaps even comments?), but live training data updates will be a massive evolution for language models.
So "Corporate profit taxes are a game of hide-and-seek", but "you can tax the value flow, the revenue generated in-country, or the massive energy consumption of the data centers"?
The author acts as if taxes are not a completely fluid system, that will quickly adept to ensure revenue keeps flowing, squeezing wherever the squeezing is the juiciest. It does not need cautious calibration.
I use a custom tool, that basically merges all my code into a single prompt. Most of my projects are relatively small, usually maxing out at 200k tokens, so I can just dump the whole thing into Gemini Pro for every feature set I am working on. It's a more manual way of working, but it ensures full control over the code changes.
For new projects I usually just copy the llm.md from the tool itself and strip out the custom part. I might add creating it as a feature of the tool in the future.
A few days ago I tried to use AntiGravity (on default settings) and that was an awful experience. Slow, pondering, continuously making dumb mistakes, only responding to feedback with code and it took at least 3 hours (and a lot of hand holding) to end up on a broken version of what I wanted.
I gave up, tried again using my own tool and was done in half an hour. Not sure if it will work as well for other people, but it definitely does for me.
ChatGPTs implementation of Memory is terrible. It quickly fills up with useless garbage and sometimes even plain incorrect statements, that are usually only relevant to one obscure conversation I had with it months ago.
A local, project specific llm.md is absolutely something I require though. Without that, language models kept on "fixing" random things in my code that it considered to be incorrect, despite comments on those lines literally telling it to NOT CHANGE THIS LINE OR THIS COMMENT.
My llm.md is structured like this:
- Instructions for the LLM on how to use it
- Examples of a bad and a good note
- LLM editable notes on quirks in the project
It helps a lot with making an LLM understand when things are unusual for a reason.
Besides that file, I wrap every prompt in a project specific intro and outro. I use these to take care of common undesirable LLM behavior, like removing my comments.
I also tell it to use a specific format on its own comments, so I can make it automatically clean those up on the next pass, which takes care of most of the aftercare.
The tech works well enough to function as an excuse for massive layoffs. When all that is over, companies can start hiring again. Probably with a preference for employees that can demonstrate affinity with the new tools.
Most of the people that dislike genAI would have the exact same opinion if all the training data was paid for in full (whatever a fair price would be for what is essentially just reference material)
If it's really hidden in its own special tab and NEVER comes out unwanted, I can see some benefits.
It's just not a very good fit for Firefox. I assume it would run on a cloud service, which is very much a privacy issue. Especially because it appears to be something "free", making my data the product.