I am only 15 minutes into this discussion (and 30 years into my design engineering career) but had to pause to thank you guys for this video. It is a Saturday morning and I just KNOW the rest of the chat is going to be inspirational. Right, ... back to watch the rest! 🙂👍
Yup, inspirational. I've loved moving from coding to design (and coding) as great digital products are only great if people like to use them. Thanks for some great perspectives Mariana.
@@rickatfidrasoft1879 hi, im actually a designer but currently im more interested to learned coding. can you give me some advices? oh ya im still 17ys btw so ya im happy to learn new things XD
omg i didn’t realise it was her because im so used to her twitter profile picture. omg that’s MOTHER!!!! also this podcast is the best thing on the planet for me rn. THANK YOU!
I love that the push for designers to code is more common to talk about nowadays. I started out as a UX Designer but wanted to learn how to bring my ideas to life. I started out using no-code tools like Webflow and eventually made the dive into coding. A certain feeling arises when you see your idea implemented/know the technicalities that go into implementation. Now that I've been building things, it's been a slow/steady journey and I'm glad I decided to go in. I appreciate that you post content like this :)
Another inspiring episode! It's great to see more designers pushing the narrative that coding is part of creative growth. Love where design career is headed.
Big time agree that even the best Figma prototype still has a certain level of abstraction from the real experience. I wish Figma was more focused on improving / removing this level of abstraction by enabling designers to build and launch more realistic experiences directly within the browser. They seem to be more focused on building AI tools to replace designers / enable anyone to be a designer than they are concerned with improving their prototyping tools. For instance, users still can't even type within a text field or fill out forms naturally. Figma is still a far ways off from enabling designers to create truly realistic prototypes.
So much insight here - this is exactly the type of deep-dive interview I was looking for, on an under-addressed topic! The “ah-ha” moments you both described in the design-dev journey are spot on (as someone going through it myself, also on my 3rd or 4th attempt). Having the idea of a real app to design and build from 0 to 1 has changed my whole mindset while slogging through JS. Ridd, you asked a question about design engineering becoming more “mainstream” now - do you think this is still a strong differentiator for designers to have? Is it just a matter of time before this becomes the norm? Or maybe it’s more nuanced where everyone will have their own specialization, and it’s a matter of communicating that to prospective employers/clients?
Thanks for sharing this! I love the advice on importance of sharing of work online. Actually this one this quite challenging wanna try to do cross post by Linkedin and X
This was both validating and incredibly inspiring. Still marinating my thoughts on this, but, in short, now it feels like "design tools" ended up becoming some sort of detour. Coming from a hybrid design+code journey, I always got the feeling that tools like Figma what they were really trying to achieve was to become a graphical code editor.
great episode! i wonder what these new role 'design engineers' do when they are faced with scaling. i can definitely see a ux engineer working on making the interactions tight or designing components. but what about when you're faced with more complicated things like fast loading tables, or customizable forms like formly? and any of those third party ui components that may not exactly fit with your typical design/engineering workflow? do you use them? or is that relegated to more senior full stack engineers to implement those? asking from a large scale saas point of view, because i can personally code and style things like isolated components, but not implement 3rd party systems that interact with data on the backend as much - but those can still highly effect UI
Marina do you have Financial Aid for your Engineeering 101 Course?
4 місяці тому+2
Design engineer is an interesting role I just started hearing in the last months . The definition is not clear to me, is it a designer that an create components in react/swift something else?
It's a tough one to nail down which is why I'm kind of trying. Some report to design and others report to engineering. Often it's a bridge role between the two (i.e. creating all of the frontend code that hooks up to the data and API calls that traditional engineers are creating). Other times (like in Mariana's case) it's closer to a "designer who can code" like the original Notion hires.
It's very fluid at the moment. I think this is expected with a unique strength on top, like if you are good with 3d or shaders or anything else which can take the level of craft to next level. And I believe design engineers steer away from the norm and acquire these skills organically, which is driven by pure curiosity
I recently did a map that tries to define the scope and competencies required for a Design Engineering role. Although as mentioned it really depends on the company and the context. I did it because I wanted to clarify myself about what this role need to cover in order to learn it. I can provide the link maybe is helpful. Great interview!
crafting and building software can be - and is becoming - an aspect of the (product) design work, but certainly not its totality. to me, the this upcoming design engineer role is a call out for front-end developers who dont care for user experience/interface design and for designers that live too much in the figma file and dont talk to developers. it means that the bar has raised and the so called handoff process is going to require much more attention and interdisciplinary knowledge on both parties.
I am only 15 minutes into this discussion (and 30 years into my design engineering career) but had to pause to thank you guys for this video. It is a Saturday morning and I just KNOW the rest of the chat is going to be inspirational. Right, ... back to watch the rest! 🙂👍
Yup, inspirational. I've loved moving from coding to design (and coding) as great digital products are only great if people like to use them. Thanks for some great perspectives Mariana.
@@rickatfidrasoft1879 hi, im actually a designer but currently im more interested to learned coding. can you give me some advices? oh ya im still 17ys btw so ya im happy to learn new things XD
so glad to hear it :)
Absolutely loved this interview and Mariana's practical advice. Absolutely love your channel! I religiously watch new interviews every week :)
that's so cool to hear 🫶
omg i didn’t realise it was her because im so used to her twitter profile picture. omg that’s MOTHER!!!!
also this podcast is the best thing on the planet for me rn. THANK YOU!
🤗
this comment hahaha thank you!
Mariana is really talented. Taking a lot inspo from her Twitter. 🇧🇷
same :)
thanks for this episode! speaks so much to me. i am also a designer on a journey to make beautiful interfaces by learning how to code!
i appreciate mariana's drive for learning and care for other people's perspective in their team.
great interview! ✨
same! everyone should just have fun making stuff. that is the best path to learn
I love that the push for designers to code is more common to talk about nowadays. I started out as a UX Designer but wanted to learn how to bring my ideas to life. I started out using no-code tools like Webflow and eventually made the dive into coding. A certain feeling arises when you see your idea implemented/know the technicalities that go into implementation. Now that I've been building things, it's been a slow/steady journey and I'm glad I decided to go in. I appreciate that you post content like this :)
right there with ya :)
Another inspiring episode! It's great to see more designers pushing the narrative that coding is part of creative growth. Love where design career is headed.
same!!
Absolutely great discussion! So much abt how I also see the future of our craft.
🙌
Fantastic episode!! I feel like I could listen to y’all talk about this all day 😂 I’m also enrolled in the course - soooooo excited for it!
niiiiice see you in there!
Big time agree that even the best Figma prototype still has a certain level of abstraction from the real experience. I wish Figma was more focused on improving / removing this level of abstraction by enabling designers to build and launch more realistic experiences directly within the browser. They seem to be more focused on building AI tools to replace designers / enable anyone to be a designer than they are concerned with improving their prototyping tools. For instance, users still can't even type within a text field or fill out forms naturally. Figma is still a far ways off from enabling designers to create truly realistic prototypes.
I've enrolled to the UI Engineering 101 course on Maven. Can't wait to begin learning! :)
See you in there!
So much insight here - this is exactly the type of deep-dive interview I was looking for, on an under-addressed topic! The “ah-ha” moments you both described in the design-dev journey are spot on (as someone going through it myself, also on my 3rd or 4th attempt). Having the idea of a real app to design and build from 0 to 1 has changed my whole mindset while slogging through JS.
Ridd, you asked a question about design engineering becoming more “mainstream” now - do you think this is still a strong differentiator for designers to have? Is it just a matter of time before this becomes the norm? Or maybe it’s more nuanced where everyone will have their own specialization, and it’s a matter of communicating that to prospective employers/clients?
Personally think this is going to be a differentiator for a while. Things never progress as quickly as we think :)
Thanks for sharing this! I love the advice on importance of sharing of work online. Actually this one this quite challenging wanna try to do cross post by Linkedin and X
This was both validating and incredibly inspiring. Still marinating my thoughts on this, but, in short, now it feels like "design tools" ended up becoming some sort of detour. Coming from a hybrid design+code journey, I always got the feeling that tools like Figma what they were really trying to achieve was to become a graphical code editor.
"detour" 👀
great episode! i wonder what these new role 'design engineers' do when they are faced with scaling. i can definitely see a ux engineer working on making the interactions tight or designing components. but what about when you're faced with more complicated things like fast loading tables, or customizable forms like formly? and any of those third party ui components that may not exactly fit with your typical design/engineering workflow? do you use them? or is that relegated to more senior full stack engineers to implement those? asking from a large scale saas point of view, because i can personally code and style things like isolated components, but not implement 3rd party systems that interact with data on the backend as much - but those can still highly effect UI
Sério Mari Cast PER FEI TA
🫰 tmjjjj
Marina do you have Financial Aid for your Engineeering 101 Course?
Design engineer is an interesting role I just started hearing in the last months .
The definition is not clear to me, is it a designer that an create components in react/swift something else?
It's a tough one to nail down which is why I'm kind of trying. Some report to design and others report to engineering. Often it's a bridge role between the two (i.e. creating all of the frontend code that hooks up to the data and API calls that traditional engineers are creating).
Other times (like in Mariana's case) it's closer to a "designer who can code" like the original Notion hires.
It's very fluid at the moment. I think this is expected with a unique strength on top, like if you are good with 3d or shaders or anything else which can take the level of craft to next level. And I believe design engineers steer away from the norm and acquire these skills organically, which is driven by pure curiosity
I recently did a map that tries to define the scope and competencies required for a Design Engineering role. Although as mentioned it really depends on the company and the context. I did it because I wanted to clarify myself about what this role need to cover in order to learn it. I can provide the link maybe is helpful. Great interview!
@@robertoerre1933 I would like to know the link. Could you share it? Many thanks
@@robertoerre1933 Do share the link. maybe we can all learn together
crafting and building software can be - and is becoming - an aspect of the (product) design work, but certainly not its totality. to me, the this upcoming design engineer role is a call out for front-end developers who dont care for user experience/interface design and for designers that live too much in the figma file and dont talk to developers. it means that the bar has raised and the so called handoff process is going to require much more attention and interdisciplinary knowledge on both parties.