3 ms·
Hopefully this helps, but I’m going to just mind dump because I have a real love-hate relationship with designers and this is my therapy. Yes, learn a bit. Des
by Waterluvian 4y ago
Hopefully this helps, but I’m going to just mind dump because I have a real love-hate relationship with designers and this is my therapy.
Yes, learn a bit. Design yourself some stuff and write it. Don’t worry about how bad the code is. In fact, I hope you make mistakes in architecture so you grok how architecture decisions matter, because they will also affect what UI/UX changes are easy and what’s shockingly hard.
Save the fancy design pitches for the stakeholders. My favourite talks with designers is not when they’re selling me on a design but just casually chatting about how they got to the final plan. I learn a lot by learning your process. It demystifies things that can too easily be dismissed as silly or pointless.
Don’t make change for the sake of change. Be that brave soul who is comfortable saying “after a bunch of studies and tests (using company resources), I would make these tiny changes but honestly, it’s all pretty much fine.”
Don’t feed us design or throw it over the wall. Work with us. Understand what’s easy and what’s hard to implement. Understand why that is. Don’t always accept our reasoning (because sometimes we make arch. mistakes that really corner us on design changes being hard), but generally we have scars to explain how we know why certain things are a bad idea or whatnot.
Teach us. Talk through your thought process. Don’t fear that we might think, “wow these people are impostors, there’s no science there!” Bruh, that’s programming too. Seat of our pants half the time. Sometimes we throw out jargon to feel legit. I love hearing “I did X because in the past I’ve found that works well for that kind of data view. I did Y because the AB years suggested as such. I did Z because I just think it works.”
Uhh I think that’s it for now. Good luck on your career. It’s gonna be a lot of fun!
- theeohsees 4y agoThis is really inspiring, I really appreciate your response. Thanks for taking the time to write all this out, getting the dev perspective is really great.
- dtagames 4y agoAwesome advice here. As a dev and also design person who works with non-dev art folks all day, I'd say the more you can get down to specific exact asset files and names, the easier things will be for your devs. On the design side people work with multiple protypes and sketches in different states. But none of that ever makes it to the cold bare metal of programming. Design folks are often surprised that no visual tools are involved in actual website or software creation. Software requires exact numbers (margins, image sizes, color codes) and exact assets in specific places (on screen and on disk) to work. This means it will be as much effort for your dev to implement a "wrong" or temporary design as it will be to implement your final. Whenever you can carve out individual components or design aspects that don't change and canonize them in writing, this will help your devs. Think of their job as translating ideas and pictures into code which produces something like your pictures and you'll be easy to work with. And, have fun and keep adding the joy of your art skills to the (sometimes dreary) programming side.