• 0 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle

  • Benjaben@lemmy.worldtomemes@lemmy.worldFun fact!
    link
    fedilink
    arrow-up
    16
    ·
    4 days ago

    Thanks for that! I need more of the good lines distilled. People miss that there’s a ton of legit philosophy in the show (I mean beyond the scenes where Chidi is directly teaching of course). It’s not just a side bit to use here and there where it helps the jokes or the narrative or whatever. I really fell in love with that, like not only was the show hilarious and FULL of interesting and likeable characters, they really made it kind of a class in (or “love letter” about?) the strengths/weaknesses/clashes to different approaches to existential philosophy.

    And they did it in a way that wasn’t ham-fisted, ya know? If you already knew some, you’d pick up on it, if not, maybe you’d pick up a few tidbits here and there but otherwise, just a great show without any of that! That’s so hard to do well, idk, I’m just so impressed lol.









  • Awesome, thank you! This largely matches my own experience, I’ve found it (Claude in my case) most useful in areas where I’m weakest. I haven’t tried this scaffolding-via-comments approach though, it sounds cool.

    Any experience with Cursor or other IDEs or agents? Was co-pilot a choice or just kinda a natural default?


  • Would you mind sharing a bit more about the workflow you’re describing? I’m on a “ask people how they’re using AI to help them dev” kick.

    Sounds like you’re using an agent integrated with your IDE, would you be willing to give specifics? And you’re talking about writing some comments that describe some code you haven’t yet written, letting the AI take a stab at writing the code based on your comments, and then working from there? Did I get that right?

    Happy for literally any elaboration you feel like giving :)



  • Completely understand the frustration here. Mistakes happen, even competent people sincerely trying to do a good job can overlook things, etc. But if it’s a pattern of just copying and pasting code without really even trying to understand what it does, that’s a big problem that needs to be addressed. And frankly they should feel embarrassed if it happens more than once or twice.

    OTOH, delivering criticism in a way that winds up productive for all involved is difficult at best, and the outcome depends on the junior as much as it does the senior. What good is being right if it ultimately just alienates you from your team? Tough situation for sure, and one of the many reasons it’s so important to hire carefully (which is itself a whole huge can of worms too!).

    Can you simply ask them to walk through their submission line by line with you, explaining what it’s doing? If you’ve never asked that before it might come across as a strange request, but if you phrase it well it’s possible this causes them to notice their poor understanding without you ever seeming to point it out.