Talk about "Drawing" and tools

I am often asked: how to draw pictures and what tools to use?

Every time I encounter this problem, there is a trace of joy in the brain circuit;

It's not that the problem is strange;

It's because I'm not professional in drawing pictures, even if it involves drawing at work, I haven't read any related grammar or rules;

in fact;

For the operation of drawing pictures, the individual is purely at will, and the tool is repeatedly jumped;

The mixed and disorderly styles of pictures in many work documents are particularly obvious;

So, about drawing and tool selection;

Two sentences can explain clearly;

[1] The clear indications are all "good pictures";

[2] Free, sufficient, and support cloud storage, all are good drawing "tools";

As for other aspects, I haven't noticed;

In terms of developing this scenario;

The fundamental purpose of drawing a picture is not whether the picture itself is beautiful or not, but whether the process and logic to be expressed are clear;

The most important thing;

Many scenes can be understood at a glance with a picture, directly saving a lot of boring text descriptions, which greatly improves efficiency and experience;

certainly;

If the aesthetics is good enough and time is enough, you can also write a volume of your own drawing level;

Let's talk about the experience accumulation and tool practice of drawing in the past few years;

Let’s talk about tools first;

If a worker wants to do a good job, he must first sharpen his tools, and there are "really" many useful tools;

As for which one is the most convenient, you have to toss and fiddle to know it yourself. Generally speaking, different tools must have their special applicable scenarios;

The following paragraphs have been in use, in no particular order;

【Markdown】

Quickly make various graphics through grammar, the most efficient way, the premise is to have a certain accumulation of grammar;

【draw.io】

Powerful and rich components, many documents have integrated this component, providing convenient cloud storage capabilities;

【ProcessOn】

The R&D team has a unified tool for big picture production, and the template library is very rich;

【语雀-画板】

A document tool for team collaboration, the overall function is very rich, and the pictures of many blog content are from Yuque Sketchpad;

【Carbon】

A tool for converting source code to images, of course, other document content can also be converted, and the frequency of use is very low;

In fact, the tools used are far more than these;

Don't ask which one is the best;

There are no multiple-choice questions in the adult world, different tools are used in different scenarios, and the pursuit of efficiency is the answer;

Let’s talk about drawing again;

There are many scenes involved, and the space for play is wider;

From a professional perspective;

From organizations, to departments, to individuals, involving organizational structure and role management, and then intertwined with products, technologies, and business models;

The complexity can be imagined;

If you want to understand the core framework quickly and intuitively, it is the best choice to refer to various schematic diagrams;

When a newcomer enters the job;

Will understand the company's "organizational structure diagram", the "system architecture diagram" of the R&D team, the "business system diagram" at the product level, etc.;

During the actual development process;

Frequently used flowcharts, sequence diagrams, class diagrams, database model diagrams, etc.;

For drawing needs in different scenarios, you can find suitable and easy-to-use tools, and any single tool is not enough to support the needs of all scenarios;

There is another problem that is easy to tangle;

Within the team, is there a need for unified drawing tools and grammatical rules;

Let me talk about my personal habits first;

Although there is a learning cost for the cartographic grammar that I have only seen Markdown, it is easy to use and efficient;

In addition, any other basic rules of drawing have not been carefully reviewed;

However, in the early stage of drawing, I referred to many excellent templates in ProcessOnand in;draw.io

Let's talk about the requirements of the team;

There are only a few core large-scale productions, which are required to ProcessOnbe managed in a unified manner, and someone is responsible for regular update and maintenance, and others are free;

There are requirements and there is room for free play;

Within the company's organization, it usually involves the production of large-scale images of various scenes;

For example, the common large picture;

Organizational structure, business model, product matrix, collaboration process, business system, etc., the main purpose is to expand the frame display of these dimensions at the company level;

These large pictures will be archived to the knowledge base, and the commonly used tools are the internal integration tools of office software;

【Organization Chart】

Describe the company's rights and responsibilities and the structural system of hierarchical management. Although it is relatively clear on the surface, I personally feel that this is the most difficult thing to manage;

→ A lot of infighting and involution in the workplace require a deep understanding or misunderstanding of the organizational structure; "Workplace Experience"

【Business System Diagram】

Top-down analysis of the company's main business system has the same taste as the organizational structure;

→ The common phenomenon is: the higher the rank, the higher the requirements for business ability; "refer to the workplace promotion document"

【Business Canvas】

As a commonly used model diagram in the company's internal business, it mainly focuses on three aspects: customer needs, platform capabilities, and business resources;

→ For most business bragging scenes, many businessmen introduce their company's common speech routines; "It is said that they will make up the picture"

Organizational core framework diagram;

It is necessary for professional players to roll a roll, and they will not suffer losses. What if you really need to play high-end games?

In the R&D team, there are only a few large guiding pictures involved;

For example, the common large picture;

System architecture, business system, technical system, R&D process, deployment process, etc. The main purpose is to guide the team's internal R&D guidelines;

At present, the team uses 语雀these ProcessOntwo tools;

【System Architecture Diagram】

The system architecture should be the core big picture of the R&D department, which can intuitively reflect the core structure of technology and business;

→ If newcomers want to quickly understand the business and technical system, it is most efficient to start from the system architecture diagram;

【Sorting chart】

Items that have been promoted recently, such as system component application list, third-party cooperation information list, unified management of various accounts, etc.;

→ Complicated large structure diagram, coupled with a simple form information, the experience effect is very good; "more than one hundred accounts"

【Process collaboration diagram】

Sort out the core roles and nodes in the collaboration process, so as to ensure that the corresponding matters can be advanced in an efficient and orderly manner;

→ Companies with good management all pay more attention to the standardization of processes, which is also a topic that is repeatedly emphasized in work;

From years of experience in moving bricks;

When writing summary reports or promotion documents, organically combine your work content with the team's framework diagram, and the visual effect is first-class;

As a programmer, learning to draw sketches is really a necessary skill;

Complicated business scenario sorting, abstract programming logic, R&D also need to coordinate the management of the two, and these tasks can be completed quickly and accurately with the help of drawing;

As for drawing tools, the ones recommended above are all easy to use;

Personally, I am used to using complex large images draw.io, using blog content 语雀-画板, commonly used grammar at work Markdown, and using programming tools for class diagrams;

【Programming Advanced Map】

In the past few years of work, many components of the active or passive learning technology stack have only been used shallowly;

→ When they first entered the workplace, most players probably dreamed that they could become technical experts; "I still have this fantasy"

【Technical flow chart】

In R&D, we need to design a lot of complicated processes. Personally, I like to use Markdowngrammar the most, and I use Carbontools to convert code to pictures;

→ It is extremely efficient through grammar mapping. Many tools provide the integration of this capability. If you are not satisfied with the default style, it is recommended to use it with caution; "Enhancing Efficiency and Anti-involution"

【Coding Tool Class Diagram】

During the coding process, the relevant class diagram design can be directly generated by coding software, and can also be pasted on the canvas to add comments;

→ In the work, we must be proficient in using the commonly used tools, so that we can solve various things efficiently, and then focus more on the core dimension; "Laziness makes tools improve"

It is necessary to emphasize;

Tools are fundamentally to improve efficiency, and drawing is just a presentation of thinking and understanding of affairs, so it is enough to try more;

At work, I have encountered big-witted operations using pptand drawing architecture diagrams, and the effect is not inferior to other tools;word

Therefore, tools are not a problem, and drawing should not be a problem;

The core ability lies in the understanding of complex issues, whether it is comprehensive and in-depth enough, of course, in the process of understanding, a lot of sketches may be needed to assist in the final rendering;

Finally, if you have a useful tool, remember to leave a message and share it, don't hide it;

$EN D$

Talk about "Drawing" and tools

Guess you like