I find daily stand ups are completely useless because most of the useful communication can just be done by the people involved directly over email, messaging, or just talking to each other. I find it’s useful to have a whole team meeting maybe like once a week just to see where everyone is at and how different parts of the project are going. There’s very little reason to do that every single day.

haha yeah writing code while dealing with distractions is effectively impossible

it’s basically this

Because that’s how it often goes. I find there are two types of scrums in practice. First is when it goes fast, and everybody just says they’re working. There’s no time to give any detail or context so the status update is largely meaningless. Second is when people start giving details about what they’re working on, and that quickly explodes to an hour long meeting.

gpt4all has been my go to as well, this one’s neat cause it can do multimodal stuff

we need a programming horror community for stuff like this

The only one doing a gish gallop here is you. I had a very clear and simple point all along, which is that it’s not productive to perseverate over symptoms of the system. Evidently, you’re incapable of addressing this point and instead proceed to keep making straw man arguments that have nothing to do with anything I said. Apparently you think that if you keep writing walls of text that will somehow distract from the fact that you don’t have any actual counterpoint to the simple statement I made.

Seeing how you clearly need to have the last word here, I’m going to stop here so you can get it out of your system and move on with your life. Bye.

The only one struggling with “non sequitur” and “strawman” and “basic connections to underlying language” is you. Since you keep using these terms without evidently understanding them or even understanding the content of what’s being said to you. The irony here of you exhibiting generative model behavior while raging against them is quite hilarious.

None of the points you’ve listed actually address my argument, and it’s pretty clear that you’re either incapable of understanding it or intentionally avoid engaging with it. My blog in no way contradicts my online persona, but I guess that’s something you felt important to throw in as a way of ad hominem in lieu of having any actual point to make.

Cheers.

Thanks for clarifying that you utterly failed to understand what was being said to you. My point was that the actual problem is with the capitalist system itself. Stuff like Crypto, NFTs, and generative AI is not the root cause of the problems, it’s simply a symptom of an underlying problem. Getting upset over these things is a complete and utter waste of energy, and it’s utterly misguided. Let me know if you’re still having trouble understanding my point and need me to use smaller words to get it across.

Maybe the real issue is that you’re desperately trying to show how clever and cultured you are while just outing yourself as a boring pedant?

The joke is very obviously that modern software development is hellish. The fact that you couldn’t figure out a simple joke, but fancy yourself as some sort of an intellectual and an art critic is really chef’s kiss.

Hence why it’s pointless trying to have an actual discussion with people like you.

I applaud you for being able to produce content indistinguishable from a chat bot. A really clever way to illustrate why we don’t actually need LLMs.

I love it when trolls get angry and start using Latin terms to make themselves sound clever.

It’s adorable that you think you’re making the world a better place by leaving vapid angry comments on public forums.

Enjoy tilting at windmills I guess.

My point was that wasting energy raging about this stuff isn’t going to make it go away.

Good thing we never found ways to waste energy on shit like NFTs before generative models showed up.

If even a fraction of the rage AI generated content produces could be harnessed as useful energy, it could power all of humanity’s needs till the end of time.

I find a good approach to getting better at programming is to reflect on the projects you’ve done and try to identify patterns that got you into trouble. Then you can try doing things differently next time, and eventually you end up settling on a style that works for you. At the end of the day it’s really just practice. The one key thing I’ve learned to focus on is reducing the operating context I need to have when reading the code. Once the context becomes too big to keep in your head, then trouble starts. So breaking things up aggressively into small components you can reason about in isolation tends to be the best way to write reliable code you can maintain over time.