gnunicorn

9 ms·

1.
What are you looking for when reviewing LLM generated code?
4 points by gnunicorn 3mo ago|1 comments
2.
by gnunicorn 3mo ago
Interestingly, despite it being much more detailed and a lot more process and procedure than what I currently do - which is more akin to the version 0 described, but in parallel - we come up at the same final problem: reviews and quality as
3.
by gnunicorn 3mo ago
Just because everything is a potential threat vector now: doesn't this also mean you could easily put AI specific malicious instructions into the PDF that the regular human would never notice? Like the "white text between the line
4.
by gnunicorn 3mo ago
Sounds like the default k8s setup every startup deploys to not fail it single digit number of users. It learned from the best
5.
by gnunicorn 3mo ago
Yeah, same sentiment here. I agree that some more people need to be told to relax a little in our field, but on the other side, the product and project managers are constantly looking to ensure maximum utility, especially in startups and hi
6.
by gnunicorn 3mo ago
I totally see where they are coming from, jitsu, too is making every change its own artifact. And it plays hard to the "faster shipping" that especially AI-driven teams are pushing hard, and find the review process to be the next
7.
by gnunicorn 3mo ago
Odd though, isn't it? Considering it is supposedly from April already...?!?
8.
by gnunicorn 3mo ago
It was a great hack, but it was always just that: a hack. We all always knew that the "certificate authority"-hierarchy is broken and can easily be abused by the ones in power. I appreciate everything that the let's encrypt p