[Sugar-devel] Requesting the 2nd Feedback, made changes after getting the feedback.

[Chihurumnaya Ibiam]

I couldn't look at it properly at the time, that's why I sent that.

I just noticed you used the Music Blocks logo, I'm wondering why.
If you want to use a Logo, at least use just the Sugar Labs logo as this
project isn't for Music Blocks.

*"suitable for youth"*
We want the responses to be suitable for kids.


*Task: Install the Sugar desktop environment and fork the Pippy repository
from Sugar Labs’ GitHub.*
This is stating the obvious, which is why the project idea mentions it.

You've also said the model you intend to use runs offline, does that mean
you intend to bundle it
with the activity?
You've mentioned integrating an API based approach if local performance
lags, how do you intend
to measure this lag?

*Error Detection: Run the code through Python’s exec() in a sandboxed
environment, capturing errors via traceback. For static analysis, parse the
code with the ast module to identify potential issues (e.g., undefined
variables, infinite loops, or logic errors)*

Pippy can execute code, do you intend to still use exec in a sandbox?

*"Use the LLM to ask leading questions"*

If I understand correctly, in the context this was used, this seems like
you're

thinking about how you'd use the debugger, not how a child would use the
debugger,

remember it's supposed to guide the child.

*Handle common beginner errors:*

The things you've listed in the above section seem like cases you intend to
particular

implement in the debugger, is that the case?

*Avoid technical terms (e.g., say “mix-up” instead of “exception”)*

I agree about using simpler terms, but I don't think the necessary terms
should be avoided,

I think they should be stated where they need to be stated, of course
something else can be

used in its place, but they should be stated.

*Cache frequent error responses (e.g., missing colons) in a local
dictionary to reduce LLM calls.*

We usually use sugar-datastore to store data that's needed by an activity,
this data doesn't persist across activity

instances except you want it to, is that what you're thinking about here?


Hope this helps!

-- 

Ibiam Chihurumnaya
ibiamchihurumnaya at gmail.com




On Thu, Apr 3, 2025 at 7:35 PM Anurag Mishra <anuragmishra0521 at gmail.com>
wrote:

> Is that all the feedback you have for me? I’ve removed that section to
> keep the focus on my contributions rather than personal details.
>
> I appreciate your insights! Could you share any other areas where I can
> further improve?
> Regards
> Anurag Mishra
>
> On Thu, Apr 3, 2025, 9:09 PM Chihurumnaya Ibiam <
> ibiamchihurumnaya at gmail.com> wrote:
>
>> Programming Languages: JavaScript, TypeScript, C++, Python, C, Java Libraries/Frameworks:
>> React, Sass, BootStrap, TailwindCSS, Node.js, ExpressJs, Django, NextJs,
>> Rust
>>
>> Databases: MongoDB, PostgreSQL
>>
>> Tools/Platforms: Git, GitHub, Vercel, AWS, VS Code, Postman, Docker,
>> MATLAB
>>
>>
>> This section has little to do with the project, I don't see why it's
>> there tbh.
>>
>>
>>
>>
>> --
>>
>> Ibiam Chihurumnaya
>> ibiamchihurumnaya at gmail.com
>>
>>
>>
>>
>> On Wed, Apr 2, 2025 at 7:31 PM Anurag Mishra <anuragmishra0521 at gmail.com>
>> wrote:
>>
>>> Dear Sugar Labs Community,
>>> Thank you for the opportunity to refine my Pippy Debugger proposal!
>>> Based on feedback about enhancing the UX and expanding the debugging scope,
>>> I’ve made some exciting updates. Here’s what’s changed:
>>> 1. Enhanced UX for the Debugger Panel
>>>
>>>    - Original: A basic side panel with LLM suggestions.
>>>    - Updated: The “Debug with Helper” button now opens a dynamic side
>>>    panel that:
>>>    - Highlights the error line (e.g., for i in range(3) missing a
>>>       colon).
>>>       - Shows a chat-style LLM tip (e.g., “Oops! Your for needs a :—can
>>>       you spot it?”).
>>>       - Offers interactive buttons: “Hint,” “Example,” and “Tell Me
>>>       More” for deeper guidance.
>>>       - Updates as the user revises code, styled in Sugar’s bright,
>>>       kid-friendly aesthetic.
>>>       - Why: This makes debugging engaging and intuitive, letting kids
>>>    explore at their pace. I’ve attached a mockup (Pippy_Debugger_Mockup.png)
>>>    to visualize it!
>>>
>>> 2. Broader Debugging Scope: Flow and Logic
>>>
>>>    - Original: Focused mainly on syntax errors.
>>>    - Updated: Now handles program flow and logic too:
>>>    - Uses ast to spot flow issues (e.g., infinite loops: “This while
>>>       never stops—how can we end it?”).
>>>       - Probes logic errors (e.g., “You wanted 10, but it prints
>>>       5—check range(5)!”).
>>>       - Combines code and output for context-aware tips.
>>>       - Why: Beginners struggle with more than syntax, so this ensures
>>>    well-rounded support.
>>>
>>> 3. Teaching Debugging Strategies
>>>
>>>    - Original: Gave hints but didn’t teach methods.
>>>    - Updated: The LLM now suggests techniques:
>>>    - “Try print(i) here to see what’s happening!”
>>>       - “Test just the loop—comment out the rest.”
>>>       - “What did you expect? Let’s check!”
>>>       - Progressive hints escalate from vague to specific.
>>>       - Why: This builds debugging skills, not just fixes, aligning
>>>    with Sugar’s educational goals.
>>>
>>> These updates make the debugger a true learning companion. I’d still
>>> love your thoughts on the panel’s usability, the flow/logic approach, and
>>> strategy guidance. Updated draft is attached/linked:
>>> https://docs.google.com/document/d/1kDaOTUjNIghWLVJUuLWUtLNLC9XB3hWYoDoOO_kWGV4/edit?tab=t.0#heading=h.7ajmtdnyhjmz.
>>> I’ll hop on #sugar IRC soon to chat more. Thanks again!
>>> Best,
>>> Anurag Mishra
>>> _______________________________________________
>>> Sugar-devel mailing list
>>> Sugar-devel at lists.sugarlabs.org
>>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20250404/d985c486/attachment-0001.htm>