DEV Community: Jerrold.Lee

My New Product PinterestVideoDownload.org launched!

Jerrold.Lee — Sun, 14 Sep 2025 15:13:54 +0000

Hi everyone, I’m the product developer behind PinterestVideoDownload.org. I want to share with you why I built this tool, what problems it solves, and how it works — so you can see the care and intention behind it.
🔧 Why I Built It
From talking with users, I kept hearing the same frustrations:
Wanting to save a Pinterest video or image for later and not having a simple tool to do it.
Having to install apps, sign up, or jump through hoops just to download something you saw and liked.
Worrying about quality: sometimes what you download looks distorted or low-res.
So, I set out to build something clean, fast, and reliable — something that "just works."
🎯 What I Focused On
When developing PinterestVideoDownload.org, I prioritized:
Simplicity — Minimal steps. Copy link → paste → choose quality → download.
User privacy & safety — I made sure the tool doesn’t store your downloads or unnecessary data.
Cross-device compatibility — Whether you’re on mobile, tablet, or desktop, same experience.
High quality output — Multiple video/image resolution options so what you save still looks great.
🚀 How It Works
You copy the link of the Pinterest video or image you want.
Go to PinterestVideoDownload.org, paste it in.
Select the resolution / quality you prefer.
Download. That’s it.
I designed the backend to be fast, the front-end to be intuitive, and to handle all common edge cases users hit (bad links, slow connections, etc.).
🤝 What I Hope You Gain
My goal was to build something useful to creators, curators, or anyone who just loves collecting visual inspiration. If this saves you time, gives you flexibility, or helps you keep what inspires you — then I’ve succeeded.
If you use it and have feedback — for example, ideas for better UX, missing features, or issues — I’d love to hear. I’m continuously refining things behind the scenes.
Thanks for trying it out, sharing it with your friends if you like it, and supporting small dev projects like this!
👉 Try it out: PinterestVideoDownload.org

200+ Best Platforms to Promote Your Startup for Maximum Visibility

Jerrold.Lee — Fri, 01 Aug 2025 15:21:10 +0000

The Ultimate Guide to Getting Your Product Discovered by Millions

Are you tired of building amazing products that nobody knows about? You're not alone. Every day, thousands of innovative startups launch with groundbreaking solutions, only to struggle with visibility in an oversaturated market. The difference between success and obscurity often comes down to one crucial factor: strategic platform promotion.

After extensive research and analysis, we've compiled the most comprehensive list of 200+ platforms where you can showcase your startup and reach your target audience. This isn't just another directory – it's your roadmap to startup visibility success.

🚀 Why Platform Promotion Matters

In today's digital landscape, organic discovery is nearly impossible. With over 3.5 million apps in major app stores and countless SaaS products launching daily, your brilliant idea needs strategic exposure. The platforms listed below have collectively helped thousands of startups:

Generate millions in revenue
Acquire thousands of early users
Secure funding from investors
Build strong community followings
Achieve viral growth

🏆 Top-Tier Platforms: Your First Priority

1. ProductHubX - The Rising Star of Product Discovery

Website: https://producthubx.com/

Submit: https://producthubx.com/submit

ProductHubX has emerged as one of the most influential platforms for product discovery. 0 With its focus on AI tools and innovative products, it's become the go-to destination for early adopters and tech enthusiasts. The platform features daily product showcases and has an engaged community that actively supports new launches.

Why ProductHubX stands out:

High-quality, curated product listings
Strong community engagement
Excellent SEO visibility
Direct access to early adopters and investors
Featured product opportunities

📈 The Complete List of 200+ Platforms

🎯 Strategic Submission Tips

Phase 1: Start with Top-Tier Platforms (1-20)

Begin with ProductHubX and Product Hunt as your primary targets. These platforms offer the highest ROI and should be your immediate focus.

Phase 2: Expand to AI-Focused Directories (21-80)

Target platforms specifically designed for AI and tech tools. These have highly engaged audiences looking for innovative solutions.

Phase 3: Community Engagement (81-150)

Engage with Reddit communities and developer platforms. These require more effort but offer authentic community feedback.

Phase 4: Comprehensive Coverage (151-200+)

Submit to remaining platforms for maximum coverage and SEO benefits.

📊 Expected Results

Based on successful case studies, startups using this comprehensive approach typically see:

300-500% increase in website traffic
50-100 new users per platform (top-tier platforms)
Significant improvement in search rankings
Enhanced brand credibility and social proof
Increased investor and media attention

🚀 Ready to Launch?

This comprehensive list represents months of research and validation. Each platform has been verified for active submission processes and engaged communities.

Start with ProductHubX and Product Hunt today – these two platforms alone can transform your startup's visibility and growth trajectory.

Remember: Success in platform promotion isn't just about quantity – it's about strategic, consistent execution across the right channels at the right time.

Ready to take your startup to the next level? Begin your platform promotion journey today and watch your product reach millions of potential users worldwide.

Original article: https://github.com/JerroldLee/SEO/blob/main/200-powerful-platforms-to-promote-your-startup-for-maximum-visibility.md

How to break through the exhausted front-end business?

Jerrold.Lee — Wed, 22 Sep 2021 11:54:51 +0000

As a business front-end, while fulfilling business requirements, it also has to deal with various online problems. After working hard and busy for a year, the boss said that "thinking is not enough" and "there is no business scene". I went out for an interview and was asked. The project, I can’t say anything that has highlights or challenges, I want to do something awesome, and I haven’t found any valuable directions. I finally find some directions, and I have to be "suppressed" by various questions from the boss. In the end Maybe it's just a little performance optimization work, and some reusable components are removed... I can't help but sigh, business is difficult, front-end is difficult, and it is even more difficult to do business front-end!

If you have such feelings and predicaments, I want to tell you that this is really normal. There are many thoughts on this issue in Ali’s internal technical forums. Based on my own understanding and research, I have also referenced many A summary of experts in different front-end fields, write this article, I hope it will be helpful to everyone.

The dilemma of the business front-end

1. The front end of the business is "very busy"

The front end of the business, as the name implies, is the front end of the business, directly in contact with the PD and operations of the business, and is directly responsible for the users of the product. In actual work, the front-end business is often busy with various meetings, projects, and Q&A. Even if there are multiple front-end classmates on a business line, they may still feel strenuous in the face of Chengshan's needs. The reasons may include:

Demand scheduling is inverted , and development time is tight

I’m not familiar with the business. I only go to the visual review when the project requirements have been determined. There is no way to judge whether the business logic behind the requirements matches the business rhythm, whether the requirements themselves can achieve the business goals, and whether there is a better way to achieve them. Able to accept the demand, and then schedule

Maintenance costs are high , and I have to be busy solving various online problems every day. For example, there is a problem with the style here, why is there no display... Various trivial problems make your life very "fulfilling"

Demand response speed is slow . For example, the business technology stack is old, or there are too many custom logics. You have to check the documentation while writing the code. If you can't find it, you may need to check the source code, which greatly reduces the efficiency. Or it may be different from other business technology systems, which are difficult to reuse and accumulate. If you want to use it, you may have to rewrite it again...

2. Is the front end of the business a "resource"?

Under such pressure, the front end of the business is often reduced to a "resource" . When you become a "resource", you have actually lost the qualification to talk to the business on an equal footing. They will only treat you as a development machine for undeserved feelings. Enter requirements with you and let you spit out the page. In such a relationship, you originally wrote fairly neat code. In order to quickly achieve business requirements, you also began to write messy code, and you have no words about the products you create. Quan, over time also lost his passion and patience.

If you lose your enthusiasm and you are not happy about writing, it’s because you haven’t made anything special, and your boss won’t particularly approve of your hard work. He will also feel that you don’t think enough, don’t have a business scene, don’t help the business, and don’t let the business. It's different because of your existence ...

3. Want to make a breakthrough in the front end of the business

Okay, then I decided to make some changes , so I put forward a series of ideas with the boss:

The technical system here is too old, in order to further improve the development efficiency, we want to carry out technical reconstruction

The front-end and back-end joint debugging is a bit laborious. We want to build a joint data center to improve the efficiency of joint debugging.

The display speed there is too slow, we need to optimize the performance

...

The boss often asks a series of soul questions :

Why do it? (What is the business value? What is the technical value?)

Why do it now?

Why did you do it?

What about ROI (input-output ratio)?

Before it started, the restless heart was poured cold water by a series of "questions" from the boss.

If you don’t answer these questions well and convince the boss, you won’t be able to win any resources. You can only do it by one person. Often the quality is not good and there is no one to use. In demand.

I was not happy and did not grow up. In the end, I could only leave the job dimly, but would it be okay if I changed a company? It is likely to be a similar process...

This is really the "dilemma" of the front-end business, so how to break through this dilemma? First of all, we must set our mindset and start with understanding the business.

Understand the business

1. Business and demand

Before understanding the business, we must first know that business and demand are not the same. Understanding the requirements does not mean understanding the business. The requirements are the products of the business after product digestion, which may have been deduced or disassembled. Therefore, the requirements are not the business itself . Of course, the more you understand the needs, the better you will understand the overall picture of the business.

So what is business? The industry has many definitions of "business", but the main idea remains basically unchanged. Business is a process in which a series of people complete a certain task through a series of activities. Therefore, the business can be large or small, and can be split infinitely.

The business involved in this article generally refers to commercial business, which is the business or its component parts directly related to the business model of the BU or company.

2. Why should the front-end learn business

Even if the front-end does not learn the business, it does not affect the demand. After all, you only need to tell me what the interaction is like, and the front-end can help you achieve it, and there is already a product manager role. Why does a technologist ask the dog to take the mouse, or do it on his behalf? This is to say:

Only by understanding the business can you think of things that the business side has never thought of from a technical point of view; if you don’t understand the business, you may not understand what the business side wants, and you can’t even figure out the business logic of the requirements. In this case, there is only one cooperation model. Seed, the demand comes down, you catch it, and then schedule it. Maybe, the design of this requirement is unreasonable , you don’t know; there is a better solution for this requirement, you don’t know; this requirement can be solved through ready-made related product solutions , saving time and manpower, you don’t even know.

Only by understanding the reasons behind the business can we plan the future of technology from a global perspective. If you don’t understand the business, you will be far away from the real needs of users. The harder it is for you to find some of the pain points and challenges, and you can’t really put forward your thoughts and solutions to solve users’ problems.

As a product research and development engineer , I naturally hope to personally polish a product that solves user problems and is experience-friendly. If the product can be recognized by users, it will have an impact and will naturally have a special sense of accomplishment.

As a commercial technology company, Alibaba's requirement for technical people is to combine technology and business . On the basis of meeting business needs, it becomes a bridge between technology and business, actively enters the business, and thinks about how to help the business win and satisfy through technical means. Market and user needs, advance technical planning, talent reserve, technical architecture and technical pre-research.

3. Do you understand the business?

So do you currently understand the business you are dealing with? Try to answer the following questions:

What does the business do? Is there a big picture of the product?

What are the core indicators of the business? What are the KPI goals and what is the meaning behind these numbers? To achieve these goals, what is the business strategy?

Who are the users of the business? How is traffic stratified? What's the proportion? What is their positioning in the business?

The business model of the business? How to attract traffic and what is the profit model?

What are the pages we make? What value does it bring to the business? What can we do to create more value?

4. How to learn business?

Suggestion 1: Reading of business domain knowledge

Find books with good scores related to the field to concentrate on reading, and quickly form a knowledge framework.

Recommendation 2: Understand the business background and planning

Just take over a new business, you can invite the business owner or senior operation/product classmates to tell you about the past, present, future, vision, fiscal year planning, and expectations of technical classmates of this business;

Take the time to read the weekly reports of the partners (operations, products, R&D) to understand what is happening now and whether it is getting closer to the goal;

Understand the business goals, landing strategies, and the data caliber to measure the goals, pay attention to the data, and pay attention to whether the current project is fighting to achieve the goal, if not, put forward your ideas and suggestions;

Participate more and establish a product sense. The best way to collect information is to participate in the KO meeting of the boss of the business. Various KOs will disassemble the strategy and the thinking behind it and communicate to the BU or classmates in the department.

Recommendation 3: More exchanges

Chat with server-side classmates, chat with PM, chat with users, and look at the business from multiple angles, but it should be noted that for more professional businesses, you need to do your homework first . At least some English abbreviations must be clear and understandable.

Recommendation 4: Keep the numbers in mind

If it takes a long time before, then this one can be done now, that is, remember the business-related numbers as finely as possible, the more specific the better, and the more comprehensive the better. This has two advantages:

The recorded digital indicators themselves have already covered this business value direction to a large extent, and you will know which dimension the business focuses on;

These numbers can be used as the source of "equal dialogue" with business parties and products, otherwise there is no even the most basic basis for dialogue.

Recommendation 5: Start with daily needs

First of all, the needs are endless, so there must be trade-offs and focus on manpower and energy to do the core business needs in order to maximize the value. If your team is currently in a situation where various scattered needs come in and cannot meet , It is necessary to carry out corresponding demand management measures, such as scheduling bi-weekly meetings.

Secondly, for the one-sentence requirement, we need to analyze the purpose and value behind it , what is the expected benefit after doing it, why this benefit can be achieved by doing so, whether it is in line with the overall goal, and whether the points mentioned by the business side are effective The plan, or the plan that is too costly, depends on whether an alternative plan can be given, and the existing plan or a low-cost method can be used to satisfy the business side.

If it is determined that this demand is OK, but you really can’t spare the time to handle this matter for the time being, in this case you can say that I accept this demand, but I may need a longer buffer time or cut some demand ( Partially satisfied), or if the project must be launched on time, the effect and quality of the project after the launch cannot be guaranteed, and the business side can make partial trade-offs .

Finally, after the project is tested and launched, carefully analyze and pay more attention to the business data and effects after the launch. The analysis and summary have the following benefits:

Improve your understanding of the business . When you pay attention to business data, you will also see from a business perspective whether the value brought by this function meets expectations. When it does not meet expectations, you can The business side will analyze the data funnel together to find the problem and prevent our labor results from becoming a one-time job.

At the same time, the summary can help you sort out the deficiencies in this project, or what problems exist in the related promotion, and how to improve later, which improves the iterative efficiency and quality of the next project. For example, whether there are problems such as poor understanding of requirements and rework in this project, or low efficiency of communication & joint adjustment, unstable environment, and whether the plan designed by yourself is reasonable, and how to solve it in the future.

It can also be judged from the data and summary what kind of demand is reliable & what kind of business side is reliable, the business side who frequently strives for resources to go online but does not have a good effect, and the next time there is a demand, it needs to be increased. A process of mind and thinking.

Recommendation 6: Persevere

Business thinking ability, no one will not be effective for at least half a year.

Boost business

1. Thinking

Although the business is usually very busy, no matter how busy you are, you have to take time to think . So what should you think about? Here are some examples:

Develop the habit of memorizing work content every day and analyze where your time is spent.

In business development, are there any points that make you particularly want to complain? Think about the reason behind the problem. Is there any way to avoid not committing it next time? Can it be refined into a more general solution? How can other students solve it? How can I solve it?

Constantly input and observe, what are the real needs of the business ? Thinking from the perspective of the business side, where are the pain points and challenges encountered by the business?

2. Communication

Focus on the boss, teammates, and business side to confirm whether "what I want to do" is "what everyone wants"?

As the knowledge of the business increases, some "immature tips" will gradually be generated for the business:

The technical system here is too old, in order to further improve the development efficiency, we want to carry out technical reconstruction

The front-end and back-end joint debugging is a bit laborious. We want to build a joint data center to improve the efficiency of joint debugging.

The display speed there is too slow, we need to optimize the performance

Usually you will be ruthlessly rejected by your boss or business side, and you will be confused when you ask.

In the current business context, why do we do it? (What is the business value? What is the technical value?)

Must it be done now?

Why did you do it?

How to do it? (Systematic, full-link, single-point technical challenge)

What are the business and technical results? Can it be reused?

Future planning (can it be linked and co-constructed with BU or group plans)

This is often because the things you propose to do are valuable but not necessary, and do not combine with what the current business needs. In other words, the technology you want to do is considered from a personal and purely technical perspective. There is no technical plan based on the current situation and pain points of the business . It is not grounded and the input-output ratio is not high.

Therefore, first find a good business position for technical output, see if there is any place to borrow, and don't repeat the wheel. After quickly verifying the correctness of this direction, gradually increase investment and full technical design. Don't do it by yourself, silently, and there is no business scenario to pay for it.

3. Technical planning

Business empowerment actually requires us to closely follow our business plans and formulate technical plans and plans. After understanding the key points of the business side’s KPIs this year , the expected dismantling and implementation paths, and combining your own and team situation, think about what you can do to help the business achieve its KPIs. There are two points to note here. Down:

Grasping the essence from the point and aspect, consider the overall situation : In many cases, the pain points and business needs we receive are single points. At this time, we cannot focus on the single point problem at hand, but need to consider the overall situation, such as the SEO page Very sensitive to performance, and often may receive feedback from some business parties, saying that our SEO has this place and that place needs to be optimized, and single-point solution to these problems may not bring much benefit to the business. There is no growth in his skills.

At this time, if you consider this proposition comprehensively, you will actually find that the optimization of SEO pages is actually to improve the inclusion and ranking of SEO pages. In fact, to improve the inclusion and ranking of SEO pages is not only the path of front-end performance optimization, but also some other paths: such as optimizing keywords & long tail words, using Google's AMP technology to transform SEO pages, and optimizing crawlers to crawl pages Time-consuming to improve the crawl rate and so on. In this way, we can turn the problem of the point into the problem of the face, and then we can develop a more effective and comprehensive handle to empower the business .

We must not only solve the immediate pain points, but also long-term plan : In many cases, we can not only be satisfied with the KPIs in front of us, but also need to understand the business side's long-term ideas and foreseeable plans. For example, in the pilot new business, the first level of planning is to ensure that the business projects are launched on time. Considering the future, the other level of planning may be how to achieve the reproducibility of technical solutions .

4. Stand on the shoulders of giants

When you need to develop a productized plan or tool and framework, it is best to look at the group and the industry to conduct a survey to see how the industry and other colleagues solve this problem. Try to stand on the shoulders of others to innovate or participate in co-construction to avoid repetitive and low-quality wheels in small teams.

Technical depth

1. Technical knowledge and technical ability

"Technology" cannot be a general term. I think it can at least be divided into two parts: "technical knowledge" and "technical ability".

What is "technical knowledge"? Knowledge is I KNOW

"TypeScript from entry to abandonment"

"React from getting started to giving up"

"Webpack From Entry to Abandonment"

......

What is "technical capability"? Ability is I CAN

I used TypeScript to refactor a large-scale system, and the code robustness and R&D efficiency have been greatly improved.

I used React Hooks to conduct front-end training for the full stack of students, and the training effect was greatly improved.

I studied Webpack in depth and optimized the configuration, which greatly improved the system construction speed.

.....

2. Cultivate technical vision

Pay attention to new technologies in the daily industry. It is not necessary to understand in depth, but be curious about the new technology and probably understand what it does. If you encounter a matching landing environment at work, you can consider writing a demo to see if it is valuable.

Pay attention to the solutions of the group and the industry . When we discover problems in the business and make solutions, we can easily fall into our own design, and we want to make everything ourselves, but the input will be very large, and the value of the output will be the same? do not know. In most cases, you want to do, can be found to the ATA, the first man to step on the pit, or existing mature solution, as long as you communicate to get in touch, you can easily take in, why spend a lot of Time to make wheels? Where you can borrow, let’s borrow it, and spare the time to do the more core and valuable things in your solution.

3. Technical depth

When you talk about "technical depth", you may naturally think that you have dig deep in a certain technology or solved a technical problem that is recognized by the industry as difficult, but this is only part of the "technical depth":

Systematization/systematization. Body line of thinking is a way of understanding things, in the face of problems, can for complex issues, and outline key elements of the solution, the problem will be scattered and disorderly, become logical, rule-based . In the embodiment of the positioning and solution of the problem, from the appearance to the essence, the reasons behind the problem are disassembled, and the essential reasons are solved in a targeted manner, instead of treating the symptoms and not the root cause, there are solutions to solve them in a rhythmic manner.

Full link. In addition to the front-end part, the technology stack forwards and backwards can dig deep.

Single point of technical challenge. What are your thoughts and solutions on a certain technical challenge?

4. Win-win technology and business

Really breakthrough business results that bring significant value will inevitably be accompanied by technical in-depth and even innovation. Therefore, when doing business results, there must be scenarios that allow us to increase the depth of technology.

finally

Cultivating a sense of business is indeed a very difficult thing. He requires you to take business rather than technology as the first perspective. This may violate the inner "technical persistence" of many people, but if you keep working on technology, it is actually very difficult. It is a very big breakthrough. In your work, if you can achieve a win-win situation between technology and business, it will help you reach a higher height.

Change is indeed difficult, but the result is worth the risk.

FURTHER READING
▶ Walkthrough007 - https://www.walkthrough007.com/

Methods to improve code quality: domain model, design principles, design patterns

Jerrold.Lee — Tue, 31 Aug 2021 16:07:57 +0000

A root cause of poor code

1 Embodiment of poor code

We can enumerate the manifestations of a lot of poor-quality code, such as unintelligible names, super large classes, super large methods, repetitive code, difficult code, difficult code modification... Among them, the two manifestations that most affect the quality of the code are naming untrue names. , Logical scalability is poor. When a newcomer reads the code, he sometimes finds that the method naming does not match the actual logic, which makes people very confused. This phenomenon is not uncommon in normal work; the other is the poor logical scalability. After the new business requirements were put forward, it was discovered that there were many changes to be made, and there were more business logics that needed to be returned, resulting in low R&D efficiency.

2 Problem summary

The problems mentioned in section 1 are summarized and sorted out, and 6 types of problems are roughly sorted out and explained separately.

Naming problem: Naming problem is a very headache, it is not so easy to choose a name that is worthy of the name and easy to understand. When it comes to variable naming, method naming, and class naming, there are two common naming problems: one is incomprehensible; the other is misnomer. Naming is incomprehensible when a person looks at it at first time and does not know what it means. The fundamental reason is that they did not think of a suitable vocabulary to abstract the problem; the naming name is not the same as the actual logic intended to express. Such naming will be misleading. people.
Code structure problem: When a person looks at the engineering code for the first time, before looking at the code logic in depth, the overall code quality can be felt from the module division, class division, and method division. If a class has several thousand lines of code, one There are hundreds of lines in the method. I believe that not many people are willing to look at this kind of logic, and the complexity is relatively high. The hierarchical structure of a good code is very clear, just like reading a beautiful book, there is a pleasing feeling.
Programming paradigm problem: There are three programming paradigms: table mode, transaction script mode, and domain design mode. The transaction script mode that everyone uses the most is the transaction script mode. This mode is most in line with the way people do things, step by step, the biggest problem of this mode It just takes on the responsibilities that shouldn't be undertaken by oneself. It seems more logical, but in fact there are more problems. People usually like to call it "noodle-type code".
Readability issues: In addition to achieving business functions, the code must also have good readability. Some codes do not have any comments; some code formats are not uniform; some are to show off technology, large sections of Lambda expressions (and Not to say that Lambda expressions are not good, the key is to control the depth of the hierarchy), such code looks concise, and the readability is not very good.
Scalability issue: Scalability issue is a commonplace issue. It is not so easy to achieve good scalability. Generally, there is no abstract problem. For example, if a shop displays Tabs in the store, the noodle-type code is to directly define a List. , And then add a Tab object to it, what if you need to add another Tab? Typically, the principle of opening and closing is not satisfied.
No design problem: The entire code looks relatively plain, and others can't learn from it after reading it. Generally, this kind of problem is that there is no in-depth analysis of the problem, only the problem is solved, without considering how to better solve the problem, such as whether the work of the repeated processing flow can be abstracted into a general template class, and whether different processing classes can be passed through the factory class. Obtain specific strategies, whether asynchronous processing can be processed in event mode, whether newly added capabilities can be discovered through automatic registration...

3 Root cause analysis

Next, analyze the reasons why the code is bad. There are external and internal reasons for this problem. The main external reasons are: the project is urgently scheduled and there is not much time to design; the shortage of resources and the lack of manpower can only come as quickly as possible; emergency problem repairs, temporary solutions quickly... The main internal reasons are: my own skills are low, how I have not mastered the skills, such as Lamda expressions, commonly used tools, advanced framework usage, etc.; the spirit of infinite pursuit, just complete the requirements, stability, scalability, performance, Data consistency, etc. are not considered...

The author believes that the most critical issue is the internal problems, the root causes are two: low self-demand; no feedback channel. If you don’t have high requirements for yourself, you will stop developing just to meet your requirements. It is difficult to write high-quality code. In addition, without external feedback, it is difficult to improve your skills. The author’s previous supervisor was very strict and reviewed the code written by everyone carefully. A variable name and a logical way of writing were repeatedly modified. This is actually the fastest way to improve skills.

Two ways to improve code quality

The author likes to use three methods to improve code quality: domain modeling, design principles, and design patterns. I mainly talk about how to use it.

Analysis stage: When you get a requirement, don't worry about how to implement this function. This mode is easy to fall into the transaction script. What to analyze? It is necessary to analyze the purpose of the requirements and which entities are required to complete the function. The core of this step is to find entities. Take the above example of the tab display in the shop. It has two key entities: navigation bar and Tab. The navigation bar contains several Tabs.
Design stage: After analyzing the entities, analyze how responsibilities are assigned to specific entities. This requires some design principles to guide. GRASP mentions some principles of responsibilities assignment. Interested students can go and see in detail. . Going back to the above example, there are two main responsibilities of Tab: one is whether the Tab can be displayed, which is its own responsibility, as the logic of the new Tab display is that there are new products on the store within 30 days; the other is the Tab specification The construction of information is also its own responsibility. The navigation bar has two responsibilities: one is to accept Tab registration; the other is to display. The unreasonable assignment of responsibilities does not satisfy the characteristics of high cohesion and low coupling.
Polishing stage: At this stage, choose the appropriate model to implement. Everyone will understand what it does when they see the model. For example, when you see the template class, you will know to handle the general business process, and the specific changes are handled in the subclass. . In the above example, two design patterns are used: one is the subscriber mode, which is the process of automatic tab registration; the other is the template mode, which first judges whether the Tab can be displayed, and then constructs the Tab specification information. Although the process is simple, it can also be used. The general process is abstracted out, and the subclass only needs to simply rewrite 2 methods.

The role of the three-domain model

The entry barrier for domain modeling is relatively high and contains some difficult concepts. This article will not talk about how to model (you can communicate privately). The author finds that getting everyone to accept domain modeling is far more important than knowing how to model. After you know the role of domain modeling, you will think about each Kind of way to learn. The following is a description of some actual cases experienced by the author, so that everyone does not sound so empty.

1 Simplify understanding

I joined a financial company after working for a year. At that time, I didn’t know anything about finance. After I came into contact with terms such as subject matter, debt, debt transfer, financing guarantee, and non-financing guarantee, I felt at a loss for a while, and I had to learn a lot of new things every day. content.

Two months later, my supervisor shared with us and took a ppt. It contains the entities in the domain and the relationship between the entities. I immediately understood how the entire business is. Fun. The role of the model is to simplify people's understanding of things. If we are caught in the code details at the beginning, it is difficult to see the full picture of the business, and the code is to achieve business capabilities. When you know the business, look at the code again. Much faster.

2 Unified understanding

In the company, there are research and development, products, operations, testing...When we communicate together, everyone's default language is not unified. Development often talks about how to operate this database table, and products often talk about business models...this As a result, everyone’s understanding is not uniform.

That was one night. Just after confirming the interaction process with the interactive classmates, she suddenly asked a question: Let the seller move similar pages to the same folder, is this easy to achieve? After listening, I told him that I couldn’t. When the interactive students heard that it was reasonable, why couldn’t it be realized? I started to talk to her about the current system process, and found that she was stunned, and immediately found the problem. I used the language developed to describe the problem. I immediately changed the method and found a pen and a pen. A piece of paper, I drew interactive students what our domain model is and what the interaction between business entities is. After finishing the lecture, the interactive students immediately understood the reason why it could not be realized.

3 guide design

Some students feel that domain modeling is hollow and imaginary. In fact, in addition to simplifying and unifying understanding, domain modeling may also guide code design. For example, the store navigation Tab example mentioned above, the author uses domain modeling to design Yes, although it is a small requirement, it does not hinder the application of domain modeling. In the figure below, you can clearly see that the navigation bar contains several Tabs, and one Tab contains specification information and click operation information. After the business model is drawn, the corresponding code will also have the above concepts, and there is a mapping relationship between reality and code. The model is the code, and the code is the model. If your model can’t reflect reality, the module can only be considered a garish. Teacher Fan Gang summed up three sentences on this: What things are in reality, and what objects are there; what are the behaviors of real things, and what methods are there to correspond to the objects; Real things What is the connection, and what is the connection with the corresponding object.

The underlying logic of the four design principles

1 SOLID

For design principles, we generally talk about SOLID, which contains five design principles:

Single responsibility principle: A class should have one, and only one, reason to change, a class can only be modified for one reason.
Principle of opening and closing: Entities should be open for extension, but closed for modification, open for extension, and closed for modification.
Richter substitution principle: Functions that use pointers of references to base classes must be able to use objects of derived classes without knowing it, subclasses can replace parent classes.
Interface isolation principle: A client should not be forced to implement an interface that it doesn't use. The client should not be forced to implement an interface that it doesn't use. The interface should be as small as possible.
Dependence inversion principle: Abstractions should not depend on details. Details should depend on abstractions, abstractions do not depend on details, and details depend on abstractions.

2 Why should there be design principles

We have basically heard or understood about the SOLID principles, but why do we have these design principles? In order to answer this question, we derive from the goal. The goal of software development is high cohesion and low coupling. This sentence is often difficult to measure. For example, to answer: What is high cohesion? What is low coupling? How high is high cohesion? How low should low coupling be? These four questions are not easy to answer.

Think about it in reverse, what if our code is not highly cohesive and low-coupling? That is, the scene of low cohesion and high coupling. If the code is low cohesive and highly coupled, there will be changes to one logic, which will lead to multiple code changes. This is not what we want to see, especially when modifying the original logic, it is easy to have bugs, such as before the author Modifying one problem and changing the rules in another place seems to be no problem, but it affects a business side. This is why the opening and closing principle proposes to close the modification. Modifying the original logic is risky.

The ideal situation is that the modification is only limited to a certain local scope, so that the scope of impact is limited, so we require a single logic, not containing multiple responsibilities. Think further down: Why do we want to modify it? In addition to bugs in the original logic that need to be repaired and code refactoring, an important reason is that the requirements have changed, and the changes have caused us to modify the original logic. If there are no modified scenarios, there is no such thing as high cohesion and low coupling. Therefore, the underlying logic of the design principle is to allow the software to better respond to changes and reduce costs and increase efficiency.

3 How to practice

Design principles are just a guideline, and there is still a long way to go. Some students say that I understand the design principles, but I still can’t apply them. In fact, the essence of this problem is that you have no understanding of the underlying logic of the design principles, and no insight into the focus of change. How to solve this problem? The answer given by design patterns: find changes, encapsulate changes.

The essence of five design patterns

Please refer to the article written by the author before for the design pattern.

Six case practice

When the called interface has different implementations (the input parameters, output parameters, and interfaces are different), a layer of anti-corrosion layer needs to be abstracted. How to implement it? Next, let's look at two cases respectively. The two cases have different focuses. One is the abstraction of partial behavior, and the other is the abstraction of partial structure.

1 Store brand query

The store needs to query the store brand information, but the interface of Lazada and AE is different, how to abstract the anti-corrosion layer?

First of all, the simplest solution is easy to think of, which is to define an interface, and then there are two implementations. Its advantage is that the level is simple, and everyone can understand it after reading it. Its shortcomings are also obvious. In the two implementation classes, the responsibilities are not single, and two responsibilities are assumed: one is to realize the query of the store brand, and the other is the data conversion.

According to the shortcomings mentioned in the first scheme, it is easy to think of using the adapter pattern to split the previous class into two classes: one class is to call the corresponding brand service; the other is to do data adaptation and conversion. However, there is another disadvantage of the method at this time. In the internationalization scenario, the isolation between multi-tenants must be considered. For example, Lazada has multiple sites. How to achieve more fine-grained differences? Scheme 3 is based on these thoughts.

The third option is to introduce a multi-tenant framework, which can support multi-tenant scenarios.

2 Store coupon query

There is a "golden oil" development model: assembling parameters, calling interfaces, and parsing response results. You will find that this model is too versatile and suitable for all scenarios. This development model is also "transaction script mode" or "noodle type" Code".

For the coupon query case, use the domain modeling model to first think about what entities are there. The essence of coupon query: query through xx conditions to return a set of coupons that meet the conditions. For coupons, two types of information are essential. One is the specification information of the coupon, such as the name of the coupon, the discount amount, the validity period, etc.; the other is the restriction conditions of the coupon. When inquiring, whether to check store coupons, fan coupons, or commodity coupons... Therefore, two abstract coupons are divided: one is the coupon query request; the other is the coupon specification entity.

If you follow this design, there is a disadvantage that the business side understands that the complexity will increase, it is a low-level implementation, and it is not simple to use. Coupons focus on product delivery rather than just function delivery. Therefore, the product components are abstracted on top of the underlying implementation, so that the business side is relatively simple to use.

FURTHER READING
▶ Walkthrough007 - https://www.walkthrough007.com/

What is the resume of an excellent front-end development engineer?

Jerrold.Lee — Thu, 26 Aug 2021 01:24:20 +0000

A resume is not just a resume, its important role is to demonstrate ability ! ! !

Recruiting in Ali all year round, screening all kinds of resumes. Every recruitment season, the process of screening resumes and interviews is very energy-intensive. Of course, one of the reasons is that I want to recruit very good people. I would rather spend more time. On the other hand, in addition to the unqualified resumes, there are many resumes that are unclear and have to be confirmed repeatedly during the call. At the same time, in order to take into account the candidates’ feelings, they have to pretend to be very professional and do some interaction with him. A large number of people were sifted out, which encroached on a large area of my time. In order to improve the efficiency of these people's resume (interview), here are some suggestions:

First, the self-recommended resume must be signed

After the recruitment information of the recruitment season is sent out, a large number of resumes will be received in the mailbox, and most of the email titles and attachments are basically unsigned. After the resume evaluation + contact, not every resume will be written in a complete evaluation entry system, especially some inaccurate resumes.

I can’t remember which email contains whose resume, and then go through the attachments one by one (some are PDFs, some are Word, some are HTML, some are simply a zip, some are a URL, and some simply paste the resume in the body of the email... .) It is very time-consuming and inefficient to evaluate the original evaluation. Even if I finally turned to the resume I was looking for, my points were already greatly reduced. Therefore, if you recommend your resume, you must write clearly in the email title and the file name of the resume attachment, who, what position you are applying for, and the recommended level (junior, senior, expert). Anyway, I don’t have to rename it after downloading the attachment.

Second, you must have a resume in word or pdf file

Nowadays, a lot of people's resumes are directly posted online, or in HTML. It is very difficult for me to deal with this kind of resumes. Alibaba’s internal recruitment system supports word and pdf formats the best. When I entered the system, many fields were directly read by the system after uploading the attachments. The HTML resume support is the worst. After uploading the attachments, I need one more. It’s completely meaningless to fill in by hand, and it’s totally meaningless to spend energy on this. And from my experience, what can be expressed by a page of HTML resume source code is really limited. So word and pdf format carriers are enough, so spend more energy on resume content.

Third, the resume must show bright spots, preferably with works

The front-end technology is also very differentiated now. If it is not strictly divided, there are NodeJS, H5, Hybrid, architecture and business research and development directions. Now there are many libraries and specifications, but the difficulty and technical baseline of each branch are similar (for example, the cost of reaching senior It takes about the same time), so the full-stack generalist is good, it is a bit too difficult to go deep in each direction, but at least one direction should be very precise and very deep. So highlight this strength in your resume. In fact, the "skills" part of 90% of resumes is almost the same, and they almost list the technologies used in the front-end, meaninglessly occupying the prime location in the resume.

Therefore, since the full stack is not easy, it is better to highlight and bold the language or technology that I am best at. During the interview, I will directly bypass the others and focus on this "highlight and bold" part to do some technical probing. , In order to guide the interviewer to ask what you are good at, it is more conducive for you to use your strengths and avoid your weaknesses.

What do you usually do when you get to the bottom of technology? Look at the work! If you are good at Node, just take a look at the module submitted on NPM, install it and demonstrate it, and talk about the core code. If it is a component, just look at the Demo directly and talk about the design and packaging ideas. If it is a set of scaffolding tools, draw the architecture diagram directly, explaining the principles and applicable scenarios. If it's a project, then show the Release email you sent as a PM! The works are not only these, but also technical patents, design schemes, successful cases of leading people, successful team building cases, etc., as long as the content is substantial and grounded, and the pulse (it can be a code or one thing) is clear. During the show, the eyes gleamed and the stars flew around. This is the right feeling. Therefore, you should include these well-reserved works in your resume, and prepare them to show off during the interview.

Fourth, highlight key points and demonstrate ability

Now it is not difficult to recruit a person who can work, but the difficulty is to recruit someone who can solve the problem. In particular, business research and development such as Ali requires not only to get demand from the business side, but also to be alert to demand traps, accurately identify rigid demands, formulate plans, push for implementation, and release results. Therefore, the skills required to deal with each of these aspects are best shown in the resume. Specifically, when describing each project, you must not only have the background and process, but also the results you brought to the project . For example, describe the project like this:

I refactored the XX project and used the XX technical solution to overcome the difficulties of XX. In the end, changes in the requirements of XX can be digested quickly and quickly, with rapid R&D, rapid launch, and standardized data collection. The cost of research and development is huge. Decrease, data accumulation grows rapidly, such as XX, and finally began to be promoted in the XX product line.

During the interview, this description can easily lead to targeted topics to talk about. It is precisely because of these foreshadowing in the resume that it can save a lot of interview time and make judgments faster.

In contrast, this description is not good:

The front-end research and development of the XX project uses AngluarJS, and the entire project is completed independently, including the acceptance and charging of the entire Boss system, merchandise retail, PHS SMS group sending, cable television agency charging, salesperson/business point checkout and other modules.

This description only conveys one message, that you have used AngularJS. As for how many types of technology we were faced with, how to choose AngluarJS, how to couple these system modules based on AngularJS, did it involve front-end architecture, how deep is AngularJS used, what is the division of labor among project members, and how to develop in parallel? What problems have you encountered that you think are valuable, and proposed a solution to this, is it a code solution or an organization solution? This process will take a long time to figure out the question and answer during the interview. If you can’t ask, you will basically skip it. If it is expressed in your resume, your mind will be awkward, and the interview will not be procrastinated, and your ability evaluation will naturally be very high.

One more thing. Many people have the habit of blogging and writing summaries. This habit is very good. If a summary can be combined with the project in the resume, it would be even better.

Fifth, the all-green Github submission record

Attach Github to your resume. It’s best to submit a record where it is very green. If you go to the Github homepage, you want to click on the project list and find the project to read. If you see the kind of long-term maintenance, the Readme is clearly written, Write "reprinted with an indication of the source" in a serious manner, basically grab the phone and start the chat, and the result is basically not bad.

Sixth, other concerns and non-concerns

Attention: The reasons for resignation every time you change jobs, quantifiable work results, and projects that can represent your highest level should be written in detail, marked in red and underlined in bold, and emphasized in your resume.

Don't pay attention to: certificate, level four or six, familiar programming language (if you are not proficient, don't write), what you are not good at, personal profile.

Seventh, typical problems

I will definitely ask some questions about the bottom of the technology. In addition, everyone in the interview will ask:

Which project satisfies you the most and represents your highest level? How to do it
The one (technical) difficulty that impressed you the most, which caused you to deal with it for a long time, how did you solve it in the end? What's your experience?
For the project (or product) you have done for the longest time, what problems do you see in this project and what can you do?
What can you bring to our team or product?

These problems are not hard and fast. They mainly depend on whether they usually think about something other than the technology, especially on the basis of the basic shape of Ali's many BU products. Trial and error, innovation, efficiency, refinement, and direction are needed. In this case, only having the technical ability (to complete rigid requirements) is no longer enough, and dialectical execution is needed.

finally

Of course, the above are all suggestions. Whether you think it is useful or not, stick to a principle, that is, "Resume is not just a resume (what you have done), its important role is to demonstrate ability (what you can do well)!! !"

FURTHER READING
▶ Walkthrough007 - https://www.walkthrough007.com/

Since the front-end has already been rolled in, why is the company still unable to recruit people?

Jerrold.Lee — Wed, 25 Aug 2021 04:54:31 +0000

From 15 years ago, artists and cut figures with a monthly salary of 5k, to today's front-end experts, architects, front-end managers, and business leaders with an annual income of over one million, the front-end has been rolling out.

Let's make the conclusion first: the front end enters the deep water zone and is rolling out. The harder the rolling, the harder it is to recruit people.

The greater the gap between the capability model of large factories and small and medium-sized factories, the hundreds of thousands of front-ends that have grown from small and medium-sized factories, the more difficult it is to enter large factories. It is better to recruit a P5+ who has been working for 3 years than to recruit a fresh graduate. The high potential of the company eventually led to the fact that Dachang has never recruited suitable people, and there are a large number of intermediate front-ends on the market, and they have not been able to enter the big factory, so they mistakenly believe that the front-end is very inward. The development of front-row groups in the industry has led to deteriorating competitiveness.

If the evolution of technology and industry changes are regarded as a history book full of changes, and the front-end industry is included, there are several common historical viewpoints:

The front end is an inconspicuous small technical branch. It doesn’t matter much to me. I just want to concentrate on writing code to make money, and I’m not too interested in it.

The front-end threshold is getting higher and higher, and it’s becoming more and more unfriendly to newcomers, and the ceiling is also particularly low.

In the past ten or so seniors, they have explored and raised the ceiling of the industry. I am very fortunate to enter the industry at this time. There are a lot of community resources and opportunities....

Individual struggles and the overall environmental development stage of the industry are inseparable. Talking about the other without any one is divorced from reality :

For example, in my elder generation, I will hear older people complain that hate did not move their family to Beijing and Shanghai in the 1970s to enjoy various household registration dividends and demolition benefits. There are also some younger elders who complain that hate is not there. When Deng was drawing circles in the South, his family went to Shenzhen to start a business. There were also some complaints from his older brothers. They hated that he did not learn economic knowledge and trade stocks to realize the freedom of wealth when the stock market and the Internet started in 2000. Some high school children's shoes of my age hate not having a good study and college entrance examination, which leads to no chance to enter a better platform and struggle. I also heard complaints from front-end elderly people who are slightly younger than me, and hate that they were not born 30 years earlier and catch up. Since the reform and opening up, I was not born 20 years earlier and caught up with the first pot of gold on the Internet. I hate myself for not doing a good job of technology in the early years and missing the rapid development dividends of China’s mobile Internet. Today, even if it is a P7, I have already earned one million a year. I have also heard some younger front-end newcomers complain that they hate that they were not born 10 years earlier, so that they can enjoy the dividends of the front-end slash-and-burn cultivation 10 years ago. Just build a wheel and join a big factory to be promoted to an expert. I already have a P8 today.

NS...To this day, some of these opinions can still be heard among people of the same age, and the hidden voices behind them are like the dividends of a certain era node, and others can get it without any effort. It seems that as long as you choose the right one, everything will go smoothly. In a chapter, I don’t know that behind the choice is continuous effort. Although luck plays a very important role in this process, the decisive factor is your level of effort and the improvement of your ability and cognition brought about by your effort, which in turn leads to Here comes more forward-looking choices and the ability to make judgments. This is a positive and progressive relationship. A better choice leads to better results of efforts, and stronger efforts lead to better choices the next time . This is especially true for ordinary people who don't have much ambition.

Behind the choices and efforts are 80 years since the end of World War II, 30 years since the end of the Cold War, 30 years of China’s reform and opening up, 20 years of China’s PC Internet development, and 10 years of rapid development of mobile Internet and industrial Internet, the entire complex global economy has become refined. In all walks of life brought about by the division of labor, each person’s own life opportunity has changed everyone into today’s front-end. The group of the oldest front-end practitioners, their front-end development experience, is nothing more than a dozen years. Talking about dividends, this is just getting started, so how come "Since there is no future, it is better to be lazy as a teenager"?

Therefore, what we are talking about above is about an engineer’s basic judgment and self-positioning of an industry. The more emotional and labelled this judgment and positioning, the more difficult it is to sort out his career plan and see all the difficult things in the world. The first reaction is to use the word "juan" to escape things, as if as long as the situation in front of you is defined as a "juan", if you can't get a good result, it is controlled by the "juan" instead of being determined by yourself. On the contrary, if this judgment and positioning become more objective and rational, and the more able to handle a few kilograms of one's own weight, the more able to settle down and endure loneliness .

Try not to be labeled with rhythm, especially not to be strayed by labels with pessimistic negative energy. It is an ability and a kind of deep thinking that newcomers need to train. This kind of thinking must be deliberate as they grow older. Only in this way can we still have the underlying motivation to continuously update our existing knowledge system, the so-called incremental value learning rather than the consumption of the stock knowledge structure, in the middle age when the three views are stable .

There is a huge difference in cognition and values between people. What we need to do is to understand the fact that this difference exists. It is not based on my will, and just continue to concentrate on what we are doing, continue coding Continue to preach, continue to write, continue to build a sharing platform, continue to do community exploration and product thinking.

So what I’m talking about here is actually talking about the engineer’s self-worth identity, whether you are driven by responsibility or curiosity, when you are a front-end, you only need to identify with your current engineer status and your current job attributes and responsibilities. , And when the matter of writing code and technology is pushed to the extreme, whether it is to do a line of love, or love to do a line, the ability to "do this line well" will become your core competitiveness. In the impression of the label, you are just a material and sample, but in your personal world, giving and gaining are all you have .

However, if responsibility or curiosity is scarce, it is difficult to recognize the value of oneself as an engineer, and it is also difficult to recognize the value of peers, which is what we call "maybe in the wrong line", you can use one or two Years ago, I actively made reserves and changed jobs to do what I was better at, because the threshold for front-end engineers is indeed rising. Otherwise, how is he different from the "artist" of earlier years, and how can he be called an "engineer" Well, because the engineering field itself has a certain degree of academic research, it is a cross-field comprehensive ability practice, and its requirements themselves are high.

So more than ten years ago, the degree of "artist", "refactoring engineer" and "page UI engineer" was generally not a bachelor's degree, but nowadays, 985 and 211 are flooding in, because the process of this industry moving into the deep water area requires academic , Research-oriented engineering talents, such a talent pool is far from enough, but the income ceiling of the front-end industry has long exceeded one million. A front-end who has worked for 7 years has a capacity of 2-2 bytes, and there is a high probability The annual income can exceed one million. If Byte is listed in the future, the options in hand will be spread every year, and the annual income will even exceed 2 million. Such a high income ceiling has long raised the front-end industry ceiling. So when I complain about the ceiling of children’s shoes, I can ask myself this question: Do I first worry about whether I can break through my ceiling and achieve an annual income of 2 million in 10 years, or is it because I have been worried about another "possible" existence after 2 million. A higher ceiling, so today I lost my fighting spirit and passion, so I no longer try to break through my ceiling?

The above content is written very specific in order to take care of newcomers. So much verbosity is just to let everyone know that the front-end industry has been developing rapidly in the past ten years. From a few thousand people to hundreds of thousands today, the development in just ten years has not only not reached the time of internal roll-out, but also in the period of crazy roll-out expansion, which has rolled out more employment opportunities and rolled out higher industries. Ceiling. Regarding this point, once I watched the live broadcast of Ant’s school recruitment, I also heard that Yu Bo expressed similar views, which are very similar to my ideas. I can’t remember the original words. I will talk about my own understanding, that is the front end. It is indeed rolling, but it has been rolling out. If there is no such a roll, we are still the company's art/page boy today. The income is lower and the ceiling is lower. This roll can be viewed like this:

Roll up, roll up to data processing, business decision-making, visualization and analysis, roll up to PRD, straight out of the page without code...
Scroll down to the R&D tools and interface generation process, engineering, intelligence, and large-scale concurrent service orchestration capabilities...
Scroll to the left, scroll to cloud componentization, design asset management, design productivity breakthrough, design low-code construction...
Scroll to the right, scroll to testing, security, usability, stability and R&D platform and operation and maintenance methods throughout the R&D life cycle...

The front-end has such a volume, but due to the characteristics of the front-end community information dissemination (the popular science and collection-oriented articles are more popular), and the lack of corresponding sharing platforms and mechanisms, a large number of excellent front-end teams have explored results. It’s well known that people mistakenly think that the depth and breadth of front-end technology is nothing more than this. That’s why I set up the semi-commercial and semi-community co-construction organization that the front-end talked about early to show the truth. The topics involved are front-end management, Front-end infrastructure, visualized site construction, low-code and intelligent construction, front-end monitoring, front-end construction, componentization and cloud assets, online documents, data visualization, data reporting and analysis, cross-end and cross-stack, micro front-end, front-end framework, CI/ There have been more than 140 sharing sessions on CD Pan-R&D platforms and other topics, as shown in the figure:

Although many fields have not yet been rolled out, it is precisely the technical people in this industry who are frantically expanding the entire front-end territory... The territory is expanding, we can choose to join, we can choose to watch... It is our own choice. Everyone’s career path is flowed out by himself. There are not only the general trend of the global political and economic structure, but also the general direction and basic rhythm of the current industry. In this process, it depends on whether you have the courage and execution ability. I dare not take one step at a time to rewrite my own trajectory .

You should always look up, look up, look down, look forward, look back, look out, and look in. These are all new worlds brought about by changes in cognitive methods, such as the Guangdong-Hong Kong-Macao Greater Bay Area, RECP, The China-EU Investment and Trade Agreement, as well as the possible future CPTPP, China-Japan-Korea Free Trade Area...Don’t be afraid to miss the previous dividends. Today and today, the dividends are still everywhere, or the size of the dividend has nothing to do with you, whether to let yourself The ability to grab dividends is related to you. The height of the front ceiling has nothing to do with you . Whether you can break through your own ceiling is related to you .

Finally, how many opportunities have nothing to do with you, whether to break your past perception of opportunities, re-understand and grasp it is related to you, so for the front end, it has nothing to do with you, and only you are closely related to you. The process of breaking the circle personally, this process is of little importance to others, but it is almost all to you .

FURTHER READING
▶ Walkthrough007 - https://www.walkthrough007.com/

Talking about "Anti-routines" in Management

Jerrold.Lee — Sat, 21 Aug 2021 09:55:45 +0000

After doing management for so many years, I found that "management" is a very complicated word. Why is it complicated?

First of all, most people agree that management is indispensable in an organization.

However, when it comes to management, the first thing that comes to mind is some negative words.

"Routine" should be one of the most typical evaluations.

Don't believe it? Let me give you a few examples

First part
Routine One
Someone once asked me on WeChat:

The morale of the team has been low recently, and many people leave after get off work. How can we make everyone willing to work overtime?

Quite common, right.

I asked the person how much he recognized the job, and the answer was just to eat. I don't want to work overtime, but I can't stand the pressure of the boss.

In this example, the manager's attention is not on how to find the reason for the low morale, but on the hope of fooling team members through "talking".

Routine 2
If you want to select "What scene makes managers feel the most difficult?" 』—— Interviews with low-performing employees and dismissed employees must be on the list.

So some people choose to say:

Actually, I don't want to fire you either. This is the above decision. I can't help it.
In fact, I don't want to give you low performance, but the company requires someone to be the bottom, and I can't help it.
Everyone takes turns to get low performance. This time you take it first, and next time I will improve your performance.

Some "good-hearted" supervisors are always entangled in their hearts when they have to play the role of "villains", even with a deep sense of guilt, and feel that they are "executioners".

All the above statements seem to be acts of "goodwill" sympathy, comfort and even compensation, but in essence they are also a routine. The purpose is to shirk the responsibility that one must bear as a manager and reduce the inner anxiety and sense of debt.

In this case, the most important purpose of the interview: the analysis of the employees’ problems, and the exploration of opportunities and measures for future corrections, are not important in the minds of managers.

The moment the manager walked out of the meeting room, what the manager thought was definitely not "great, we finally reached an agreement on the issue and action", but "thank God, Ta finally accepted this result".

Routine Three: Interest Exchange
In the promotion season, the biggest headache for managers is the question of who should go to with a limited number of places.

The backbone is promoted and resigned. I want to take advantage of this promotion to promote Ta to keep him. Is it okay?

That's correct, isn't it?

If the backbone wants to resign, of course they have to do everything possible to keep people.

The heart is good, but the means are wrong.

Whether it is a salary increase, bonus or promotion, the original intention is to motivate.

However, in practical applications, these incentives are often used by some supervisors who usually neglect team building, personnel training, and employee care, or by inexperienced young supervisors, as a "trading bargaining chip" to quell employee dissatisfaction.

It is not difficult to explain why many technical people are determined to leave no matter how the leader promises to increase the salary or even promotion after resigning. Because the other party feels in his heart: Your move is just a routine, just a slow strategy.

Even if it succeeds by luck, the company's system has lost its true meaning in the eyes of employees and has become one of the means of bargaining next time.

Part two
Sometimes I think about it, this is really the "sorrow" of management and managers.

Obviously, management studies are the propositions of "how to make enterprises, organizations, and individuals better", but in practice, it always becomes a "thick black school". Managers have become a group of "treacherous and cunning" people in everyone's minds.

Where is the problem?

A few days ago, I finally found the answer after reading the book "Knowledge and Action: The Road to Management of Technical People". There are a few key paragraphs, I excerpt as follows:

"Management methodology exists for the purpose of good management. As a whole, it belongs to the category of "means". Since it is a means, its good and evil lies not in the management methodology itself, but in the original intention of the managers who use the methodology." "Knowledge and Action: Technicians" The Road to Management, page 279

"Most of the managers do not have character problems, but lack of knowledge-they don't know how to use management methodology instead of "routing others"." "Knowledge and Action: The Road of Technical People's Management" page 279

In fact, there is only four characters from "Tao Lu" to "Non-Tao Lu"-sincerity and righteousness.

Specifically: What you think in your heart and your words and deeds are unified, not contradictory. It is precisely because of words and deeds against your will that the methods and means you use become "routines."

Talking about skills but not energy in management work is like having only tricks without internal strength, and its management skills cannot be strengthened. "Knowledge and Action: The Road to the Management of Technicians" page 279

Most of the middle- and basic-level managers (including myself) of enterprises are from wild roads. When we approach management, we don't start with learning "role recognition", but start with imitating "management skills".

In the above three cases, the managers used all "management skills", and their hearts, words and deeds were inconsistent:

I am disgusted with overtime and have to do it under pressure.

Unwilling to face the fact of dismissing employees, forced to do it due to duties

May not feel that the backbone is worthy of promotion, because the situation has to do

So, we saw an interesting phenomenon:

Originally, the manager's attention should be on how to solve the problem, but in the end the manager's attention has become: how to solve the person who caused the problem.

At this time, the manager had already unknowingly walked in the direction of the "routine".

What should I do then? The answer is given in the book-sincerity and righteousness.

A manager said: I did what I should do, I have a clear conscience! What he said "what I should do" is actually judged from personal values, which is not necessarily the same as "I did what I should do as a manager".

Starting from the role of the manager, do what the manager should do instead of personal preference.

For example, sometimes from a manager’s point of view, it is necessary to persuade an employee, and you may not like to do it personally, but you still need to make a choice based on the manager’s role to be considered righteous. "Knowledge and Action: The Road to the Management of Technicians" page 280

To put it simply, it is to: be clear about the role of the manager, start from the role of the manager, think about things and do things

Part Three
Take the above case as an example:

Case 1: The responsibility of a manager is neither a "microphone" nor a "supervisor". What managers have to do is to find the inner driving force for themselves and the team, not how to fool everyone into working overtime.

Case 2: One of the responsibilities of a manager is to "correctly evaluate everyone's contribution and decide whether it is suitable for staying." You have your brotherhood, but you should look at this issue more from the perspective of team development. You don't owe the other party anything, let alone a villain. What the manager has to do is to analyze the problem honestly with the other party based on the facts and find ways to improve, instead of just thinking about how to make everyone "feel better in their hearts".

Case 3: One of the responsibilities of managers is to use the power and resources in their hands to create a better environment for competition and cooperation, rather than using these as bargaining chips to quell problems. What managers have to do is to review whether their usual work is in place.

As the book says:

If we manage with a sincere and upright attitude, the methodology we use will have its own "anti-routine" function. On the contrary, if you fail to be sincere and upright, all methodologies are fake and fancy methods, which will eventually put the managers themselves in a passive position.

Encourage it!

FURTHER READING
▶ Walkthrough007 - https://www.walkthrough007.com/

DEV Community: Jerrold.Lee

My New Product PinterestVideoDownload.org launched!

200+ Best Platforms to Promote Your Startup for Maximum Visibility

🚀 Why Platform Promotion Matters

🏆 Top-Tier Platforms: Your First Priority

1. ProductHubX - The Rising Star of Product Discovery

📈 The Complete List of 200+ Platforms

Tier 1: Major Discovery Platforms

Tier 2: AI & Tech Directories

Tier 3: Community & Social Platforms

Tier 4: Specialized Directories

Tier 5: Emerging Platforms

Tier 6: Industry-Specific Platforms

Tier 7: Developer & Tech Communities

Tier 8: Additional Discovery Platforms

Tier 9: Niche & Specialized Directories

Tier 10: Community-Driven Platforms

Tier 11: Review & Rating Platforms

Tier 12: Startup Ecosystems

Tier 13: Design & Development Communities

Tier 14: Marketing & Promotion Platforms

Tier 15: AI-Focused Directories

Tier 16: Global & Regional Platforms

Tier 17: Specialized Tool Directories

Tier 18: Emerging & Niche Platforms

Tier 19: Additional Discovery Channels

Tier 20: Final Tier Platforms

🎯 Strategic Submission Tips

Phase 1: Start with Top-Tier Platforms (1-20)

Phase 2: Expand to AI-Focused Directories (21-80)

Phase 3: Community Engagement (81-150)

Phase 4: Comprehensive Coverage (151-200+)

📊 Expected Results

🚀 Ready to Launch?

How to break through the exhausted front-end business?

The dilemma of the business front-end

1. The front end of the business is "very busy"

2. Is the front end of the business a "resource"?

3. Want to make a breakthrough in the front end of the business

Understand the business

1. Business and demand

2. Why should the front-end learn business

3. Do you understand the business?

4. How to learn business?

Boost business

1. Thinking

2. Communication

3. Technical planning

4. Stand on the shoulders of giants

Technical depth

1. Technical knowledge and technical ability

2. Cultivate technical vision

3. Technical depth

4. Win-win technology and business

finally

Methods to improve code quality: domain model, design principles, design patterns

A root cause of poor code

1 Embodiment of poor code

2 Problem summary

3 Root cause analysis

Two ways to improve code quality

The role of the three-domain model

1 Simplify understanding

2 Unified understanding

3 guide design

The underlying logic of the four design principles

1 SOLID

2 Why should there be design principles

3 How to practice

The essence of five design patterns

Six case practice

1 Store brand query

2 Store coupon query

What is the resume of an excellent front-end development engineer?

Since the front-end has already been rolled in, why is the company still unable to recruit people?

Talking about "Anti-routines" in Management