4 comments

  • thomasben 21 hours ago

    It made me code again.

    Before I had not enough time to gather context, be in the flow, code and test.

    Now I work throughout the day, as soon as I have 10/15 minutes I send a prompt to one of my Claude Code so they can make progress on tasks that the teams cannot undertake because too time consuming versus business needs (major migration, architecture changes, etc…)

    I love it to be able to contribute more

    • Raidion 21 hours ago

      Same. I can take on things that are nice, but not critical (yet) and make a ton of progress without bothering the devs.

  • austin-cheney 21 hours ago

    Not at all. None.

    I am in enterprise API management and gathering requirements from outside teams is the bottleneck, not writing the code. We have officially supported internal AI capabilities now and nobody is using it.

  • davismwfl a day ago

    GPT + Grok (sometimes Claude) for writing docs, policies, requirements, client responses etc. Grok is often times more concise/direct, which helps me as I tend to be verbose. I always review/edit regardless. Much faster than writing from scratch, and combining responses on the same topic is sometimes best.

    Copilot for code completion + reviews or small snippets/functions but larger code/module generation has been weak so far.

    Claude for full modules generation or complex multi-file edits.

    Research: Grok (less filtered + better search), Claude (complex dev topics), GPT (balanced but sometimes slanted and/or seems to favor certain sources).

    My Teams: Mostly Copilot for code completion/reviews, mix of GPT/Claude for code. Last year was loose/experimental to learn but we plan to formalize guidelines more this quarter.

    Definitely a ton of hype that doesn't always match reality, but it is a super powerful tool that really has made things move faster.