• James LaneJames Lane, almost 5 years ago

    If there is a shit piece of code that you think could be done better, of course you can! But if you do, you've got to have an example of how you think it can be better.

    0 points
    • Account deleted almost 5 years ago

      If it's about a UI Engineer, then OK. But it seems the author (and me, personally), are more UX + designing solutions. And in such case NO, we do not even try to get into dev's work. We understand it, yeah, but we don't do it, don't try to edit it, etc. The same is the other way round - the dev gets what's to be done, analyzed, designed. Produce it, the best possible way you can produce it. Of course, you can be asked questions or asked for comments in the process but once given to produce - produce, maybe with petty questions if something is not clear, but I can't imagine useless discussions about the designer's choices. This is ridiculous.

      0 points