Where the design community meets.
Front-end developer Joined over 8 years ago
Wouter hasn't posted any stories yet.
I actually miss using Gulp from time to time, it was a lot easier to setup and extend. Everything was based on different tasks that you execute in a specific order.
Plus you could also integrate other tasks that weren't related to your build process.
I exclusively use Webpack now, but Gulp was a lot more fun to work with.
Just to provide some feedback; I'm guessing English isn't your first language, in the future it would be best to have someone proofread it first as there are a lot of structural errors in your text, making it incredibly difficult to read.
Also your first sentence is just plain wrong.
Node.js can be use frontend as well as backend for coding purpose in web app development.
But overal the article does a poor job of explaining why you would want to use Node.js for backend development, there's a lot of good use cases, but you fail to outline them.
I could definitely see myself using this, I live in a city where there's a huge lack of talent, every day I get multiple recruiters emailing me with jobs, it's really difficult to keep track of the ones I've already applied to and at what stage they are.
I used to keep notes in Evernote, but for some reason that doesn't really work for me. So something more organised might do the trick.
Also seeing #3b5998 here in Hong Kong
I can understand you were having issues with anything below IE7, but quite frankly, if IE8+ is still bothering you so much, you might need to review all the code you're writing for it.
In large Angular.js projects, it's much easier to organise your routes in a good directory structure
- routes - Templates // A separate folder that contains parent templates which other routes will use. - users // List of user (/users) - users.route.js - users.controller.js - user.template.js - user // Individual user (user/:user) - user.route.js - user.controller.js - user.template.js - edit // Edit user (user/:user/edit) - edit.route.js - edit.controller.js - edit.template.js - settings // Settings ( /settings) - settings.route.js - settings.controller.js - settings.template.js - notifications // Notifications settings ( /settings/notifications) - notifications.route.js - notifications.controller.js - notifications.template.js
And so on, if you are looking for user/:user/edit, you instantly know where to look based on the folder directory.
I've been using this method for a while now in some large Angular.js projects, and found it to be really helpful.
From Belgium, working in Hong Kong. So a regular working visa for me.
Wouter hasn't upvoted anything yet.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.
This discussion could go both ways, I've worked with plenty of developers who will just code something without thinking about design, users or business requirements. All they could think about is their code and how perfect it should be. At the end of the day, most users won't care about the code you've written, they won't even care about the design, but they'll care about how they'll use your product.
I don't particularly think should learn to code, work better with developers for sure. But I think designers should at least give coding a try, it will only be for their personal benefit. If you have an idea that might be hard to explain, you can always just code it, or use other means to make it functional so anyone else can code it up.
Asking the question "why are we expected to learn coding?" is a good one, saying "why we shouldn't" is just stupid; there's no reason why you should stop learning, especially with everything going more and more digital, it'll only benefit you. The same way it will benefit developers to understand design better and think more about their users.