|
|
The collaborative design process has always been somewhat of a pain for me. I think this may be because I have a visual design background which many of the folks I work with do not even know thinking I’m only a programmer and developer. I’ve learned to let the client or agency take the lead on design, often telling myself not to comment on it even though I often see some basic mistakes. Although I’ve built some serious layouts with InDesign and drawn a bunch of logos/graphics with Illustrator, it’s primarily the coding that pays the bills. Lots of clients and agencies already have their own iterative design processes in place before I’m even on board so I have to follow their lead. I think the primary reason I’m in that position is that a lot of folks can use various tools to ‘design’ and far fewer can write and debug code.
|
|
|
-Workflow improvements, in theory, can be quite different than in practice. Right now, I’m just seeing an easy way not to leave my text editor instead of also jumping between a graphics program and the developer console<sub>7</sub>. I can easily use third-party plugins to pull in existing framework libraries for React, Vue, Tailwind, Bootstrap, and other frameworks. I can import existing site designs into Figma using conversion tools and I can export Figma designs back to code <sub>8,9</sub>. I can connect to GitHub repos and view those in my text editor<sub>10</sub>. I mean… what could go wrong ¯\_(ツ)_/¯ ? The quality and formatting of the exported code might be off. And although I bemoaned emails with screenshots above, when Jira and Slack first came into play at agencies I was playing a game of communication ‘whack-a-mole’ every morning instead of having them all in my email client. I’ll give it a whirl for a while for various projects and get back to you. But if there’s one thing I’m 100% sure of… I’ll be working with whatever process parameters I’m given, there will be a whole new batch of agency quasi-coders, and I’ll still be getting screenshots in emails.
|
|
|
+Workflow improvements, in theory, can be quite different than in practice. Right now, I’m just seeing an easy way not to leave my text editor instead of also jumping between a graphics program and the developer console<sub>7</sub>. I can easily use third-party plugins to pull in existing framework libraries for React, Vue, Tailwind, Bootstrap, and other frameworks. I can import existing site designs into Figma using conversion tools and I can export Figma designs back to code <sub>8,9</sub>. I've connected to GitHub repos so that issues and commits can be synced and viewed in Figma<sub>10</sub>. I mean… what could go wrong ¯\_(ツ)_/¯ ? The quality and formatting of the exported code might be off. And although I bemoaned emails with screenshots above, when Jira and Slack first came into play at agencies I was playing a game of communication ‘whack-a-mole’ every morning instead of having them all in my email client. I’ll give it a whirl for a while for various projects and get back to you. But if there’s one thing I’m 100% sure of… I’ll be working with whatever process parameters I’m given, there will be a whole new batch of agency quasi-coders, and I’ll still be getting screenshots in emails.
|
