For tasks that are trivial to verify, it's ok: a code compiler will run the code written by a LLM. Or: ask a LLM to help you during the examples mapping phase of BDD, and you'll quickly be able to tell what's good and what isn't.

But for the following tasks, there is a risk: - ask a LLM to make a summary of an email your didn't read. You can't trust the result. - you're a car mechanic. You dump your thoughts to a voice recorder, and use AI to turn it into a textual structured report. You'd better tripple check the output! - you're a medical doctor, attempting to do the same trick: you'd have to be extra careful with the result!

And don't count on software testing to make AI tool robust: LLM are non deterministic.

Martin Bernklau, who has served for years as a court reporter [...] asked Microsoft Bing Copilot about himself. He found that Microsoft's AI chatbot had blamed him for crimes he had covered."

Comments URL: https://news.ycombinator.com/item?id=41550157

Points: 2

# Comments: 4

Ask me "what have you done yesterday?" and I need a few minutes to remember and sum it up. For daily scrum meetings, that's not ideal.

That's not ideal for sprint retrospectives either, or when asking my manager for a raise. Or for anything else that requires me to outline events.

I've created a system to help me with this. It isn't perfect, but it's good enough to have solved my problem, it might help other people too.

Comments URL: https://news.ycombinator.com/item?id=40954285

Points: 1

# Comments: 0

That's why I set up my own thing. I don't care about analytics at all, so I just wrote a simple build system doto generate some very basic HTML redirects.

It isn't perfect but it's very cheap to run!

https://github.com/lucienbill/lucien.run/

I once made a PR to a project I use a lot at work. The PR was about the documentation of the project, so no change to any feature, no new thing, just an improved version of the tutorial... Or so I thought. The maintainers refused my PR. My first instinct was to be upset about it, but then I thought "this might be a natural reaction because they said 'no', but maybe, just maybe I can avoid acting like a kid and use my brain". So I re-read their reply: it contained a valid reason and provided me with a good solution to my problem, I thanked them and moved on. They were just right to refuse my PR.

Linus Tech Tips made a great video about it: https://www.youtube.com/watch?v=Skry6cKyz50

- Talend API Tester: a Chrome extension to test (you probably guessed it) APIs! I can automate many things with it and use regex in my tests. If I had to do all that manually, I'd have become crazy by now. - Watir: a Ruby library that is essentially a wrapper around Selenium. Watir is easy to use, and I found Ruby very easy to learn. Also, bundler makes the process of keeping my libraries up to date really painless (when my webdriver tells my that it can't communicate with the browser because it has become outdated, a simple 'bundle install' fixes the issue)

[] Note: I don't need to do a fancy program, I just need to write some farily simple scripts that automate actions a verify a few things on web pages.

I think the real issue here is the failure of Apple to acknowledge the technical flaw. That, and the the poor customer service. If it's a design issue, it should be covered in the warranty : it would be costly on a short term perspective, but in this specific case I think it would be worth it, as it would keep customers happy with the brand.

Good news: many businesses and influencers (iFixit, Louis Rossman, Linus Tech Tips ...) are talking about it. This is bad press for Apple. The more noise we make about these issues, the better the chances are that Apple improves on its flaws.

I'm not overly optimistic about it: spreading the word about Apple's bad habits might be useless. But trying and failing is in my opinion better than not trying at all : at best, Apple makes better product ; At worst, they just keep on doing what they're doing.