• State of Frontend 2020 Report – Frontend Development trends by tsh.io
  • Authors: The Software House, Vercel, DAZN, Honeyspot, Onely
  • The Nuggets translation Project
  • Permanent link to this article: github.com/xitu/Annual…
  • Translator: Hoarfroster
  • Proofread by: LSvih, HumanBeingXenon, Usualminds

Click here to view =>directory

Click here to view PDF =>Fly books – State – of – Frontend – 2020 – by – TSH. PDF

9. The Design of the Design

With the addition of product designers, software companies are increasingly focused on creating strategies and products that align with their customers’ business goals.

Graphic designer to join the software development team already is nothing new, still vaguely remember ten years ago, or have the subject may be more early, but now we finally came to the designers and developers collaborate closely what is not fresh but the standard time, and we are still a lot more great, can help these more collaboration tools.

In software development, the most basic categories of design types are probably UX (optimizing the possible user experience), UI (building the right user interface), and product design (thinking about the customer’s business and business goals). Nowadays, it is standard for software developers to employ two types of designers — UI/UX designers who are user experience-centric and product designers who are business-centric.

The birth of a product designer makes me particularly happy: it means that as a software company, we care more about the actual needs of our customers and focus on creating products and strategies that are relevant to our business. And customers are starting to realize this change — more than 70% of development teams worldwide have at least one designer (see Chapter 8 Development Teams). Instead of hiring additional freelance designers, clients can now choose a team that allows developers and designers (as well as project managers, software testers and others) to work more closely together.

To make collaboration more effective, we also need better tools. For years, designers have been using software like Adobe Photoshop — it’s hard to find tools that fit the needs of designers in the software development business. Fortunately, there are plenty of tools for this, including Figma, Invision, Sketch, and Zeplin. These tools make it easy to create vector graphics, collaborate with other designers, and submit designs to front-end developers. 71.7% of the development team uses this tool, which is great!

While the relationship between designers and front-end developers may not be that great, I believe the future will be bright with more designers and better design and submission tools.

Did you use any transition design tools when working with designers last year?

What transition design tool have you used

10. QA Quality Assurance

Software testing and software development are two inseparable subjects

As more and more digital products are implemented on the client side, we software engineers and quality inspection specialists must incorporate testing as part of our workflow to develop, maintain and extend JavaScript applications. Happily, as many as 80 percent of front-end developers already perform software testing, and this number is increasing in recent years.

Fortunately, the JavaScript ecosystem provides us with plenty of tools to build perfect test suites and provide adequate code coverage for testing our applications.

In recent years, we’ve seen a trend in the JavaScript testing ecosystem toward iterating toward simplicity, improving the development environment for developers through ergonomics, integrating with other testing solutions, and much more. At.cult, many software projects, including our powerful application, Honeypot.io, are automatically tested and gain higher test coverage as the code base grows. In addition, our quality assurance team will manually test and verify that the functionality and design fully meet the functional requirements, which is an important part of our release workflow to better ensure a great user experience.

While our team allocated more time to manual automated testing while developing the platform, we found time and time again that software testing was an excellent and necessary investment in the stability of our digital products, ultimately impacting the efficiency of our overall workflow. We use units like Capybara, RSpec, Ember CLI, and QUnit, integration, and end-to-end testing. Of course, there are many more solutions to choose from. At.cult, we firmly believe that the continued development of an ecosystem of tools for testing will enable us to cover a wider range of product development through automated tools in the near term. Why are we doing this? Because we believe that software testing and front-end software development go hand in hand.

In your team, who is responsible for software testing

Have you tested software yourself in the last year?

What kind of software testing have you done yourself?

  • This article is participating in the “Nuggets 2021 Spring Recruitment Campaign”, click to see the details of the campaign

If you find any mistakes in your translation or other areas that need to be improved, you are welcome to the Nuggets Translation Program to revise and PR your translation, and you can also get the corresponding reward points. The permanent link to this article at the beginning of this article is the MarkDown link to this article on GitHub.

The Nuggets Translation Project is a community that translates quality Internet technical articles from English sharing articles on nuggets. The content covers Android, iOS, front-end, back-end, blockchain, products, design, artificial intelligence and other fields. If you want to see more high-quality translation, please continue to pay attention to the Translation plan of Digging Gold, the official Weibo, Zhihu column.