@timnitGebru @jonny it also reads like code if “no humans actually talked to each other or coordinated their work in any way”

As a product (and past project) manager I often tell people that the main job of real programmers is communicating with otber humans. The code is the easy part.

Deciding what the code should (and should not do) and coordinating everyone’s efforts is the hard stuff.

But also how you avoid everyone reinventing (badly) the same functionality and how you avoid crunches

@Rycaut @timnitGebru @jonny My favorite success metric isn't LOC added, but LOC removed. You can't avoid it when working in a team that similar bits of code get created concurrently, so you have to regularly unify that stuff. I enjoy being the cleanup detail.

I was told that LLMs are supposed to be good at that tracking down that stuff, but I guess somebody needs to bother to prompt it to do so?

@gunchleoc @timnitGebru @jonny it’s a good thing to track.

My favorite success metric is a two parter.

We release Friday evening to production .,,.

And the whole team has dinner at home.

(Meaning code pushes to production have become stable and routine that no one has to babysit them and no one has to stay late to resolve failures and problems)

It means both that the dev/test environments are solid & that as a team our processes are working to mean we don’t suddenly release crashes

@Rycaut @timnitGebru @jonny "It's Friday afternoon, let's push to prod"" memes coming in... 😁

I'd still release on a Tuesday, but it does make for a good metric. I like myself a bit of quality in the workplace, and I don't just mean the code.