Live data from Hacker News

I think I need to go lie down

twitter.com

141–150 of 475 posts

Re: I think I need to go lie down

#141
hey I'm Lu from tldraw, I worked on some of this.

The point of this demo is to experiment with new ways of interacting with an LLM. I'm very tired of typing into text boxes, when a quick scribble, or "back-of-the-envelope" drawing would communicate my thoughts better.

It worked a lot better than I expected! If you give it a try, let me know how it goes for you! And please feel free to check out the source code: https://github.com/tldraw/draw-a-ui/

Re: I think I need to go lie down

#142

Earlier quoted context omitted.

While I've had similar notions throughout my life, they have their own host of problems, yeah?

Nothing is truly perfect. Maybe in 5-10 years we'll have massive 3D printers that can build you any house without needing a big construction crew. I doubt but if you asked me 5 years ago about AI being capable of replacing me, I'd have laughed in your face... Alas, here we are.

Not replacing, augmenting. Try to find ways to use the new tools to become more productive than other engineers. Help evolve integration and deployment frameworks to handle the snippets from LLMs in the context of larger projects with a minimum of glue.

I wouldn't be surprised to see some old ideas come back to life like encapsulation concepts from enterprise software development. But this time we let LLMs deal with the boilerplate code needed to use and connect them.

Re: I think I need to go lie down

#144
post #84

I was discussing with a client how to integrate our software with his. He sent me a screenshot of the main form. I put the screenshot into ChatGPT and said “make a react form like this in bootstrap”. Made some adjustments, added my software, a few hours later showed the client who was knocked out to see a proof of concept of our systems integrated so quickly. When doing web development I often take a screenshot of a…

Yes, the customer will be impressed by your speed the first time. The second time, he will expect it. The third time, when requirements have grown enough to be beyond what ChatGPT can deal with, he'll be angry that timescales have exploded.

> The third time, when requirements have grown enough to be beyond what ChatGPT can deal with, he'll be angry that timescales have exploded.

Or worse, they'll feel they've been scammed, and that you're a fraud.

AI or not it's not a good strategy, in life and in business, to lie regarding on what you can actually do/deliver.

Re: I think I need to go lie down

#146

Earlier quoted context omitted.

It’s a lot better as it lets you see the replies / thread which xitter has stopped showing and does not drive engagement it.

> xitter has stopped showing and does not drive engagement. In the specific case in Xitter, I perceive that as a good change. I like seeing what was linked to, without otherwise getting engaged there.

Using nitter is the part which avoids engagement-ing with xitter.

Not having any context is the part which makes links to xitter useless, most of the time you get a link to a reply but without context it’s difficult to impossible to understand what it’s about, and the link is functionally useless.

Re: I think I need to go lie down

#147

I was discussing with a client how to integrate our software with his. He sent me a screenshot of the main form. I put the screenshot into ChatGPT and said “make a react form like this in bootstrap”. Made some adjustments, added my software, a few hours later showed the client who was knocked out to see a proof of concept of our systems integrated so quickly. When doing web development I often take a screenshot of a…

But the thing is, creating a basic form page -is- simple. What is so amazing, is that after ~25 years of web development, we have continued to make it more complicated than it should be, by continuously coming up with new web frameworks that are brilliant for all kind of fancy use cases but overcomplicated for the more common and basic tasks. Yes, there have been exceptions every now and then, but most web devs don't…

Basic "fill out the fields then submit" forms are simple. But many use cases these days want intakes or onboardings like apps, then complain about complexity or timelines when they fail to realize the requirements spawned 45,000 branching paths.
Post reply on HN