Breakfast :)
(fried dough filled with egg and cabbage)
Bio's are hard.
| ex-JFrog
| ex-Magic Leap
| He/Him
| Homepage | https://tamir.dev |
| Github | https://github.com/tmr232 |
Tamir Bahar
@tmr232
- 255 Followers
- 348 Following
- 2.8K Posts
@davidism who needs a lockfile when you can ask an LLM to maintain your dependencies?
I'm starting to think that the only valid response to "how do you expect me to know why the code is that way? I used an LLM to generate it" is violence.
So cursed when tools that increase determinism are owned by the chaos machine companies.
Created a pre-commit hook for pinning gh-actions using Ratchet
@mistersql yeah, I'm starting to think what checkboxes I might want to check before even starting to review code. But it's trickier when there are tens of developers.
Currently thinking that the first thing to review should be the tests. Can't trust LLM code without them (it makes different mistakes than humans), and can't trust them to write decent tests (mocks! Mocks everywhere!)
But I need to sharpen my test-reviewing skills for that!
I still don't understand why "it's now far cheaper to write code" leads everyone to "so it doesn't matter if the code is an unreadable mess" and not "so we can make it really neat and clear and well-made"
If you're letting me review that an LLM wrote for you - at least have the decency to have the LLM review it for you first.
I should not be able to find trivial bugs by prompting "please review this PR".
I should not be able to find trivial bugs by prompting "please review this PR".
Neil Brown