I'm an ex-programmer and I want to create a basic guide for designers that want to learn some front-end development. As designers, what do you feel you don't know about it and wish you would?
Pushing production code in a dev environment and staging. Using git to handle the latter, and setting up a proper environment. And all things html/css/js.
Yes, definitely this ^
I think a good starting point for writing the guide would be 'What designers don't know, but FE developers wish they did' :D What designers wish to know about might not be the thing that they need to know in order to..whatever - make communication with FE better, make end product match the design files even more etc.
I'd be interested in (clickbaity) articles like '5 things to keep in mind when designing apps that will be coded in swift' or what's easy to do for iOS apps, but hard for Android and vice versa. In general, anything that has to do with designing apps for different platforms.
Oh that's awesome. There are a lot of libraries, languages and frameworks and each has its unique properties needed attention. I will totally think about this direction and update. Thanks!
You're welcome! :) I just feel like that would be a more unique take on the topic.
Awesome. Will do!
Learning git was a turning point in my 'development career' and today allows me to interact with devs much more proficiently.
Nowadays I can't think how I'd be able to work without it, haha.
Do you wanna sell to designers, or educate designers? If you are a programmer, then you already know what designers would be better off knowing I think.
That's definitely a big thing to consider and it's not a thing many designer pay attention to. Thanks!
Probably something that outlines best practices. In an ever growing field it seems that the way to tackle a particular problem is endless.
Perhaps some do and don'ts when it comes to jumping on the next big thing. I'm looking at you grids...
How to make a rap naming the most popular frameworks.
I know it's not front-end but I'd like to know where to start with backend, and saving data. just the simple stuff and not like 5 frameworks and super perfect security. ut I'd like to involve some backend possibilities in my work that I would be able to play around myself
As a designer who is fluent in HTML/CSS but can only read JS and write very basic functions, I want to learn more about best-practices in JS with examples specific to prototyping UI or manipulating basic data. I have looked at lots of JS learning resources and while some are great, they are too often over-abstracted regarding manipulating data or arrays without any clear visual connection to how this could help me save time prototyping or animating a website or app.
I know theoretically all the things JS can do to a string, or array, or what-have-you, but I have a hard time knowing how to tackle something I want to do or what the best way to do it would be.
If you want to generate 50 elements and randomize these two X and Y attributes for an animation with increasingly shorter duration per element, this is the cleanest way to do it and why. Here is another way to do it that is harder to read, but is more performant and why.