112
The end of apis? (thelemmy.club)
submitted 5 months ago* by to c/slop@hexbear.net
33 comments fedilink hide all child comments
 

This guy posts nothing but bangers btw

https://x.com/yegor256

CTO of http://zerocracy.com/; founder of http://elegantobjects.org/; co-organizer of @iccq_ru and https://kaicode.org/

pretty sure he's serious too

Zerocracy boosts the productivity of software teams by rewarding and punishing programmers when they deserve it (programmers, not teams).

Zerocracy is non-intrusive: it doesn't tell programmers what to do, when, or how. Instead, it observes their actions and informs them when they earn or lose points.

As a manager, you can use the points earned by programmers to calculate their bonuses or even salaries. Even if you don't, the gamification alone will significantly improve team productivity and reduce turnover.

What the fuck

you are viewing a single comment's thread
view the rest of the comments
[–] 25 points 5 months ago (3 children)

Like I think that tweet is just a really bad description of an mcp? Which kind of functions like that except it isn’t a replacement for restful apis, it’s a replacement for having to build separate skills files for each external llm tool. It can be a replacement for restful apis, a lot of companies seem to be trying to push for it, but it takes a lot of engineering time and usually people are skeptical because there’s obviously going to be a cost beyond just the token usage

  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
  • [–] 21 points 5 months ago (2 children)

    The issue is that an API is kinda the foundation of everything. It's really hard to have that foundation when it could just decide not to be that foundation because one of the values in your POST request contained a text string that caused it to hallucinate.

    LLMs can only process raw text, and any version of one that can run fast enough to replace a REST api will either have to be baked into bare metal and every API update now requires months of retraining on a test suite then fabrication of new chips, or you use a general purpose one with 1000X the compute.

    This whole system still requires you to build an API that it can be tested/trained with anyways, and it will end up dispatching requests to that base API.

    Why even have the middle man at that point? Just document your API and be done with it...

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •