Reviewing code was also a big bottleneck. With lot more untested code where authors don't care about reviewing their own code it will take even more toll on open source maintainers. Code quality between side projects and open source projects are different. Ensuring good code quality enables long term maintenance for open source projects that have to support the feature through the years as a compatibility promise.
That's where pair programming came in but it turns out that most people hate each other so much that they'd rather work with a machine pretending to be a person.
I realize there are many levels to this claim but I'm not being sarcastic at all here.
Not really, LLMs do not push back on design decisions and will happy continue with whatever prompt you throw at them. That’s after we look past quality isssues.
It could push back more, true. Although it's role in pair programming is the driver, you are the navigator. I often begin a session with exploring and asking it questions of the code as I would a junior developer.
Not sure how to respond to this as clearly that's what I was getting at. Perhaps this is a response from an LLM though. Again, not being sarcastic, it just seems like it's maybe the case?
you make a good point and everything but have you considered the way people using LLM is similar to the way we review code together as humans? but if you think about it, they just swapped one of the humans with an LLM
Pair programming is exhausting to a lot of people, myself included. My brain just doesn't work like that. I work in fits and starts, with weird, sustained bursts of productivity.
It's exhausting to me too! But when you do it every day you get used to it. You also get a lot more done so last time I did it we would work shorter days.
I like to agree as sorta yes but also really no because it's a rubber ducky that doesn't give you the chance to come to your own conclusion and even if it does it has you questioning it.
Yeah, this. Every conversation inevitably ends with "you're absolutely right!" The number of "you're absolutely right"s per session is roughly how I measure model performance (inverse correlation).
Thanks, any idea what the “leet” Python version listed at the very top right of the first chart linked to below, which was in one of the links you provided; attempted to Google it and found nothing.
Direct link to the chart, see “133.7” Python version (elite version) in the top right:
I too wrote a similar app for my personal problem and also served to be a good way to learn about kotlin and Android ecosystem. I also tried a rewrite in flutter and compose. The idea was to use select the word and then click meaning from context menu so that meaning occurs as notification and disappears in 15 seconds. I used Wiktionary as dataset source and app works offline.
I used rewriting as a learning experience. I found flutter to be simpler with respect to UI and state management compared to using XML by default for UI. Since mine was a crud app flutter was okay. I later found jetpack compose which has flutter like UI composition and I liked it better since I can access the existing Android library ecosystem too.
