Hacker Newsnew | past | comments | ask | show | jobs | submit | jorisw's commentslogin

> Anthropomorphising LLMs is inevitable, but we should do it somehow responsibly.

One way would be for vendors to have the models give dry answers and less of the "That's a great question!" type response. Just keep it factual.


Rather I'd see vendors of chat bots like ChatGPT make less of an effort to appear human like. I believe this week's release of ChatGPT (or whichever new model) addresses some of that.

> Agents that consume context need agents that produce it. Once that loop is running, the organization has a written substrate it would never have produced on its own.

I'm not sure a business is helped by documentation that distilled from (hopefully present) PR descriptions and comments in JIRA, by agents. Or wherever this context is supposed to be reverse-engineered from.


I think the point they're trying to make is that context known by humans and the requirements they agree on, is 'the' bottleneck, rather than implementation

> difference between code used to implement a product and when code _is_ the product

Care to elaborate? I don't understand the difference unless you mean code that _is_ the product, being OSS code or code for license.


I think what I'm trying to get at is that there's a lot of code out there that really just needs to work. It doesn't need to scale to millions of users, it doesn't need to be abstract-able and useful to use cases we don't even know about yet, just needs to get an idea off the ground. That code is not the product. In such a case writing the code very much is a bottleneck.

If you're writing OSS code or software projects expected to be used by others that may have constraints like that, then by all means the code that gets output matters itself. But even still I'd argue that the cost of writing code manually to get there is still a bottleneck.


In my mind this is what prototyping is for. Just get it working quickly and see if the concept has legs. But be prepared to completely re-write it because the "just make it work" mindset will make it more difficult to change and improve upon in the future.

But when you factor in today's favorite business model of "make it shitty", perhaps this matters very little.


Code you ship vs tooling you use to build the code.

So, the product vs everything that is needed on the way, but isn’t the core.

CI/CD tooling, template population…. Things you write a use once/use few script for.

I typically end up with a library of tools to deal with repetitive finicky tasks.


systems vs application code

I'm picturing a splash screen announcing the feature(s) it enables, with a Download button

Thanks, I thought the forum software came custom out of YC.

Yes, it is custom.

That, and they forget they’re just one single experience in a person’s day of hundreds. The trivial part of the user’s day that the app represents, in no way warrants interruption.

Most of their managers want to be a bigger percentage of your day though.

TL;DR: Canada has an entrepreneurial self esteem problem

Compared to the US, everywhere has an entrepreneurial self esteem problem. A culture that promotes and encourages entrepreneurialism is the US’ special thing.

The Great American Dream is to start your own business and strike it rich. The Great Australian Dream is to own your house rather than rent it.


Does everyone need to have read it though, in order to understand its premise?

Surely they were at least aware of the basic premise that adding people doesn’t necessarily speed up delivery?


An analogy I saw once: can 9 women make a baby in 1 month?

In a meeting where "adding more people to speed up delivery" was exactly the topic and the reason I brought up the book, nah.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: