Do These 4 Things to Write Fewer Bugs

Поділитися
Вставка
  • Опубліковано 6 січ 2025

КОМЕНТАРІ •

  • @RafaMartinelli
    @RafaMartinelli 10 місяців тому +7

    Your videos are super valuable. You share them with humility and from your experience. Trust you’re attracting a community of like-hearted people because of that! Keep being yourself and sharing these great resources! ☺️

    • @baconandgames
      @baconandgames  10 місяців тому +1

      I don’t know what to say, Rafa. That’s one of the nicest things anyone has ever said to me. Thank you.

  • @HuangShengHong
    @HuangShengHong 10 місяців тому +3

    Depend on schedule, I don't always write clean code, but I always write (unnecessary) amount of error catching code, to a point even a spaghetti can report what's wrong with it and fallback to a bread. I'd say in my experience, debugging time can easily eat up a great portion of development time if you're not careful,.

    • @baconandgames
      @baconandgames  10 місяців тому +1

      💯 I’m with you on that. Debugging can definitely be a time suck. For me, it’s about finding a balance between over engineering your code, which can also eat time, and writing sloppy code that takes forever to clean up. The former slows you down at the beginning of the project and can mean the death of good ideas, if you can’t get off the starting block. And the latter can mean you run out of time and ship with bugs. Balance is key.

  • @timberjustinlake
    @timberjustinlake 10 місяців тому +2

    Great stuff. Refreshingly thorough and not just the usual beginner-level Godot video. Would you consider doing a deep dive about how to use the Godot profiler?

    • @baconandgames
      @baconandgames  10 місяців тому +2

      I don’t know if I have anything on hand to be able to show that off properly, but it’s a good idea. Let me think on that 🤔 I appreciate your kind words. 🙏

  • @darthnegativehunter8659
    @darthnegativehunter8659 10 місяців тому +1

    one thing that you aren't mentioning (or may have mentioned in some other video) is unit testing. both automated and interactive.
    structuring and coding the project in a way that allows it to be unit tested is one of the strong points of godot. I don't know if any other engine or framework makes it so smooth and easy to setup.
    1- Never make autoloads initiate an operation on startup.
    2- Don't make scripts that depend on parent to not crash. Maybe give errors/warnings but not fully crash.

    • @baconandgames
      @baconandgames  10 місяців тому +1

      I would honestly love to do one on unit testing but I’ve never taken the time to learn it well enough to teach it. Maybe I should brush up on that and do a video just on that. It’s such a deep subject it could probably be a whole series. Do you know of any good resources for this? I appreciate you calling this out.

    • @darthnegativehunter8659
      @darthnegativehunter8659 10 місяців тому +1

      ​@@baconandgames sadly all i have is just fromt my experience.
      for testing you can make dedicated interactive testings scenes. meant to just test smth like a character controller.
      Or a debug level.
      the scenes themselves if made modular can be tested by just running the scene.
      for automatic tests you can also use "gut". it supports things like async calls as well.
      It's also possible to make a debug ui. and add buttons to it that quickly execute.

    • @baconandgames
      @baconandgames  10 місяців тому +1

      I need to spend more time digging into this. I love the idea. Thanks for dropping the comment and for the info. I’m adding this to my list!

  • @l_gravitor
    @l_gravitor 10 місяців тому +1

    Amazing video! I'm currently working on a very intimidating project and your last video gave me the confidence to just write code and know that when something breaks I can catch it and fix it. Now with this one I have to worry even less about breaking stuff!! Keep up the good work!

    • @baconandgames
      @baconandgames  10 місяців тому +1

      What a lovely comment to wake up to. 🥹 Thank you. When you’re ready to share, I’d love to see what you’re working on!

  • @ravveni
    @ravveni 10 місяців тому +1

    i'm a huge fan of all of these strategies! "failing with style" is going to become part of my debugging lexicon!

    • @baconandgames
      @baconandgames  10 місяців тому +2

      You heard it here, folks. It's gonna be a thing 🤣

  • @moonstar_connor
    @moonstar_connor 10 місяців тому

    Solid recommendations 💪

  • @darenn-keller
    @darenn-keller 10 місяців тому

    Volume is great. 😉 Great video!

    • @baconandgames
      @baconandgames  10 місяців тому +1

      You made it to the end 🎉🥳👏👏👏
      Thanks for letting me know. Now I just have to figure out what I did differently to make sure I keep my audio levels in check 🤣

  • @puzzlinggamedev
    @puzzlinggamedev 10 місяців тому +1

    Excellent tips! I wish I could explain things so clearly in my own videos. How do you decide when to highlight something using a zoom effect?

    • @baconandgames
      @baconandgames  10 місяців тому +2

      That’s very kind of you to say 🥹 That’s a good question. I think it comes down to whether I’m showing off something specific versus whether I’m speaking conceptually.