Aperocky

10 ms·

121.
by Aperocky 6mo ago
Github is not git, git is far more robust and can be really anywhere.
122.
by Aperocky 6mo ago
At one point, it was awesome. then it became bloated. then I both found and made gateway agent for different tools that does exactly one thing - connect me to the machine and does nothing else. No, no subagents, no workflows, nothing, just
123.
by Aperocky 6mo ago
If they never learned to code, it wouldn't be very easy to build or catch the BS that AI generate.
124.
by Aperocky 6mo ago
If the team does the exact same thing, not very long. The ability to know what to build and what not to build is going to be as important as knowing how to build it. I still think engineers have an edge here. All my childhood dreams of what
125.
by Aperocky 6mo ago
Well if you do nothing you should definitely be worried, because not using LLM is rapidly becoming untenable. If you do a lot, you'll grow skeptical about some of the claims and hype, and have a sense of where this is leading to. My po
126.
by Aperocky 6mo ago
It's a strong signal in the negative direction, the best kind of signal really.
127.
by Aperocky 6mo ago
The problem that I'm trying to solve with agent is similar here, for instance, my comment likely made zero impression on you because I'm against both of the things that you are also against here.
128.
by Aperocky 6mo ago
As someone in 99th percentile in terms of token usage, it's super clear to me where the agent will not be able to replace my judgement, two areas: 1. if it exceed the context the agent does random stuff, that are often against simplici
129.
by Aperocky 6mo ago
Funny enough, I think github and communication are still a huge part of what I see. Github code itself maybe irrelevant, but is the product KISS/UNIX? Or is it an demonstration of complete lack of discipline about what "feature&qu
130.
by Aperocky 6mo ago
As an engineer, I'm never more excited about this job. My implementation speed and bug fixing my typed code to be the bottleneck - now I just think about an implementation and it then exist - As long as I thought about the structure&#x
131.
by Aperocky 6mo ago
rare case of feature bloat for git. Still completely optional, thank god linus.
132.
by Aperocky 6mo ago
REPO_NAME_0 REPO_NAME_1 REPO_NAME_2 REPO_NAME_3
133.
by Aperocky 6mo ago
With agents, my go to is now have multiple of the same repository and each agents must work on a separate one. Preventing dirty workspace by solving the co-work problem to start with. merges are much more trivial than trying to make agents
134.
by Aperocky 6mo ago
solution is simple: if bug { dont } /s
135.
by Aperocky 6mo ago
This makes sense but what if nobody get the system to the next checkpoint where the difficulty is allowed to go down?
136.
by Aperocky 6mo ago
This only works when the difficult drop rates are below miner leaving rates. Which in normal times, are something taken for granted, but once it does happen, the edge case collapse the entire system. edit: the earlier language is not exact,
137.
by Aperocky 6mo ago
This maybe one of the area that MCP are ok-ish, however at huge cost to context.
138.
by Aperocky 6mo ago
Microsoft was and still is the reason why average people needed more powerful chips lol, maybe with the exception of browser bloat.
139.
by Aperocky 6mo ago
The most common mistake that I see here is people thinking only MCP can be bound to a server and store secrets and be called remotely No, a CLI with RPC can do exactly that, just smaller. It goes lower in the exact same stack without the fl
140.
by Aperocky 6mo ago
It's like saying it is very safe and nice to drive a F150 with half ton of water on the truck bed. How about driving the same truck without that half ton of water?
141.
by Aperocky 6mo ago
The separation is being oversold as if only MCP can do it, which is laughable. Any CLI can trivially do exactly what MCP do in terms of separation.
142.
by Aperocky 6mo ago
Anything you said here just demonstrate that you don't really understand the differences between MCP and CLI. MCP is just wrapper on top of API layer that RCP to a worker/daemon. That API layer itself can be the CLI. You get no mo
143.
by Aperocky 6mo ago
You can have that with CLI. MCP is just a wrapper on top, there are no inherent differences other than complexity on top. How do you think MCP work under the hood?
144.
by Aperocky 6mo ago
Yes, but my agents also do. The whole concept of PR is that you want additional looks on the code, and multiple agents working adversarially on PRs with philosophical rules are really nice.
145.
by Aperocky 6mo ago
It does though.. you don't have agents that can connect to github or wherever your git mirrors are and comment on PRs?
146.
by Aperocky 6mo ago
You see, the actual problem is raising the money.
147.
by Aperocky 6mo ago
MCP is just CLI wrapped in boxes. CLI is the same API in more concise format. At minimum, the same amount of context overhead exist for MCP, but most of the time more because the boxes have size. CLI can be secure, AWS CLI is doing just fin
148.
by Aperocky 6mo ago
gateway agent is a thing for many months now (and I don't mean openclaw, that's grown into a disaster security wise). There are good, minimal gateway agents today that can fit in your pocket.
149.
by Aperocky 6mo ago
A CLI can just be a RPC call to a daemon, exact same pattern apply. In fact my most important CLI based skill are like this.. a CLI by itself is limited in usefulness.
150.
by Aperocky 6mo ago
Occams Razor spares none. Everything will go to the simplest and most convenient, often both, despite the resistance of the complexity lovers. Sorry MCP, you are not as simple as CLI/skill/combination, and no, you are not more sec

More ›