[ This is a content summary only. Visit our website http://ift.tt/1b4YgHQ for full links, other content, and more! ]
by Web Desk via Digital Information World
"Mr Branding" is a blog based on RSS for everything related to website branding and website design, it collects its posts from many sites in order to facilitate the updating to the latest technology.
To suggest any source, please contact me: Taha.baba@consultant.com
In this 2-part series, Google Developer Experts Jurgen Van de Moere and Todd Motto share their 12 favorite productivity tips for developing Angular applications using WebStorm.
You can check out part one here. In this second part, Todd shares his personal top 7 WebStorm features that allow him to increase his productivity on a daily basis:
Each tip will power up your productivity while developing Angular applications in WebStorm. Let’s explore these tips.
Before we get started!
When making changes to settings, remember that WebStorm allows you to change Settings/Preferences at an IDE scope and at a project scope separately.
By default, WebStorm will resolve your import paths relative to the file. This setting will satisfy most projects and avoid unnecessary path editing. It’s also the method used for projects generated with the Angular CLI.
What’s fantastic about WebStorm is that you don’t have to type these import statements yourself! When you need to use a construct that would usually be imported, just type it where you need it. WebStorm will either suggest the construct to import through the AutoComplete context menu, or highlight the construct and give you the option to import it by pressing Option + Enter.
WebStorm will create a new import statement at the top of the document for you, or add the construct to an existing import group that is using the same source library.
WebStorm gives you other specialized options to handle your imports. For projects that require it, you can instruct WebStorm to calculate import paths relative to the tsconfig.json file location. If you decide to roll up your exports using a barrel index.ts file to import your components (read more about the Barrel technique) then you can use Use directory import (Node-style module resolution). This will use the Node.js module resolution strategy, instead of TypeScript’s classic module resolution strategy.
When importing submodules that don’t require the entire module to be imported, add that module to the Do not import exactly from list. WebStorm will skip the specified path during the automatic import. For example, instead of having:
import {Observable} from 'rxjs'
Adding rxjs to the list yields:
import {Observable} from 'rxjs/Observable'
WebStorms skips the rxjs module and imports the Observable submodule automatically for you!
Extra tip: Format input to use space inside curly brackets in Preferences | Editor | Code style | TypeScript – Spaces – Within - ES6 import/export braces.
When you find yourself writing certain patterns of code repeatedly, create a Live Template to quickly scaffold the block of code. WebStorm already comes with some predefined Live Templates that you may modify to fit your development style.
To create a Live Template, navigate to:
You’ll see that WebStorm has already bundled the predefined Templates into categories. I created a category to bundle my ngrx Live Templates by clicking on the + sign and choosing "Template Group." I then created a new Live template within it by clicking on the + sign again, but choosing Live Template this time.
Let me walk you briefly through the elements that make a Live Template a productivity success:
You are ready to try out your template. Open a file that honors the context you defined and type your shortcut, press the defined expansion key and watch your template appear for you! If you defined any variables, the cursor will be placed where the first variable should be entered. If there are other variables defined, you can use tab to navigate to them - no need to click.
WebStorm is an excellent testing tool. You can run a variety of JavaScript tests right from the IDE, as long as you have the Node.js runtime environment installed on your computer and the NodeJS plugin enabled. Here are some productivity tips when running tests.
Continue reading %Top 12 Productivity Tips for WebStorm and Angular – Part 2%
Developing software has become a collaborative effort. Many development platforms are open source. Developers share libraries on GitHub. And there are huge communities for knowledge sharing, like StackExchange.
While most developers hate email, a developer newsletter can be a great way to share knowledge, be visible in the community and establish yourself as an expert.
A carefully curated newsletter full of useful tips and other content is not the type of email that people hate. Rather than being a distraction, it can be a great time-saver and help readers avoid missing any useful content.
But how do you get started?
A good way to get started is to subscribe to some well-done developer newsletters and learn by watching what their authors do.
An instructive example is Ruby Weekly, which was started back in 2010 and today is at an almost unbelievable issue #358.
What we admire about this newsletter is its consistency. It’s sent every Thursday and has been sent on that very same day for years and years. This is a great way for readers to know what to expect and when. Its layout is simple and no frills. And the articles shared are strictly on topic every week.
A very different, but also very interesting example is Versioning by this article’s publisher, SitePoint itself.
It covers a broader array of topics, and is sent on a daily basis. It’s early morning reading to make sure you’re briefed on the best in front-end, back-end, UX and design, business and wacky tech news, to start your day.
What we like is its personality. It’s personally curated by SitePoint’s Head of Content, Adam Roberts, and spiced up with his own sarcastic humor and plenty of puns.
Another tech newsletter we like a lot is Vue-newsletter. We really admire the laser focus on just a single JavaScript framework.
The result of this focus is a very comprehensive newsletter. Each edition provides a good overview of everything that has happened in the Vue.js community in the previous week. It becomes essential reading and a perfect one-stop shop.
A final example is the Fullweb newsletter, a newsletter for full-stack web developers.
It, too, really has personality, but very much uses design to achieve this. And again, its format is very consistent, sharing the five best links of the week, every week.
Subscribing to a few newsletters is the perfect way to get started. It will provide you with plenty of examples of what others do, and help you figure out what works and what doesn’t.
We hope that our favorites are a good start. To find more great developer newsletters see the tech section on Revue’s newsletter directory, Discover.
We’ve looked at some great developer newsletters. Are you ready to start your own? Then we have these best practices for you to provide some additional guidance.
The newsletter needs to be high in quality and authentic. You will only succeed at that if you are very involved with the topic.
The broader the topic you choose, the harder success will be. There will be more competition on general topics than a well-chosen, still-neglected niche. People in a niche will be glad to receive highly targeted news, and will quickly recognize and appreciate your expertise.
Sending a newsletter in your own name creates trust. Readers will open and read the newsletter because they recognize the sender.
Adam sends Versioning, Kevin Rose sends his Journal, and Boris sends The Next Web's newsletter…
It’s email. It’s person-to-person communication. And it’ll be much more effective if used accordingly.
There are different frequencies for newsletters — daily, weekly, bi-weekly, monthly, quarterly. While the right frequency depends on the topic and also on the author, it’s still important to send the newsletter regularly.
This will set expectations with readers and help them decide whether the newsletter fits their reading habits.
Benedict Evans, partner at venture capital firm a16z, has sent his personal newsletter every Sunday for years. And the results are impressive:
The people you hear about are often influencers or public figures with astronomical numbers of followers or subscribers. Don’t forget that while they are the ones you hear about, they are a minority. Reaching the right audience is much more important than reaching a large audience.
And you know what is best? Once you have identified the right audience and reached them, you can be pretty sure your subscriber numbers will go up. Just make sure your subscribers are happy and ask them to share the love.
If you have picked your topic carefully and chosen a specific niche, you should look for other places where this topic is discussed and carefully promote your newsletter there.
Continue reading %How to Start a Developer Newsletter%
Happy World Usability Day!
Join us for a video panel hosted by our friends at Optimal Workshop and hear three industry experts share their stories and experiences about usability.
This year, they sat down with three UX experts: Anna Lee Anda, Greg Nudelman and Mark Wyner.
Optimal Workshop’s take on this year’s theme is ‘How to bring the wider team closer to UX research’.
They believe it’s important for companies the world over to recognise UX research and design to make more thoughtful, accessible and delightful experiences for everyone, everywhere.
Head on over to Optimal Workshop to watch the panel discussion, read articles, and even win prizes!
The post UX Experts Share Stories on World Usability Day appeared first on UX Mastery.