• 0 Posts
  • 21 Comments
Joined 3 years ago
cake
Cake day: June 11th, 2023

help-circle
  • 5 with reasonable acceptance and use, even advocacy, for up to 1. I don’t see a difference between 4 and 5, though.

    Reviews should be the norm. Even for simple changes, a simple code change should be simple to review and approve, too. At the same time, some formatting changes or small or minimal changes with high confidence can be pushed to main without review - that’d be just wasted time and effort on the reviewer’s side. High urgency can also warrant an immediate push to main, or live hotfixing on prod if possible, with a corresponding PR still open.


  • It’s a tool that adds yet more complexity to our profession. More choice, more cost-benefit-analysis, more risk assessment, more shitty stuff to inherit and fix, more ability for shitty code producers to hide incompetence, more product and data policy analysis, more publisher trustworthyness and safety analysis, more concerns regarding what tooling sends into the cloud and what it can access and do locally, a significant “cheap and fast solution” you will be compared against requiring more communication, explanation, justification, new attack vectors to protect against, …

    My team and some others [can] use Copilot at my workplace. I haven’t had or seen significant gains. Only very selectively. Some other senior devs I trust are also skeptical/selective. We see the potential opportunities, but they’re not new solutions. Some other colleagues are more enthusiastic.

    What it does is make me question bad code from review request authors. Whether they missed it, are this unobservant, or incapable, or used AI. Quality, trustworthyness, and diligence are concerns anyway, but now I can’t really assess how much care and understanding they actually take, if they’re misled, take shortcuts, and how that changes over time - other than asking of course.

    I’m not scared for my job. It already changed the field and industry, but not in a net quality productivity gain. And will continue to in one way or another. There are many parts of and surrounding software development that it can’t do well.




  • Kissaki@programming.devtoOpensource@programming.devLutris is AI slop now
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    2
    ·
    12 days ago

    I appreciate your comment, even when many others downvote it. Honest experiences like this provide context and should always be upvoted in my eyes.

    You didn’t even make any claims about effectiveness or usefulness. Downvotes like these make me sad and make me feel like this is an unwelcoming community in general, where you can’t have open and honest discussions.





  • if I could stay later when there’s broken things in prod

    In general, or on this instance?


    Do you have team retrospectives? That’s where I would bring it up in my team. Raise my concerns, explore and understand what team consensus is around this topic, around risks, quality, etc.

    If the team consensus and/or management consensus is YOLO - then I try to protect myself from personal investment and going beyond contractual obligations. Because I already know what will come and how it will negatively affect me personally.

    It’s possible a honest discussion with management about goals and risks could lead to clarified guidelines, requirements, and goals. If it doesn’t, I’d probably be looking for a better job/environment. Because I’ll be miserable if colleagues YOLO, no matter how careful I am personally.



  • Some people are more receptive to these kinds of things than others. Not only in terms of open mind but also how they are able to apply it (or capable of applying it?).

    I wish agreeing on intentions and improvements in terms of scoping and description would be met. Same with unnecessary, obvious issues showing up costing review time and iterations. I just don’t get how these are issues - but they are - for or with some people.


  • I never thought I would move away from FOSS/AGPL by default. The more I read about this issue, the more I consider providing free services instead of FOSSing. It’s a shame.

    FOSS is still important and necessary to a degree, for auditability and self-hostability, very important for security and control, even as a conscious/careful user.

    Maybe this puts us more towards “pay to free the code” or something, so there is at least some compensation. Won’t make verbatim regenerated AGPL to MIT any less hurtful though.

    If you publish a free service, at least they’re not feeding from your code too.

    Tragic.