|
| 1 | +--- |
| 2 | +content: |- |
| 3 | + Hi, I'm Mike with UkeTastic. I'm here again at SCNA. I'm sitting down with Jen Meyer from Relevance and she, as a, well you're a designer, you're a digital native designer and you come and you speak to technical audiences, programmers and developers and also you speak to designers. |
| 4 | + I'm sure that, or I believe that there's probably a big difference between those two audiences. What is it that you, do you see any difference when you speak to them? |
| 5 | + There's some differences and I'm definitely personally more comfortable in the techie community for lack of a better term. That's kind of where I started and that's where I feel most at home honestly. Honestly when I go speak to designers I feel a little bit kind of on the other side of things because I do spend so much time in the technical landscape. |
| 6 | + But there is. |
| 7 | + There's definitely differences. I think a lot of the designers that I know, I know a lot of people who are in the UX community which is kind of almost a subset of the larger design community and they have, they work with different mediums and some of them are product designers but it's still very interesting to be able to find the common ground in between things. It sometimes just takes a little bit more work to figure out what a designer's perspective and what medium they work in and where they're coming from and then find the common ground. You don't feel I do have to do that as much in the tech community. |
| 8 | + And I do think the designers too tend to, they have, they seem to see a larger sense of a lot of things. Not to say that tech people are narrow minded or anything like that. It's not that at all. But I think designers tend to have a very large sense of everything. And that always helps even if they're not very technical. I can kind of find some common ground in what they are passionate about and what they do and connect it to what I do and do that. And that's the main thing with designers. |
| 9 | + So in just a broader sense, do you mean that they're looking at their design and how their design interacts where maybe a developer is just like, oh, how do I make this design work with this app? |
| 10 | + I think that could be. I'm not sure exactly what it is, honestly. It's just kind of an impression that I get. And I think that designers tend to, they just really do like to have the large picture. They like to know how everything fits together. And I'm like that in that sense. |
| 11 | + Right. |
| 12 | + That's one thing that I do like to talk to developers. |
| 13 | + Right. |
| 14 | + Because it's easy to get wrapped up in little things. And details are important. |
| 15 | + Right. |
| 16 | + But it's really important for me to have larger context on things. And I think that's something I bring as a designer, having a context and knowing how things fit in. And that's the same whether you're actually doing that in a product or you're dealing with a community. |
| 17 | + Right. |
| 18 | + You have to manage those perspectives. |
| 19 | + And just to jump back, when I introduced you as a digital native, what does that mean? |
| 20 | + That's a term that I just started to coin, actually. |
| 21 | + Oh, okay. |
| 22 | + Because I haven't heard anybody else use it. But it was a way that I'm using to describe it. |
| 23 | + Right. |
| 24 | + So I think it's really important. |
| 25 | + It's a way that I'm using to describe myself. |
| 26 | + Okay. |
| 27 | + Because I am a designer. I worked as a designer in software. But I don't have a formal design background. |
| 28 | + Right. |
| 29 | + So I didn't come from a print background and then learn to do it. I learned design by learning HTML back in 2001. |
| 30 | + Right. |
| 31 | + And things like that. |
| 32 | + So you started on a computer. |
| 33 | + I started in a digital landscape. And so everything that I've learned about design theory, I've learned about design principles. But since I'm always working in a digital medium, all of those principles I've always applied digitally, not to print or things like that. |
| 34 | + And I have done some print projects. But actually, print projects are more of a struggle for me because I'm used to working in a digital thing. |
| 35 | + Yeah. |
| 36 | + So it's -- |
| 37 | + Why doesn't this resize? |
| 38 | + Exactly. I get really nervous if I make something for print. And I'm like, I can't change it afterwards. |
| 39 | + Right. |
| 40 | + Or I can't change it down the road. It's a completely different process, completely different medium. And you can do it. The principles are the same. It's just about learning that medium. And that's the thing with -- I like the idea of a digital native designer in this field because those are designers who understand how design works in this medium. |
| 41 | + Right. |
| 42 | + And they have all the specific, you know, implementations and needs and all the possibilities. |
| 43 | + Is there anything that when you go and you're talking to a technical program or audience that is -- you think is particularly hard to get across that maybe as developers we're just not quite attuned enough to some concept or idea that you see maybe as you go to one conference after another, this one just doesn't click for some reason? |
| 44 | + No, there really isn't. I have really good experiences talking to developers universally. I've talked about this topic at many conferences. And I always have developers come and talk to me. |
| 45 | + Yeah. |
| 46 | + And they ask me, like, how can I learn? And there's a lot of them that feel that they can't. But I don't think there's any one thing that would be holding -- I've never seen anything across the board that's like, no, they're not getting this. It's just a matter of not knowing where to start, really. |
| 47 | + Right. |
| 48 | + Which has nothing to do with them. It's about, you know, how we're educating people and sharing information. |
| 49 | + And that's one of the reasons in my talk I talk about how designers need to be more explicit and be more clear so that developers understand this. But mostly -- in fact, pretty much universally, all the developers that I've talked to, developers I work with, are really interested in learning these things on their own. |
| 50 | + I think the only thing holding them back is not knowing exactly where to start, which hopefully is something that I can work on helping and us other, you know, digital designers can work on putting resources out there and stuff like that. |
| 51 | + Yeah. |
| 52 | + Because we could certainly use a little bit more usability and a little bit more just -- |
| 53 | + Mm-hmm. |
| 54 | + -- make it look nice. |
| 55 | + Mm-hmm. |
| 56 | + And that is -- have you spoken -- like, Software craftsmanship North America is a -- what we call a polyglot. |
| 57 | + Mm-hmm. |
| 58 | + It's not one platform. But working in a real -- have you spoken at, like, any real specific or any -- any .NET specific or any -- any specific technology? |
| 59 | + I have spoken at specific Ruby conferences, although most Ruby conferences that I have spoken at are very open -- |
| 60 | + Yeah. |
| 61 | + -- to -- to things. |
| 62 | + Yeah. |
| 63 | + I have not spoken at anything else specific, although I have spoken at other polyglot conferences that tend toward -- more towards .NET, more towards things like that. |
| 64 | + Mm-hmm. |
| 65 | + So there's a wide range of -- |
| 66 | + Right. |
| 67 | + -- of programmers. But honestly, the same -- I -- I still have the same experiences, the same common ground of -- |
| 68 | + Yeah. |
| 69 | + -- the interest in learning at least a little bit of design. |
| 70 | + Yeah. |
| 71 | + Yeah. Well, the -- the question I was going to get at, though, before I get a little distracted as well -- |
| 72 | + Mm-hmm. |
| 73 | + -- was that there seems to be a signature style -- |
| 74 | + Mm-hmm. |
| 75 | + -- in each one of those that -- that you kind of know that a -- a -- a .NET's Microsoft platform -- |
| 76 | + Mm-hmm. |
| 77 | + -- because it's got its own design influences -- |
| 78 | + Mm-hmm. |
| 79 | + -- versus something on iOS -- |
| 80 | + Mm-hmm. |
| 81 | + -- which is, you know -- |
| 82 | + Mm-hmm. |
| 83 | + -- that it is -- |
| 84 | + Right, right. |
| 85 | + -- but -- and -- and even in the Rails community, I tend to see a -- a certain style. |
| 86 | + And now with Bootstrap -- |
| 87 | + Yeah. |
| 88 | + -- that's going to be -- |
| 89 | + Yeah. |
| 90 | + -- you know, I mean, I -- I have to admit, even on my own site -- |
| 91 | + Mm-hmm. |
| 92 | + -- it's -- it's -- it's Bootstrap -- |
| 93 | + Mm-hmm. |
| 94 | + -- because it's -- it's easy -- |
| 95 | + Right. |
| 96 | + -- and it takes me a long way. |
| 97 | + So, have you -- is that something that's -- is that something that concerns you, that |
| 98 | + maybe there's starting to be, like, this -- or -- or is that maybe a good thing that there's |
| 99 | + these signature styles that are starting to emerge for these different -- |
| 100 | + Yeah, it doesn't really concern me. |
| 101 | + Yeah. |
| 102 | + I think -- I think it's okay. |
| 103 | + I -- I -- I will stop sort of saying Bootstrap is -- |
| 104 | + -- the solution for everything. |
| 105 | + Yeah. |
| 106 | + But no, and -- and actually, I had a conversation with somebody yesterday where I was kind |
| 107 | + of making a joke, but he was describing a cir -- a situation where, like, you know, honestly, |
| 108 | + if you're in a group stance, it makes sense for you to do that. |
| 109 | + Right. |
| 110 | + So that's what I feel, that there are just different solutions for different problems. |
| 111 | + And I think as long as, you know, they're still kind of going back to that design foundation |
| 112 | + -- |
| 113 | + Right. |
| 114 | + -- or that you're still in touch with, you know, the collaborative process, and that |
| 115 | + there are still people involved in this. |
| 116 | + You're making deliberate decisions. |
| 117 | + Okay. |
| 118 | + I think that's what it really comes down to, is we have standards that we're not |
| 119 | + thinking about. |
| 120 | + And that's true for whatever discipline. |
| 121 | + Mm-hmm. |
| 122 | + It's the same thing in design -- |
| 123 | + Mm-hmm. |
| 124 | + -- and design and development. |
| 125 | + If you're just doing things unthinkingly -- |
| 126 | + Mm-hmm. |
| 127 | + -- and everybody does -- |
| 128 | + Right. |
| 129 | + -- then that's obviously probably not the best thing to do. |
| 130 | + You've got to have the animated gif. |
| 131 | + Right. |
| 132 | + Yeah. |
| 133 | + If it doesn't sparkle. |
| 134 | + Right. |
| 135 | + But there are, you know, there are some things where even if it may not be the ideal solution |
| 136 | + in every case, in some cases it makes sense to do that. |
| 137 | + Mm-hmm. |
| 138 | + In different languages, there are things that make more sense than others. |
| 139 | + So developing solutions specifically for them I don't think is a bad thing, as long as we're |
| 140 | + continuing to think deliberately about them. |
| 141 | + Well, thank you very much for sitting down. |
| 142 | + Absolutely. |
| 143 | + Thank you. |
0 commit comments