Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)BE
Posts
0
Comments
238
Joined
1 yr. ago

  • no-code effort

    And we know that the no-code fad was very successful in the past.

    With an infinite supply of shitty projects created by “devs” who can’t code, I’ll have a guaranteed job for ever. Thanks AI!

  • Around me, most beginners who use that don't have the skills to understand or even test what they get. They don't want to learn I guess, ChatGPT is easier.

    I recently suspected a new guy was using ChatGPT because everything seemed perfect (grammar, code formatting, classes made with design patterns, etc.) but the code was very wrong. So I did some pair programming with him and asked if we could debug his simple application. He didn't know where the debug button was.

  • You’ve said everything actually.

    1. Fork
    2. Build (and if you can’t, stop because it will be too painful)
    3. Learn the code, debug, and write at the same time
    4. Write a merge request

    That’s it. If you’re not a professional it will be longer but the steps are the same.

    The only advice would be to learn your tools, learn the IDE, learn to debug. And if there is no documentation, write it.

  • Not for junior programmers around me. They use ChatGPT and then cannot tell me what "they" wrote or why it’s wrong. They will learn nothing and I suspect it’s the same for every thing that requires some thinking and fixing your own mistakes.

    As a senior I don’t care, but I pity them.