• Jimmy HookerJimmy Hooker, almost 5 years ago

    That means they empathize, which is a pretty good sign. Could they give you read only access to their git repo? Looking at how they do things could also be pretty informative (although maybe overwhelming for a beginner). Being able to fuck with something real is really compelling. Even if you just tweak some shit and see how that affects the way things are displayed. You can then look up conventions online, and how the developers did other things, and copy-paste/tweak.

    I would definitely find some good tutorials to mess around, but also would be nice if you could dig into your actual products codebase. Here's one that looks like it has potential (I haven't tried it): https://learnreact.design

    5 points
    • Linton Ye, almost 5 years ago

      Hey Jimmy! Author of the learnreact.design course here.

      Thanks a lot for mentioning my course. I completely agree with your points above which is why I created the course in the first place.

      It'd be much easier to work with devs if a designer can speak devs' language and show them that your design is not just pixels in Sketch but actually backed by code. They'd respect your design a lot more. Also completely agree that it's really compelling to be able to dig into actual product codebase and tweak things there. As long as you learn the basics, learn how to set up things, get the project running, and have a sense of where to look at and which file to change, it'd be life-changing since you can start contributing your design into the final product without someone else's help.

      4 points
      • Account deleted almost 5 years ago

        Let's end this crap. At least a solid designer knows the basics of coding but is not to code. This is the first thing. The second - when will we start telling the devs to be more communicative, cooperative and learn the soft skills? I am fed up with this attitude that they are the ones we need to listen to and care for. If you understand coding, you create something good and you get poor communication, anger, hustle (you know, the "rush" to "let's just produce it, it doesn't need to be designed"), then whose problem is this? The designer's problem? No way!

        3 points
    • Account deleted almost 5 years ago

      Git repo? Are you talking about the UX or the UI part? I hope the UI, at least... and not a UI Designer but UI Engineer. But wait... aren't we talking about more of a UX Designer with UI?

      And one more - can I come to a dev and point a line in the code and say I object using it and he has to convince me that it should be there?

      1 point
      • 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