[-] tatterdemalion@programming.dev 1 points 2 months ago

What do you mean?

[-] tatterdemalion@programming.dev 1 points 2 months ago

What good role models do we have for today's youth? I feel like they're all on YouTube watching braindead slop or chauvinistic rich douchebags.

[-] tatterdemalion@programming.dev 1 points 3 months ago

Thanks this is very interesting! I also found an extension called WEBCAT that does a similar thing.

[-] tatterdemalion@programming.dev 1 points 3 months ago

or audit the frontend code your server is serving against the trusted version.

OK but that requires everyone to be a vigilant user. It's much easier for users to just install the software themselves and verify the checksum matches.

[-] tatterdemalion@programming.dev 1 points 3 months ago

That's exactly what I'm proposing. The code that runs on the client needs to be open source and verifiable. That is not currently possible for code delivered by a web server using today's web standards AFAIK, which is why I'm reaching for the browser extension.

[-] tatterdemalion@programming.dev 1 points 3 months ago

PBKDF2 is exactly what I'm using right now. The other reason for the extension is to prevent the host from ever having access to the key or the plaintext content. Sure, if you trust the host, the web code could be written to never send plaintext content back to the server. But I'm trying to eliminate that kind of trust requirement.

[-] tatterdemalion@programming.dev 1 points 3 months ago

And by the fact of the longest part of programming being digesting code you didn’t write, in effect you’ve taken a long-cut and could have written it yourself faster.

The conclusion doesn't follow from the premise. Just because an LLM may need to tweak something doesn't mean it necessarily would have been faster to do it manually. Humans need to tweak things all the time, it's called revising, and it's an important part of improving code.

But I wouldn't claim that using LLMs is always faster than coding manually, nor the opposite. There are times when LLMs do slow me down. It's important to recognize when that risk is high.

But I'm quite certain that for prototyping specifically, i.e. building a desired UX to get a feel for it and experiment with whether the ideas are sound, LLMs are faster.

So you don’t get a valid answer, you just get a convincing one.

That's why you shouldn't trust an LLM's reasoning; it doesn't actually have sound reasoning abilities. You shouldn't rely on an LLM to reason about problems, you should use it to generate code quickly when the reasoning has either already been done by a human and/or it exists in its training set. LLMs are closer to a search engine than a problem solver.

When asking the person why they did it...

I see no reason why this process is mutually exclusive with using an LLM. You can use both human reasoning and LLM code generation.

No disagreement from me about trivial changes. I make them in my editor all the time, assuming I even have an editor in front of me. Sometimes I don't, and it's possible to use dictation to an LLM to make trivial changes without touching a keyboard.

That means that reviews of LLM outputted code by their nature are either invalid and/or non-optimal.

Not convincing. I've given my reasons

[-] tatterdemalion@programming.dev 1 points 2 years ago* (last edited 2 years ago)

Do you not do demo meetings after introducing entirely new features?

Sure but it's rare that a single PR introduces anything but a small slice of a feature, and the demo is usually something that can just be recorded in under a minute and sent over chat. The PR reviewer is likely to try building and using the new functionality too.

And if it’s an internal tool/service for fellow devs to use to make their lives easier, yes, it likely deserves a meeting so the devs can have a chance to QnA about it.

Just document the tool or service. That must exist anyway if it's going to be used by many people. And we're not really talking about a PR review at this point, we're talking about an internal release ceremony, which may involve parties that are not going to look at the PR.

If you create a new tool like that abd then just hand it off with all the devs have to go on being “here’s the manual, figure it out” you know what happens?

Almost no one reads it, and pretty much no one uses it

You're still straying from the topic of conversation: PR review process. But regardless... If no one uses it then it's probably not useful. Why did you build something that didn't compel people to use it from a one-paragraph internal PSA?

[-] tatterdemalion@programming.dev 1 points 2 years ago

It's surprising how Github is sorely lacking in git features and even encourages bad practices.

  1. There is only a linear history view of commits without any child/parent relationships visualized. I have coworkers that tell me it's annoying how I use merge commits because they just see a big list of small commits in the history, and they'd rather see one commit per PR. Well... I sympathize, but also, fuck that! I'm not squashing my carefully crafted commits because Github has a shitty UI. Use git log --first-parent or something like lazygit. It's sad that many open source projects have adopted a "squash and merge" mantra for PRs. All of the merge methods have a valid use case, but people are so beholden to the damned Github history view.

  2. PRs have no concept of what a patch is. If you rebase, the entire history disappears. Reviewers cannot see changes made to individual patches unless they are applied first in new commits and then manually squashed into old patches after the review is done. Phabricator does this better IMO; each patch has its own history. I've even heard devs at other companies tell me they never make PRs bigger than 100 LOC. That just seems like a huge waste of time to me, unless you have some special tools to support that bizarre workflow.

  3. Merge queues only support a single merge method, one of merge commit, rebase, or squash. So we just don't use this desirable feature because of this limitation.

[-] tatterdemalion@programming.dev 1 points 2 years ago

Book a night at Trump Tower.

[-] tatterdemalion@programming.dev 1 points 3 years ago

I mean... they carried the bags out of the store by themselves.

[-] tatterdemalion@programming.dev 1 points 3 years ago

Revocation and Kelly Clarkson

view more: ‹ prev next ›

tatterdemalion

0 post score
0 comment score
joined 3 years ago