36
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 28 Oct 2024
36 points (100.0% liked)
TechTakes
1427 readers
98 users here now
Big brain tech dude got yet another clueless take over at HackerNews etc? Here's the place to vent. Orange site, VC foolishness, all welcome.
This is not debate club. Unless it’s amusing debate.
For actually-good tech, you want our NotAwfulTech community
founded 1 year ago
MODERATORS
an idea I just had (which would need some work but talking hypothetical): wouldn't it be lovely if ~~IDEs~~ VS Code[0] automatically inserted "Copilot Used Here" start/end markers around all generated shit. could even make it a styleguide/editorconfig so it's universally set across projects[1]
[0] - because lol ofc it's mainly vscode rn
[1] - and then when you find colleagues who lie about whether they're using it you wrap all their desk shit in foil
I like the idea. Or maybe marking such changes in the commit message... I might try to bring that up when the time comes.
in the current most-typical mode of engagement, commit messages are too disconnected from the actual contents. it requires someone who gives a shit to go looking
conversely, what I mean is something like "a hook that guarantees that the moment the plugin is engaged and output from it is scribed in source, metadata about that event is simultaneously co-written"
it's already generating a pile of other things, it may as well generate timestamps and callsig and callhash and shit too....
the number one problem with this, of course, is that it's going to be extremely unpopular with a Vocal Set Of People who rely on this shit to make themselves look good