Retired CEO of my local crack house. Retarded and zero hoes
Joined January 2019
- Tweets22.4K
- Following1.8K
- Followers676
- Likes52.9K
Meronix retweeted
Here is Proton CTO's AI manifesto, that I obtained multiple copies of 404media.co/manifestos-fear-…
Meronix retweeted
Software around me is not improving nor is it expanding.
If AI drastically lower the cost of software… then we have a mystery, don’t we?
The answer is that building the software was never the difficult part in these cases. Our organizations have been optimized for process, meetings, and risk avoidance instead of shipping working systems. It is institutional decay: layers of people whose main job is to prevent other people from doing the work.
Meronix retweeted
Caring is the moat, you should feel visceral pain when things are bad or broken and stop at nothing to fix them
Meronix retweeted
to all my followers who believe in this, sincerely - it's bullshit.
this is an era of unprecedented technology and with it comes unknown challenges, it is like a new world map in a game where only paid promotional beta testers have been before.
what is the value of discovering a counterfactual now when people have stopped reading everything?
how reliable is this tech where you chat with a bot and it hallucinates 3 times a day but you never know on what? what is the cost of discovering such bugs late for your projects?
what is the cost of discovering problems/bugs when entire world is wearing the same glasses and everyone has same blindspots?
"there is no technical moat" - yeah, for you.
ofc you would think that if you are someone who has always just wanted to get by their day and do nothing beyond what is forced on you, then yeah, sure.
but if you tell a guy like me "everyone is offloading to the same machine to think, using the same overabstracted superficially verified systems, where agentic PR count is a porn to be consumed by those who think they are doing something". if you tell a guy like me that, i would say there is now an opportunity to be hercules amongst men. there is an opportunity to really use this tech around you to imitate what fabrice bellard could have pulled off in your niche if he cared as much as you.
there is an insane opportunity to be unlimited, your moat is starting your morning where others have stopped caring about something.
Some thoughts i have with regards to crypto and cyber security risk:
Blockchains have open source codebases that can be used to do in depth vulnerability research. Pair that with the huge pay off that is associated with actually finding a vulberability 1/9
high payoff targets that had probably intensive resources dedicated to finding critical vulnerabilities. But AI has demonstrated that they are able to find more complex attack vectors than humans and this is why the possibility of finding a critical exploit with AI 8/9
the only 2 bull cases for crypto
1. A rogue agent swarm hacks every major bank and buys crypto with the money
2. A rogue agents swarm moves all the money to high yield accounts which bankrupts banks and sends BTC to infinity
Bear case the same just reverse what gets hacked
Meronix retweeted
How have software engineering fundamentals changed with agentic coding? Here is our AI Engineering Skills map for software engineering fundamentals.
Meronix retweeted
1. Reduce the size of the task you hand over to an agent. Don't give it large swaths of tasks unsupervised if you don't have a codebase pattern the agent cannot continually reference as a source of truth. This applies heavily to monorepos, microservices with a structure org-wide, template repos, etc. While agents can one-shot, quality reduces with time and lack of human intervention in-between huge swaths of work causes rotten output. Which leads me to:
2. Decide when you bring humans into the loop: You don't have to review every PR. Have another agent decide the blast radius of the PR. You can have a workflow that deterministically generates a blast radius and use AI to drill deeper). The blast radius should determine whether a PR review agent is good enough for a merge into prod or requires HITL.
3. Scoped agents.md files. One giant agents.md file is a recipe for disaster. Keep the files scoped. Put instructions affecting a specific part of the codebase in that folder alone. Don't dump everything in the root agents.md file.
4. Let your skills mirror your working pattern, don't blindly copy skills. Skills should evolve from the way the team works and what has been proven to be successful. Copy-pasting skills into a codebase is a highway to hell. It is either too verbose and burns tokens, focuses on the wrong metrics for success, or too minimal and wastes tokens by doing nothing to help. Let team members write the skills, feel free to read externally packaged skills and adapt what works for you.
5. Self-improve. When the agent produces slop, don't yet fix the code, fix the instructions, the skills, the agents.md file, your factory. Fix it there. Then fix your code. Your skills and agents.md file MUST evolve with your review process. It must not be static.
There are a few more and I'd love to share but typing is hard. This will solve 80% of your problems. The remaining 10% is for me 😉 and the last 10% is for the black box of AI we haven't solved.
If you do not think that by some magical alignment of the universe BTC is gonna trade at 500k in 3 years i think the risk to reward of holding it is not worth it
