| ▲ | nylonstrung 3 hours ago | |
It has all the trappings of NIH syndrome. Reinventing the wheel without explaining why existing tools didn't work Creating buzzwords ("blueprints" "devboxes") for concepts that are not novel and already have common terms Yet they embrace MCP of all things as a transport layer- the one part of the common "agentic" stack that genuinely sucks and needs to be reinvented | ||
| ▲ | __float an hour ago | parent | next [-] | |
What are the common terms for those? (I have heard "devbox" across multiple companies, and I'm not in the LLM world enough to know the other parts.) | ||
| ▲ | CuriouslyC an hour ago | parent | prev | next [-] | |
I was an early MCP hater, but one thing I will say about it is that it's useful as a common interface for secure centralization. I can control auth and policy centrally via a MCP gateway in a way that would be much harder if I had to stitch together API proxies, CLIs, etc to provide capabilities. | ||
| ▲ | throwaway-aws9 2 hours ago | parent | prev [-] | |
resume driven development | ||