firelizzard

joined 2 years ago
[–] firelizzard@programming.dev 5 points 2 months ago (2 children)

In what situation are you accepting contributions that you haven't vetted thoroughly enough to detect crap code? I've seen a lot of crap from developers that's as bad or worse than LLM generated crap so there's no way I'll ever accept contributions to an important system without thoroughly vetting them unless they're from one of a very few number of people I trust implicitly.

[–] firelizzard@programming.dev 1 points 3 months ago

I’ve had success with Claude, but there’s always a layer of separation. I ask it to do something, read what it produced, and decide if it’s garbage or not. And rewrite or discard as necessary. Though counting by LOC mainly I’ve used it for writing tests.

[–] firelizzard@programming.dev 4 points 3 months ago

I didn't say never copy and paste. I'm saying when you push a commit you should understand what all the LOC in that commit do (not counting vendored dependencies). If you don't understand how something works, like crypto (not sure what Hamilton or Euler refers to in this context), ideally you would use a library. If you can't, you should still understand the code sufficiently well to be able to explain how it implements the underlying algorithm. For example if you're writing a CRC function you should be able to explain how your function implements the CRC operations, even if you don't have a clue why those operations work.

[–] firelizzard@programming.dev 0 points 3 months ago* (last edited 3 months ago)

I said you need to understand what the code you wrote (as in, LOC that git blame will blame on you) does. Not that you need to fully understand what the code it calls does. It should be pretty obvious from context that I'm referring to copy-pasting code from stack overflow or an LLM or whatever without knowing what it does.

[–] firelizzard@programming.dev 1 points 3 months ago

If you are submitting work, you should understand how the code you're submitting works. Sure, you don't have to know exactly how the code it calls works, but if you're submitting code and there's a block of code and you have no clue how that block works, that's a problem.

[–] firelizzard@programming.dev 5 points 3 months ago

There's a huge difference between copy-pasting code you don't understand and using a library with the assumption that the library does what it says on the tin. At the very least there's a clear boundary between your code and not-your-code.

[–] firelizzard@programming.dev -2 points 3 months ago (2 children)

Are you seriously trying to equate "I don't know which instructions this code is using" to "I copied code I don't understand"? Are you seriously trying to say that someone who doesn't know how to write x = a + b in assembly doesn't understand that code?

[–] firelizzard@programming.dev 25 points 3 months ago* (last edited 3 months ago) (16 children)

If you’re adding code you don’t understand to a production system you should be fired

Edit: I assumed it was obvious from context that I’m referring to copy-pasting code from stack overflow or an LLM or whatever without knowing what it does but apparently that needs to be said explicitly.

[–] firelizzard@programming.dev 2 points 3 months ago (1 children)

I guess I just don't see enough memes to have picked up on that

[–] firelizzard@programming.dev 4 points 3 months ago

Marketing. People expect to see different things on a website vs Twitter/X so the same content won't perform the same on each. So for a business it makes sense to post different things on your website vs Twitter/X.

[–] firelizzard@programming.dev 2 points 3 months ago (3 children)

I’m not sure what to tell you. I just don’t see what you do. And I never bother to look at a meme close enough to notice the kind of details the other user pointed out.

[–] firelizzard@programming.dev 6 points 3 months ago (6 children)

How can you tell?

view more: ‹ prev next ›