• 0 Posts
  • 6 Comments
Joined 1 month ago
cake
Cake day: July 14th, 2026

help-circle

  • Alph4d0g@piefed.socialtolinuxmemes@lemmy.world.files
    link
    fedilink
    English
    arrow-up
    1
    ·
    17 hours ago

    My similar experience. Plan it out with clear goals and explicit behavioral tests in Gherkin. Review first.

    Often I would have thought of three of those scenarios but it gave me an additional four with edge cases and full negative scenarios. I can choose which to keep or ditch.

    Invest planning in architecture and enlist virtual or human review as appropriate.

    Ask questions like “how well does this scale?”. “Are we painting ourself in a corner?” “What if …”

    Have coding policies. Write unit tests first, make them pass and then refactor.

    Enlist another agent - even from a different vendor to code review.

    Create a pipeline that enlists tools that you trust to catch any nonsense. That pipeline can even include invoking another agent RAGged out to be hyper focused on quality.

    Human verify commits and PRs.

    At the end of the day, if you could have blasted out the same behavior with better quality then congratulations.

    If you were able to create new behaviors in .1x the time with agentic assistance and awesome quality that catches the attention of stakeholders, you might start standing out as the person getting shit done.

    Either way, your expertise is valuable.




  • Maybe it’s already been said in so many words but I bought the OnePlus One when it was released and it was kick-ass compelling hardware that happened to have Cyanogen mod. I emphasize the hardware aspect because this is a draw for many people. People were talking about it. If you get a certain percentage of the public drooling over some eye candy they might be more openness to something like a Linux phone. Of course it’s always a spectrum and some people - like many here - are more swayed by software alone and that’s awesome too.