This article summarizes some practical ways to apply architecture to help you.
Here’s a good way to think — structured thinking
Take the structure of things as the object of thinking, to guide thinking, expression and problem solving a thinking method.
3 elements:
- thematic
- group
- The progressive logic
Give examples of foods you like, and often sporadic divergent thinking
After structured thinking
As a programmer, I recommend this way of thinking.
The body of the
architecture
My understanding:
Architecture is the ability to solve complex problems while identifying problems with technology and serving technology.
A lot of people always misunderstand that the front-end architecture should be engineering, automation or even writing back end, these certainly count, but the architecture is all around you, need to change the perspective of the problem.
Going back to the above understanding, solving complex problems, all the above content is the way to solve complex problems, first need to dig the problem.
The product manager
Found the problem
Trajectory of user behavior, optimization of experience (buried points, special UI for business units) -> engineering
In fact, the front end is closest to the user, and these things may be seen more from the programmer’s perspective than the product manager.
Business architecture
Take yourself as a user, deeply use the same kind of business functional products, some general modules can be stripped, some modules can be optimized.
Don’t understand? Let’s take an example
E-commerce and healthcare have different priorities.
E-commerce industry: interaction, high concurrency, marketing…
Medical industry: Compatibility, fast operation, professional medical process…
Of course, the actual situation is much more complicated. For users (doctors), it is necessary to make the operation simple while ensuring the details of the form function. Similar functions such as linkage, search and automatic saving can be made into tool modules (packages) for prescriptions.
Take single sign-on (SSO) as an example. When a doctor clicks submit after going through this complicated process, he is redirected to go out because of the failure of the login state. At the same time, all the contents filled in after login are gone.
The front end
Found the problem
Observe/investigate pain points in colleague development (repetitive work, areas where improvements can be made) -> automation
Single sign-on needs to jump not good? Direct development of a popover single sign-on package, you can choose to have UI and no UI.
Why do you do that? The front end needs personalized place is very much, no UI support user (technology) and designers to provide their own interface, for the development of good tools must be able to support their own magic change ~~
Devops, scaffolding, it’s the same thing, all of these tools can improve efficiency but you have to leave a hole for the user to use.
Habits kill the conventions of these new architectures and make it hard to use these tools when developers are not aligned?
Ensure these architectural output stable to use first, secondly to do quantitative, when your architecture effect can quantify exactly, it would be easier, because the content of the quantitative allows your users to easily get KPI after the use of your proposal, this time to a new architecture of quantitative solution/platform (there are some connections between architecture).
The rest, it’s time to test your propulsion…
advance
Here is not stingy, the essence of this article, some personal experience summary
The product itself
The product itself has the ability to solve complex problems, so it can be said that the promotion is smooth. Sooner or later, users will use the appropriate timing.
Bundled products
Take single sign-on bullet box as an example. The unified UI framework, polar verification, and even cross-domain and cross-level communication of IFrame are all strucable. These things can be completely linked together.
So, don’t think you’re doing something that’s one-dimensional, that’s just another architectural product when you put it together.
Win-win strategy
Most of the time, you can’t do it by yourself. For example, Devops needs operation support, business architecture needs product help, node layer/micro service needs back-end masters’ guidance, etc. I think to learn these knowledge, it is better to directly let them join you.
Put your Idea out and let professional people do professional things. Meanwhile, you can be responsible for the after-sale of products. You only do the output of the architecture and do not have to be responsible for the products.
You may ask why you are in the aftermarket, one is to learn the technology behind it by troubleshooting problems (there are more bugs than you can develop without understanding how they work), and the other is to collect user feedback.
When you get enough feedback, you’ll know if the build is successful, where to go for the next iteration, etc., and you’ll be a product manager.
Dead to tie up lousy dozen
This is not a derogatory term in terms of advancement. Expanding your social circle and practicing your communication skills are all necessary steps in the advancement process.
In addition to the cheeky sales pitch, you can use the path around you to be “haunted.”
- Use the company’s community, forum, monthly, etc. (if not, you can consider building your own)
- Use such platforms as Nuggets and public accounts to publish in the company’s technology group
- Hold an internal “launch event”
- AD placement in internal architecture systems/tools/packages
- From top to bottom, convince the leader, then create a group about the architecture and explain what the architecture solves (when one leader agrees with you, it’s relatively easy for other leaders to join).
- face scan
And finally, one day you’re ignoring me, the next day you’re fraternizing over a Starbucks.
Send resume to hit my mailbox [email protected]
Quality four consecutive, like, attention, forward, comment
Learn more, pay attention to technology public number: IHAP technology black hole!!
