Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

1. Generate reports nobody will read, or will feed to another LLM to pretend they read.

2. Sorta, with people taking both the accurate parts and the hallucinations as truth

3. See 1

4. Yet another regression from talking to actual humans for support

5. And small bug introductions

6. Code design (ie architecture)? Hopefully not

7. For things their creator never really loved and nobody wants

8. See 2

10. God, please no!

11. See 10

12. See 10 and 11

13. Alright



This is the thing. Many of these Ive tried successfully. You need human oversight but as of today Ive been able to consistently:

1. Debug k8s and implement niche fixes

2. Write code faster

3. Fill out a slack update template from just talking to an LLM

4. Made a system for my partner to generate the first draft of her standardized report (required for assessment)

5. Draft email responses to clients, customers, strata council, lawyers.

6. Turn docs into mermaid diagrams

7. POC new features

8. Write api integration code from a docs url

The obvious caveat is you do need to still act as QA and know what your doing.

But the general improvements, productivity gains, and new possibilities are all real. I think your (hard earned) engineer cynicism is now getting in your way.


>>God, please no!

This is the part which will be implemented for sure as soon as possible and exploited as much as possible.




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

Search: