NatalieApr 29

I don’t really like supportive tooling for writing code. I work in vim and prefer bazel (with occasional support from a language server client for things like large scale renames).

I’m a reasonable person I swear to god. I know that’s just a preference, my coworkers who prefer IDEs or whatever are equally valid, and I try to help them where I can. If they say they can’t use generated files because they don’t autocomplete with their IDE, or if they want 4 repos instead of 1 because they can’t have multiple languages at once, I’m cool with that, really, I try to be accommodating, I try to help where I can.

Show threadNatalieApr 29

that said, my coworker who writes his code with chatgpt is just not working out for me. I mean for one thing the code is just a mess: meaningless parameters passed everywhere, error checks that can never trigger because the implementations of the interfaces don’t throw the errors that are being checked.

but the main problem is that it’s not *designed* at all. every single one of these things is like Alton Brown used to say about unitaskers. this code passes the (generated) unit tests and that’s it. trying to use it for anything that it wasn’t explicitly and specifically designed and tested for is like trying to use a pork puller bear claw when what you want is a fork.

it’s not extensible, it’s not maintainable, if you want to add a parameter or tweak an implementation detail the only reasonable call is to rewrite it from scratch.

And what’s so frustrating about that is that it LOOKS fine at a glance. It even looks fine in code review, one chunk at a time!

Show threadSnoopJ
@gnat the perfect recipe for plausibility soup 😭
Apr 29 at 11:12pmWeb