gojogs

Before you ask, Gyúcsány was better

I wait for the day when the employer, the management, the business analyst, and the customer can get to state expected behaviour. Nevermind using AI. On all my projects programme was never a problem, it was non-competent people going "Make it good, if it makes big bucks and line go up, don't even bother with that. Make what good? Everything.".

If you think LLMs will make irrational people go "Ahhh I get it, I can't throw money and yelling at a shower idea and be the next Xooglebookflix" you will be surprised.

I don't think anyone killed old school engineering, whatever that means for you. But if someone indeed did kill it, incompetence, management and incompetent management is the culprit

> keep that which works

you forgot the "pretend that everything works" part

misanthropic programmers say no

I've found that most of LLM generated docs are diluted and unfocused. Spending 3 paragraphs on some quirk of a library, then 2 simple examples of a command.

I write README and docs by hand, thus only important stuff goes in there. If it is not worth my attention to write down, it's not worth writing down.

Smaller context, easier to consume.

we can drop the I from AI then

How does my browser authenticate to a website/service? Can't agents have session storage to store such information?

Yes and harnesses can't provide any interface for an agent to send REST requests for example.

It's a fun project without bad intentions. Crucify someone else for using AI. Your comment serves only selfish purposes.

Hi! I've dabbled in implementing an MCP server/client back in March. To me a proper REST API and/or cli tool seems sufficient enough, agents use them with good efficiency. Any reason not to provide CLI or REST interface for your tools, but MCP for agents specifically?

yeah, except throw a tantrum and the towel in

how so?