Little red book - Notes inspiration - project summary

One 、 Business Introduction

Note inspiration , It is a function of the Little Red Book Creator service team , The purpose is to provide reference and guidance for users to publish notes .
Note inspiration is updated every Friday at 8:00 , The operator should edit the notes to be displayed before 8 o'clock on Friday , After 8 o'clock on Friday, it can be displayed online .
(ps： This function is no longer maintained by me , So I'll just talk about my business experience in charge of development )

Two 、 Technical solution 1.0

1.0 The scheme , In fact, it is very simple logic ： Operational configuration , Then take effect at the point .
After the actual launch , Because before the time , There is no way to confirm the display effect online , Therefore, the operation must be updated at 8 o'clock on Friday , Go online to confirm , Whether the configuration is effective , Every time I make my heart beat （ Because there is something wrong with the launch ）.

1.0 After the version of is launched , The following problems have occurred one after another ：

• Back end bug, After the configuration data takes effect , Some exceptions are not handled correctly by the backend ‍‪​‭‪‪‬⁣
• front end bug, After the configuration takes effect , The front end treats video notes as graphic notes , As a result, the video notes cannot be displayed ‍‪​‭‪‪‬⁣
• After the launch , The operation found that some notes were not compliant , So I didn't show it ‍‪​‭‪‪‬⁣

3、 ... and 、 Technical solution 2.0

2.0 The plan , comparison 1.0, Two optimizations have been made ：

• Configuration check ： The day before each configuration goes online , Check whether the operation is configured , If not configured , Send a reminder to the operation . So as not to worry about the operation and forget the configuration .‍‪​‭‪‪‬⁣
• preview ： All configurations , You must preview before you can go online .（ About how to preview , I've written an article before ：‍‪​‭‪‪‬⁣ Preview what to do ？, So when drawing a flow chart , It directly simplifies , I won't talk about how to implement preview anymore ）.‍‪​‭‪‪‬⁣

Four 、 Timing task

Note inspiration , It will be updated every Friday , Send mass messages to specific people .
After the scheduled task execution ends , The implementation report will be sent to relevant personnel , The general content is as follows ：

 towards x Subscribe to note inspired users to send messages , Current timestamp :xx,  Number of users sent per round :xx
 towards x Users who subscribe to note inspiration send a message to end , Current timestamp ：xxx,  experiment 1 A total of :xxx,  experiment 2 A total of :
xxx

Fortunately, the message was sent with detailed numerical parameters , The product found the number of users actually sending messages , Not in line with expectations , After my investigation , It is found that the third-party components that the back-end depends on exist bug.

5、 ... and 、 Review summary

1. Configuration type requirements , Preview required , Can not be directly effective online . In fact, in the initial technical proposal , You should add language and configuration checks , At worst , The first time something went wrong online , Should have reacted .
2. Scheduled task execution , An informative and complete execution report must be sent to the interested parties , Make sure the task is being performed , And execute correctly .
3. Key time points , Notice prompt should be added , Avoid forgetting .

( In fact, the inspiration of notes has been done for a long time , But once you write a summary , There is not much to write , Summary ability needs to be improved )