Daily Todo List

7.10

  1. MongoDB learning of CRUD.(done)
  2. Refactor of touchweb about rental parts.(done)
  3. Move data to gitlab.()
  4. Update romar-ng wiki.(wait)
  5. Learn about viki(platform of romar-ng management).(done)

7.11

  1. Set kpi guideline.(wait)
  2. Refactor of touchweb about rental parts.(done)
  3. Give over charge of community module.(done)
  4. Play a football game.(done)
  5. Create mss repository and start issue parts.(wait)
  6. Reading ‘Being alive is a gift’ 1 paragragh.(wait)
  7. Make sure of differences between tomcat & nginx.(done)

7.12

  1. Finish reading  ‘Being alive is a gift’.(done)
  2. Reading one third of ‘YunJi in history’.(done)

7.13

  1. Learn APS including the essence of APS and how to use this protocal.(done)
  2. Learn kite-line.(wait)
  3. Set kpi guidline.(done)

7.14

  1. Learn about APS.
  2. Learn kite-line.
  3. Finish romar-ng guideline.

7.15

  1. JAVA-APS learning.(done)

7.16

  1. JAVA-APS learning.(done)
  2. git learning.(focus on fork, pull/request)(wait)
  3. To finish development of JAVA-APS for romar-ng.(wait)
  4.  Refactor of touchweb rental parts.(done)
  5. Jog.(miss)
  6. Reading ‘YunJi in history’.(done)

7.17

  1. Git learning.(focus on fork, pull/request)(wait)
  2. To finish development of JAVA-APS for romar-ng.(wait)
  3. Jog.(miss)

Today, i met a difficult point on java-aps development, and now i’ve found the way to solve, folder archeture is the reason of problem generation, maybe do not have delay mentality but make determination to solve, to chanllenge is a way to grow.

7.18

  1. To finish development of JAVA-APS for romar-ng.(The key point is paying close attention to folder archeture)(done)
  2. Give over charge of history module.(done)
  3. Git learning about fork/pull request methods.(wait)
  4. Play a football game.(done)
  5. Reading for a little while.(miss)

7.19

  1. Reading for a little while.(done)
  2. To realise APS for romar datas.(ing)

7.20

  1. To realise APS for romar datas.(ing)

7.21

  1. To realise APS for romar datas.(ing)

7.22

  1. To realise APS for romar datas.(ing)
  2. Jog . (done)

7.23

  1. To realise APS for romar datas.(ing)
  2. Make sure of spring:constructor-arg.(done)

7.24

  1. To realise APS for romar datas.(wait)
  2. Fix touchweb problems.(done)
  3. Job for a while.(miss)

I feel that though i’ve had destinations, when i was a little busy, i totally forgot my list, then my todo-list lost its meaning.

7.25

  1. To solve reading java configure files.
  2. To solve pointing port.
  3. To read for a while.
  4. To have a sports game, football or basket is okay.

7.28

  1. Make up api_regex.(done)
  2. Make sure of tomcat logs.(done)
  3. Research Aps dev and at least understand where the error is.(wait)
  4. 2 hour reading.(done)

After one day study, i am satisfied with my reading time, fast-reading skills need to be developed, especially for magazines or news.

7.29

  1. Aps development.(wait)
  2. Tomcat-log4j notes.(done)
  3. 2 hour reading.(done)
  4. Zeromq learing.(miss)

7.30

  1. Tomcat running based on instance and combined with complete profiles.(done)
  2. Make sure of how to make access logs or what to write down.(miss)
  3. 2 hour reading.(done)

8.1

  1. log4j learning.
  2. Zeromq learning.
  3. 2 hour reading.
  4. 1 movie.

8.5

  1. Make sure about romar-ng tasks(if tomcat- startup engine will be substituted? logger for tomcat or for program itself?)(done, both developing need to be compared)
  2. Java-aps development(done)
  3. Zmq learning.(miss)
  4. Play a football game.(done)

8.6

  1. Java-aps development.(done)
  2. Zmq learning.(done)
  3. Junit demo development.(wait)
  4. Learn about embedded jetty and tomcat container.(wait)

How to deploy log4j for program itself, refer to aps-server-assembly.

How to use kt to watch process, refer to PingRequestHandler.java.

8.7

  1. Java-aps development.(done)
  2. Junit learning.(wait)
  3. learn about embedded jetty and tomcat container.(wait)

8.8

  1. Java-aps development.(done)
  2. Junit learning.(miss)
  3. 2 hours reading.(‘developers best practises’ ‘records of city’)(wait)

8.11

  1. Make sure the questions of Java-aps and try my best to finish the development.(done)
  2. Finish reading ‘developers best practises’.(wait)
  3. 20 pages of zmq guid.(done)
  4. Finish reading ‘records of city’.(done)

I want to say sth to myself : Once you make the to do list, please to perform it strictly. I suggest i’d better execute conscious assessment and do my best, do not too much.

8.12

  1. Java-aps development. Maybe to log the problem is the straight way to.(done)
  2. Finish reading ‘developer’s best practise’.(It is important but with not emergency which is the point i need to focus on)
  3. Choose one book and begin to read for 1 hour.
  4. Jog for an hour.(done)

Today, i have found the key point of aps dev errors, to use log, please remember ! Tomorrow i need to spend time on the kiteline listener.

8.13

  1. Finish development of aps-client and make sure about the redis connection problems.(done)
  2. Read for an hour.(‘A person’s pilgrimage’)(done)
  3. Run for an hour.(done)

8.14

  1. Aps-service combined with kite-line.(done)
  2. Finish reading ‘developer’s best practise’.(wait)
  3. Read for 2 hours.(‘A person’s pilgrimage’).(done)
  4. Jog for an hour.(done)

today, satisfied with my job, i tried my best to join the group and perfect finish the kite-line development, pretty good.

8.15

  1. Merge aps-service to romar-ng, including update redis service and register kiteline.
  2. Finish reading ‘developer’s best practise’.
  3. Read for an hour. (‘A person’s pilgrimage’)
  4. BasketBall for one and half an hour. (done)
  5. learn some elementary knowledge, pull request, embedded container.

8.16

  1. Solve romar-aps problems, including version, kite-line status, embedded start-up.(done)
  2. Read for 5 hours.(‘design patterns’ ‘a person’s pilgrimage’)(done)

8.17

  1. Read for 8 hours.(‘a person’s pilgrimage’ psychology articles) (done)
  2. learn about pull request (done)
  3. think of mss (done)
  4. run for an hour (done)

i think, if i do a little more, i will be a little better.

8.18

  1. To design mss.(wait)
  2. To deploy romar-aps.(done)
  3. Run for an hour. (miss)
  4. Try to get  a feeling of pull-request and embedded container.(done)

At night, there’re sth. to do : (1) clean up pom.xml (2) rewrite startup.sh (3) run for an hour.

Even though you’ve done sth, try to make it better but not satified with what you got.

8.19

  1. Finish embedded aps-server development.(done, have finished most parts)
  2. Make up maven deployment notes. (done)
  3. Make plan of mss.(wait, already started)
  4. Run for an hour. (done)

i am satisfied with my preferences today.

8.20

  1. Initial mss plans.(done)
  2. Rewrite aps.(miss)

8.21

  1. Finish mss plans. (done)

8.22

  1. learn about ‘developers’s best practises’. (done)
  2. Play a basketball game. (done)
  3. Read for an hour.(‘a person’s pilgrimage’) (miss)
  4. Update mss design. (done)

8.23

  1. Initialize mss dataflow design. (done)
  2. Read for 4 hours to finish reading ‘a person’s pilgrimage’ .(done)

8.24

  1. Finish dataflow design. (done)
  2. Finish base coding-design.
  3. Read for 4 hours. (‘The invisible gorilla’)
  4. Jog for an hour.
  5. Have a meaningful movie.

8.25

  1. Build frames of mss and finish storage layer development.
  2. Read for an hour(‘The invisible gorilla’).
  3. Run for an hour.

8.26

  1. Mss development to finish computation layer.
  2. Learn about static constructor.

8.27

  1. Mss development to finish parts of serving layer.
  2. Jog for an hour.
  3. Learn about abstract constructor.

8.28

  1. Mss development to finish serving layer part.
  • load() part
  1. (load()/reload()/postBatch()/chineseEncode).

8.29

  1. Mss development to finish aps module. (extends requesthandler).
  2. Research about the method to start Embedded engine.
  3. When loading, diff databases should be chosen.
  4. Run for an hour.
  5. Relax for a while, maybe movie or books.

8.31

  1. Read for 2 hours (‘Elegant Hedgehog‘)
  2. Embedded tomcat & spring root development.
  3. Sololution to diff child jar versions from diff parent or diff jars.
  4. Jog for an hour.

9.1

  1. Mss development (redis selection, embedded start of aps, embedded start of mss, configure, logger-engine).
  2. Read for 2 hours (‘Elegant Hedgehog’).
  3. Refactor of mss.
  4. Run for an hour.

9.2

  1. Mss deployment.
  2. Mss pros fixed.

9.3

  1. Logger design and development.
  2. Ansible learning.
  3. Make conclusion of HandlerExceptionResolver and RuntimeException usages.

9.4

  1. Aps log ensure.
  2. Config profiles offer.

9.9

  1. log details (done)
  2. ansible deploy (done)
  3. data structure (wait)
  4. function testing (wait)
  5. start.sh/stop.sh of aps (done)
  6. 2 hour reading (‘Elegant Hedgehog‘) (done)

9.10

  1. aps logs details (done)
  2. http startup.sh (done)
  3. aps profiles (done)
  4. http stop.sh (done)
  5. data structure (wait)
  6. two hour reading (‘Elegant Hedgehog‘) (done)
  7. one hour running. (done)

Execelent, once willing giving up, hold on for a while.

9.11

  1. Mss function testing.
  2. Data structure refactor.
  3. Add reload module.
  4. To move house.

9.13

  1. 6 hours reading.(‘Hacker and Painter’)
  2. To move house.

9.14

  1. Mss.pid to each folder.
  2. Ansible refactor.
  3. Mss profiles refactor.
  4. Timing service.
  5. Fix mss.pid logic.

9.15

1 java coding to clone data. (done)

2 Deploy online. (tomorrow)

3 Rewrite jdk restart scripts (tomorrow )
(1) focus on redundancy
(2) dispatch memory to start service

4 rewrite document (the day after tomorrow)
(1) coding design
(2) User guide

5 log details (tomorrow)

6 java refactor (today)

7 when to reload without download (tomorrow)

8 awk notes (tomorrow)

banwords : pool 1

access log 5++ & 4++ using global exception catch

when first download dictionary to redis, use reload method.

error :

DEBUG 2014-09-15 20:53:06,280 [http-nio-8686-exec-2] cache – Could not find template in cache, creating new one; id=[“error.ftl”["zh_CN",UTF-8,parsed] ]

9.16,17,18

1 To deploy online . (done)

2 Rewrite jdk start shell scripts.
(1) focus on redundancy
(2) dispatch memory to start service

3 update log details (done)

4 what’s wrong with exception ? (done)

5 reload without download, think about when.

6 mss match ‘1’, what’s the meaning ? (done)

7 test environment dipatch.

8 aps script rewrite.

9 fix dumplicate return with diff methods. (done)

10 update serving layer of romar.

11 mss/search check if dictionary exists. (do not check in case of wasting running time) suppose pool split reasonable. (done)

12 after operated dict, such as delete, add, reload didn’t generate effects.

13 to deploy offline (done)

14 git tar & jar

apply new server-engine
delete dictionary

http://192.168.191.100:8888/delete/dict/dictionary?dicname=banwords-dict

create dictionary

http://192.168.191.100:8888/create/dict?dicname=banwords-dict

reload dictionary

http://192.168.191.100:8888/reload/dict?dicname=banwords-dict

mss match

http://192.168.191.100:8888/mss/match?text=tajalli&dicname=wenda-prompt-dict

mss search

http://192.168.191.100:8888/mss/search?dicname=wenda-prompt-dict&text=%E5%A4%A9%E6%B0%B4%E6%8A%93%E8%8E%B7%E6%96%B0%E7%96%86%E4%BA%BA%E6%98%AF%E4%B9%88

aps start errors :

1 if start aps first , it can not find mss.properites : /home/mss/apps/conf/properties/banwords/mss.properties
Host superchunk.example.org
ProxyCommand ssh user@bastion.example.org nc %h %p

9.21

  1. apache bench mark (wait)
  2. reload testing (done)
  3. think about how to load the point dict only (wait)
  4. for loop optimize. (wait)
  5. redis service update increasing return resource to pool.
  6. access logs recorded. (done)

9.22

  1. Mss deployment. (done)
  2. Apache benchmark pressure testing. (done with shell scripts, on 23 researching apache)
  3. Access logs location. (wait)
  4. Run for an hour. (done)
  5. Fix aps shutdown scripts (wait)

9.23

  1. Update access logs location. (done)
  2. Fix aps shutdown scripts. (wait)
  3. Apache benchmark testing.(done but use shell scripts)
  4. Learn about design patterns. (miss)
  5. Generate aps_access_logs directory. (done)

9.24

  1. Update aps shutdown scripts. (done)
  2. Reload diff dics testing  when adus. (done)
  3. Deploy pros online and monitor it. (done)
  4. Think about how to load diff dics. (done)
  5. Pressure testing. (done)
  6. Run for an hour. (done)

9.25

  1. Reload diff dics by using diff trees.
  2. Pressure testing by apache benchmark.
  3. Monitor banwords business of  brokers online.
  4. Design patters learning.
  5. Read for an hour. (‘stage of sence’)

9.28

  1. Multiple threads testing. (done)
  2. Find out where the time used in algorithm. (done) (it is used in objectMapper convertion)
  3. Run for an hour.
  4. Read for an hour.(‘look for oneself’)
  5. Discuz build.

9.29

  1. Function testing and monitor the deployment.
  2. Refactor of mss.
  3. Design-pattern learning.

9.30

  1. Split inner memory load. (done) (Because of  a global variable.)
  2. Design-pattern learning. (done)
  3. Jvm learning. (http://javaeesupportpatterns.blogspot.jp/2012/07/5-tips-for-proper-java-heap-size.html)
  4. Run for an hour.
  5. Discuz building.
  6. Router install. (done)

Think about who you are and what you really want ? your values ? your destination?

10.14

  1. Develop high concurrency service.
  2. Make high concurrency testing.
  3. Design pattern learning.
  4. Run for an hour.

I want to say that no matter what happens, remember that life does not only have one angle, you are a person and think out of the box, it doesn’t matter, life should not be disturbbed.

10.18

  1. Summarize mss in document. (mss-gurantee, coding-design, function testing)
  2. Record performance data.
  3. Fix problems of no results unless change dicts.
  4. Run for an hour.
  5. Read for two hours.(‘study abord diary’)

10.19

  1. Summarize mss in document. (user-guide, deployment-manual, development-manaul, performance monitor)
  2. Fix internal memory continuously increasement.
  3. Fix random results missing.
  4. Fix reload function not works( solution: clean dict memory ).

10.20

  1. Finish performance testing docs.
  2. Scottare Green vpn costs.
  3. Subscribe to ‘developer’ and ‘finiancial weekend’ magazine.
  4. Say goodbye to mates.
  5. Run for an hour.
  6. Read for two hours.

10.23

  1. Build env of imdada.
  2. Help automatic data counting, discuss about monitor aims and select tech tools.
  3. Run for an hour.
  4. Read for an hour.

Knowledge tags : nerd_tree :

J : go to the end

K : go to the head

p(P) : go to parent index

10.24

  1. Es & kibana arch building.
  2. Read for an hour.
  3. Jog for an hour.

10.25

  1. Learn about kibana filters and query.
  2. Combine dada business with es.
  3. Read for an hour.
  4. Jog for an hour.

10.26

  1. Gms development. (Build spring & spring-boot arch; Learn about jpa)
  2. Run for  2 hours.
  3. Read for an hour. (Person’s self finding)

10.27

  1. Gms development. (Index page development; Model layer develpment; Learn about kibana timing charts and world map.)
  2. Learn design pattern for an hour.
  3. Learn about .
  4. Deploy gms to dev env.
  5. Read for an hour. (Person’s self seeking.)

10.28

  1. Gms development. (Model layer development) (done)
  2. Learn about web service building. (done)
  3. Record es & kibana development processes. (done)
  4. Learn about big_data trendency.
  5. Read for an hour. (Person’s self seeking)

11.1

  1. Gms dev env building.
  2. Learn about big data trendency.
  3. Learn one chapter of  design pattern.
  4. Read for an hour.
  5. Run for an hour.

11.10

  1. Gms andible deployment and test feasibility. (After 7 pm)
  2. Development of shops which get out of line. (From 9 am to 3 pm)
  3. Hadoop arch design. (from 3 pm to 7 pm)
  4. Learn about machine learning.
  5. Read for an hour.

If i want to finish the above tasks especially the last two, i need to go home before 9 pm.

11.14

  1. Jobs of violate_shop_score data migration. (From 10 am to 12 am)
  2. Development about city filters of violate shops. (From 2 pm to 3 pm)
  3. Gms migration. (From 3 pm to 4 pm)
  4. Learn about Hadoop distribution arch. (From 4 pm to 9 pm)
  5. Read for an hour (‘why do chinese people industrious but not wealthy’)
  6. Run for an hour.

11.15

  1. Email development realizing emails to all about order datas.
  2. Hadoop arch design to all.
  3. Read for an hour.

11.16

  1. Email development and deployment.
  2. Gms deployment.
  3. Hadoop-ansible development.
  4. Read for an hour.

11.18

  1. Learn about python and uwsgi.
  2. cdh-ansible development.
  3. Read for an hour.

11.19

  1. Finish shop_violation development.
  2. cdh-ansible development. (Focus on hdfs and hbase modules.)
  3. Run for an hour.
  4. Read for an hour.
  5. Learn about trendency of big_data and uwsgi/python.

11.20

  1. Gateway shell scripts learning.
  2. Deploy CDH on master and nodes.
  3. Prepare profiles of hdfs and mapreduce.
  4. Read for an hour.

11.21

  1. Try to finish the deployment of  hdfs on hmaster/hslave.
  2. Deploy yarn on hmaster/hslave.
  3. Gms deployment on hmaster. (Once  one thing you choose, try your best to get it.)
  4. Read for an hour.
  5. Run for an hour.

Arrange time intelligently.

11.22

  1. Import violation datas online.
  2. MapReduce deployment.
  3. Solve hdfs start problems on slave.
  4. Read for an hour.

11.23

  1. Import violation data online. (done)
  2. Kppie domain name update. (done)
  3. Configure wireless gateway.
  4. Run for an hour.
  5. Read for 5 hours.

11.26

Today, i took a break due to unwell body, reading some articles and sleeping for quite a long time.

11.27

  1. Hive remote metastore deployment .
  2. Practice about mapreduce with hive combination .
  3. Think about the way of log access.
  4. Read for an hour.
  5. Run forn an hour.

11.28

  1. Distributed hdfs with hive.
  2. Import data into file system (By file system or jdbc) and analysis the effects.
  3. Read for an hour.

11.29

  1. Finish hive-client of jdbc way .
  2. Discuss with partners about how to import logs into hdfs .
  3. Fix hive-mapreduce analysis.
  4. Learn about hive web interface.
  5. Read for an hour.
  6. Run for an hour.

12.1

  1. Finish hwi api development.
  2. Filter logs of lb_nginx for hwi api.
  3. Fix gms problems.
  4. Read for 2 hours.(From 8 am to 9 am, 6 pm to 6.30 pm, 11 pm to 11.30 pm)

12.2

  1. Filter logs of lb_nginx for hwi api development.
  2. Make sure of gms datas accurate.
  3. Read for 2 hours.(From 8 am to 9 am, 6 pm to 6.30 pm, 11 pm to 11.30 pm)

12.3

  1. Import accurate data into filter_log system.
  2. Hue development.
  3. Watch gms function.
  4. Read for  1 hour.

12.4

  1. Hive web interface(Hue) development.
  2. Update hdfs r/w authority.
  3. Fix map/reduce deployment problems.
  4. Read for an hour.

12.5

  1. Hive web interface(Hue) development.
  2. Hive/mapreduce development for logs analysis.
  3. Read for 2 hours. (6:00pm to 7:00 pm, 11:00pm to 12:00pm)

12.8

  1. Hive web interface(Hue) configuration.
  2. Log filter deveplopment (hql and mapreduce).
  3. Fix ban_shop errors.
  4. Read for 2 hours. (6:00pm to 7:00 pm, 10:30pm to 11:30pm, “poor economics”)

12.9

  1. Upgrade Hue to 3.0 version.
  2. Combine beewax module with hive.
  3. Read for an hour. (“poor economics”)

12.10

  1. Simulate Hive analysis based on Hue online, especially function testing.
  2. Sort out Hue installation, deployment document.
  3. Think about hive-hbase application.
  4. Read for two hours. (6:00 pm to 7:00 pm and 11:00 pm to 12:00 pm)
  5. Run for an hour. (7:00 am to 8:00 am)

12.11

  1. Fix analysis problems online. (MapReduce overtime; Import data with server errors)
  2. Sort out documents. (Hue related; Logs analysis process)
  3. Read for 2 hours.

12.12

  1. Hbase deployment. (Combine with hive and do some function testing)
  2. HiveServer java-api refactor.
  3. Design pattern learning.
  4. Read for 2 hours.
  5. Run for an hour (If I wanna get it, I need to go home before 8 pm).

12.13

  1. Share hadoop platform building to my partners.
  2. Locate and record mapreduce problems.
  3. Hbase development.
  4. Read for 2 hours.

12.15

  1. Share hadoop platform building process to partners.
  2. Hbase deployment.
  3. Migrate violation data to data warehouse.
  4. Read for 2 hours. (8:30 am to 9:00 am, 6:30 pm to 7:00 pm, 11:00 pm to 12:00 pm)

12.16

  1. Migrate violation data to data warehouse.
  2. Fix adding violation pros.
  3. Hbase deployment on pseudo-distributed env.
  4. Read for 2 hours.

12.17

  1. Hbase deployment on destributed env.
  2. Migrate violation date to dw and do tight testing.
  3. Read for 2 hours.
  4. Run for an hour. (7:00 am to 8:00 am)

I think the todo list should be more rational and farsight which could make my follow sensible.

12.18

  1. Hbase client development and import data into hdfs.
  2. Fix violation add problems (shop_name with num can not be added into system).
  3. Read for 2 hours. (‘The motley crew’)

12.19

  1. Hbase client development.
  2. Realize interaction between hive and hbase.
  3. Read for 2 hours.
  4. Run for an hour. (Back home before 9:00 pm).

12.21

  1. Read for 6 hours. (finish reading LiuTong’s new book: ‘be proud of your lonely, though you may lose’)
  2. Run for an hour.

12.22

  1. Monitor online development. (Make sure why can not get sql query; What should result ‘none’ show in trendency table)
  2. App logs analysis development. (Table structure design; Hbase external table building; Read logs development of queue on logic and api layer.)
  3. Read for an hour.
  4. Play one basketball game. (Meet some colleagues, with different feelings and during walked home, also thought a lot.)

12.23

  1. Api logs analysis development. (Reading logs from redis and write to hardware.)
  2. Read for an hour.

12.24

  1. Api logs analysis development. (Write logs to hardware and import to hdfs)
  2. Read for an hour.

12.29

  1. Finish personal center program devlopment. ( From 26 to 29, I concentrated my attention on this program including Model, View and Controller modules. During this process, learned about how to use flask to build the based arch, html 5 tech to build static pages, uwsgi deployment with nginx. No doubt, it was filled with happiness and I learnt a lot, though alone and rough. Maybe it validated that if you want to get sth, correspondly you should undertake the same level. )

12.30

  1. Fix hive server rejection pros.
  2. Import data into hdfs. (simulate import with diff concurrency quantity)
  3. Run for an hour.
  4. Read for an hour.

12.31

  1. Redis input/output client development . (I met the bottleneck of java i/o, I’ll choose the solution with multiple threads or nio)
  2. Combine the html5 pages with android platform. (It is really fresh for me, feel good)
  3. Read for 2 hours and conclude the whole year. (Today is the last day of this year, it is signifficant for everyone, isn’t it ? Think deeply back the last year. )

1.5

  1. Violation list development to open Beijing business area. (Update myisam to innodb and use utf8 instead of latin)
  2. Approve logs import development . ((1)compress strategies
    (2)fix problem ‘Unexpected character (‘u’ (code 117)): was expecting double-quote to start field name’
    (3)logs backup
    (4)speed up the import rate)
  3. git submodule learning.
  4. Think about lb combined with uwsgi and nginx.

1.8

  1. Solve the bottleneck of data import which limited under 200 items/s. (The solution is to add threads in order to deal with data meanwhile and decrease i/o times. The achievement is about 1000 items/s.)

sth. to say: these days I have a little deep thought of the logs process, include reading logs from remote servers (such as the access logs operation on lb), reading logs from redis (it means that to regard redis as a middle layer, all app logs sent to it and the hpc service pulls it to complete writing hdfs_ori logs and backup logs.). Also I learnt about logs package (At the primary, I wrote logs package jobs combined with cron jobs, today I leant there is a tool named log_rotate, wow, isn’t it suprising ?). Through these days learning, I also came to know kafka, chukwa, scribe, flume frames, they all used to deal with logs collection. In the following days, I’ll research the frame(flume-ng+Kafka+Storm+HDFS), so cool!

1.9

  1. Git submodule learning.
  2. Recover access logs alalysis and write down something.
  3. Ajax tech usage in person center.
  4. Read for two hours. (‘Poor Economics’)

I think I should know what is the most important for me and also need to ensure my direction as soon as possible .

1.10

  1. Recover access logs analysis system, to use new logs system and import data into hdfs.
  2. Do person center testing and put the codes online.
  3. Run for an hour.
  4. Read for two hours. (“The poor economy”, “Yehuo collection”)

1.12

  1. Update freeze cash in person center .
  2. Import access logs into new hadoop platform client.
  3. Recover hdfs calculation about access_logs.
  4. Read for an hour (‘Anne’s diary’)

1.13

  1. Design api and access tables arch.
  2. Import api, access logs into hdfs.
  3. Ensure binary files convert strategies.
  4. Read for an hour to finish the book ‘Anne’s diary’.
  5. Run for an hour.

1.15

  1. Import logs to hdfs in new format using new hpc.
  2. Think about how to relate hdfs to hbase.
  3. Run for an hour. (I should be home before 9 pm)
  4. Read for an hour.

1.17

  1. Hbase client development. (Focus on developing hive-hbase integration)

It took me almost one day to solve the mapreduce null exception if I store date in partition way and till now i have no idea about it .

1.19

  1. Update user informs of person center and put it online.
  2. Update monitor clearing dumplicate data.
  3. Create new instance on hslave to filter access logs sharing hmaster’s pressures.
  4. Fix hpc socket exception and mapreduce null exception when in partition way.

Today I faced one problem which refused connection via ssh, first I supposed it was caused by too much ssh requests, however, it came out that I killed sshd! What a funny thing.

1.20

  1. Fix import data into hbase from partition format hdfs with mapreduce null error . (Confused me on 1.17)
  2. Complete hive-hbase integration .

1.21

  1. Import api and access logs into hbase using hive client.
  2. Design accountment of dada and shops with partners.
  3. Run for an hour.
  4. Read for an hour. (Back home before 9:00 pm, I think besides thoughts freedom, time freedom is also important for me, to enjoy the life, to share others’ better ideas. )

1.22

  1. Finish data movement from hdfs to hbase.
  2. Compare the search performance via hdfs and via hbase.
  3. Fix hive server exception of overload.
  4. Read for an hour.

1.23

  1. Learn about how to build storm arch.
  2. Focus on service overload of hive server.

To search via hive above hbase does not show better performance compared to hdfs. So it is necessary to learn about how the hbase works.

1.24

  1. Finish hue configuration combined with hive.
  2. Run for an hour.

1.26

  1. Learn about how hbase works efficient.
  2. To import data into hbase via bulk load.

1.27

  1. Development of weijin account implanation. (It took me almost the whole day, I think if i am one employee of the job, I should do my best to it, it’s my responsibility and work ethic.)
  2. Think about how to use pig to import data into hbase and do some practise. (It’s my key point, not emergency but really important!)

Today, I coundn’t keep my attention concentrated due to my doubt of future, what do I really need? Sometimes I need others’ definites, almost lost myself. If I ensure the choice and I need to follow it, focus my attention on my mission and do more great effort, however, do not lose hope of future and absolutely not allow give up anytime.

1.28

  1. Complete one pig job to import access_logs into hbase.
  2. Finish api development of diff scenes.
  3. Read for an hour (‘The nature of poverty’, ‘wird fire’)
  4. Run for an hour.

1.29

  1. Import weijin api development and make sure of the diff scenes logic.
  2. Pig job to import api_logs into hbase and watch the performance.
  3. Read for an hour.

2.2

  1. Make up the business of weijin .
  2. Finish the development of api .
  3. Update the location of hpc logs .
  4. Design the table of orders and transaction .
  5. Clean up the data under dir ‘/’ .

2.3

  1. Weijin business development, mainly about relations between orders and transaction.
  2. Recover the collection of logs.
  3. Learn about hadoop basic knowledge and think about flume and storm.
  4. Run for an hour. (need to back home before 9 pm)

2.4

  1. Transaction of orders development and to use real data with api. (done)
  2. Redis monitor development. (done)
  3. Run for an hour. (yesterday i did not get the goal, i think sometimes we need to push ourselves)
  4. Read for an hour. (‘hadoop authority’ and ‘learn about literature revolution’)

2.5

  1. Conferences with winjin partners.
  2. Fix problems on person center module which generates null object.

In my opinion, we should pay more attention to our careers, either you or me, if not, we lose our time, even life and the society development will be at a standstill, it’s unfortunate.

2.6

  1. To finish order transaction development. (It’s the key point of the day)
  2. Run for an hour.
  3. Read for an hour.

2.7&2.10

  1. Weijin api instance realization .[dada register, supplier register, dada arrival, unfreeze funds, allowance] (It took me much time :-))
  2. Person center access rules development.

2.11

  1. Weijin api instance realization [order cancel, add order] . (done)
  2. Red packet development of weijin . (done)

In these days, I think to focus on the weijin program maybe the better choice, do one thing at one time is much easier to get it, you know.

2.12

  1. Weijin development. ( (1) complete red packet logic in business part which I responsible for ; (2) develop api instance of orders add/receive )
  2. Update dumplicate data in monitor.
  3. Real-time recommendation learning.
  4. Read for an hour. (Once again, it is not emergency but important for me.)

2.13

  1. weijin account development. (complete red packet, orders add and provide ‘trade_type’ param in all request generation)

Sth. to say : till now, I’ve not got the good practise of learning techknowledge, I need to make some plans and focus my attention on it which means one tech always needs a period of time learning and thinking.

2.15

  1. Weijin account development. (Finish all business modules and do unit testing of dada register.)
  2. Design real time logs analysis.
  3. Read for an hour. (‘devil economics’)

My feelings about the book ‘devil economics’, the author discovered our daily lives, such as credit card amortization traps,  credit card scores with temptation , judgement of  estate transaction and why people wanna to be one participant in bo’ao conference and so on. It is really attractive, strongly recommend it.

2.16

  1. Weijin account development including unit testing of supplier register and part of adding orders.
  2. Design real time logs analysis. (storm + kafka)
  3. Run for an hour.
  4. Read for an hour.

3.5

Till now, I am doing weijing development all the time, what is weijin program ? It is a inner account which builded beyond our system to make balance transfer easy, so we can make trade with different banks, payment system, of course, through it comes to a closed loop which means we can see real money stream in our system ! So to make it possible and to change more people’s life.
In addition, I am in a tough journey now, bearing quite a lot pressure, but I can not lose my determination doing things better, and I am glad to welcome the wonderful life with challenges enough, enjoy it.

  1. Weijing development, I need to try my best to create something. (order finish / account unfreeze logic)
  2. Run for an hour.
  3. Read for an hour. (‘ni cai , at the turn of the century’)

3.6

  1. Weijin development. (Free funds part.)
  2. Monitor system update. (To hide the dumplicate lines.)
  3. Read for an hour. (‘ni cai , at the turn of the century’)

 

3.7

  1. Weijin development. (Finish funds free module.)
  2. Storm learning.
  3. Refactor of weijing.
  4. Read for an hour. (‘ni cai , at the turn of the century’)

3.9

  1. Weijin development. ((1) fix shop_id none problem.
    (2) red_packet of supplier init jobs.
    (3) auto testing jobs for the whole process.)
  2. Learn about strom.
  3. Learn about refactor.
  4. Run for an hour.
  5. Read for an hour. (‘ni cai : at the turn of the century’)

3.16

  1. Weijin development. ((1) concurrency testing.
    (2) online todo list and do some preparation work.
    (3) Put program online and monitor it.)
  2. Uwsgi learning.
  3. Design pattern learning.
  4. Read for an hour. (‘nicai : at the turn of the century’)

3.17

In the morning, we completed the payment system in the quiet atmosphere, everybody tried his best, we give courage and confidence to each other. Mz, Cheng, Alan, Chao, we experienced one meaningful period and I’ll never forget it, wish everyone better!

However, once we arrived one position, please remember to be with mentality turning to zero, let’s go on another journey.

  1. Payment system monitor.
  2. Design pattern learning.
  3. Redesign distribution system.
  4. Read for an hour (‘nicai: at the turn of the century’)
  5. Have a good rest! (^_^)

3.18

  1. Git submodule research. (It is really not a good feeling that having not enough knowledge in one field, especially discuss with others.)
  2. Nginx upstream research.
  3. Iptables research and do a note.
  4. Monitor the payment system.
  5. Run for an hour.
  6. Read for an hour. (Finish the book ‘nicai: at the turn of the century’)

3.19-3.20

  1. Create_settle account details in wallet.
  2. Finish and think of the booke ‘nicai: at the turn of the century.’

3.21

  1. Monitor VFINANCE_ERROR details.
  2. Look for the reason of withdraws error.
  3. Make newer version of create_settle online.
  4. Read for an hour. (CBNweekly)

3.22

  1. Run for an hour.
  2. Read for 2 hours . (‘Readme from HuShi’, ‘Lizehou dialogue set’)
  3. Visiting the botanical garden with one new friend.

3.23

  1. Git submodule research.
  2. Ensure the withdraw problem.
  3. Ensure the member informs update informs methods and finish the development.
  4. Do experiment of red_packet_init and design multiple threads solutions.
  5. Read for an hour. (CBNweekly , ‘Readme from HuShi’)

3.24

  1. Do some development of deal details of wallet.
  2. Track ensure_trade request exception problems.
  3. Run for an hour.
  4. Think of my current status. (What is the most important for me and what should I pay more attention!)

3.25

  1. Finish the development of deal details of wallet.
  2. Fix balance exception which caused by ensure_trade.
  3. Record weijin caller errors into mongo db.
  4. Design hadoop clusters to carry api logs generation.
  5. If possible, read books for a while.

—2015—

7.23

  1. Learning one paragraph of “collective intelligence”, making recommendations.
  2. Learn about design pattern focus on composite pattern and sharing pattern.
  3. learn basic knowledge of hadoop.
  4. Read for 4 hours ‘peakedness of tide’.
  5. Run for an hour.

9.6

  1. Finish Integration test of Listhubdata Service. done
  2. Finish object attribution not null development. miss
  3. Think about hadoop/docker builder. wait
  4. Finish HomeService controller and health check for api service. done
  5. Read for an hour. (‘Status anxiety’) done
  6. Run for an hour. miss

9.7

  1. Realize properties  can not be none in object.
  2. Statsd integration test for monitor performance.
  3. Discuss auto completion in background.
  4. Think about hadoop/docker builder.
  5. Run for an hour.
  6. Read for an hour. (‘Werid psychology’)

9.8

  1. Write one spring aop demo and use it to record metrics. (To learn about @Aspect, @Around)
  2. Read for an hour. (“Werid pcychology”)
  3. Run for an hour.

From aop exercise, I have one deep comprehension of aspect, I learned these annotation : @Aspect, @Around, @Target, @Retention, @Documented. Thanks for my team giving this opportunity to me.

Today, I met one funny thing that two of parterners never ate figs, they cried ‘Why is it so bit ?’. However, I felt that although the figs were not sweet enough, not bit at all. As you know, they ate the skin ! haha…Now I am thinking that they had lived abroad for a real long time.

9.9

  1. Check statsd metrics structure and ensure its functions.
  2. Combine controller with biz service.
  3. Monitor annotation exception. [1> Ensure if timed annotation slows down common service. it will 2> Ensure if throw exception influences common service.]
  4. Read for an hour. (‘Werid psychology’)
  5. Exact the mapping relations between service in xml.
  6. Use multiple threads to deal with metrics process in isolation.

9.10

  1. Encapsulate datas of search result.
  2. Catch the pointed exceptions and record it on stated client.
  3. Use property to assign service name.
  4. Read for an hour. (‘Werid psychology’)

9.11

  1. Review ‘How to build annotation via aspect-oriented’. (metricsT.java, AnnotataionTimedImpl.java, pom.xml, applicationContext.xml)
  2. Development of property can not be null, to use the frame built by Arron.
  3. Read for an hour. (Weird psychology)
  4. Think about docker/hadoop building.
  5. Read for an hour. (Weird psychology)
  6. Watch a movie. (‘pride and prejudice’)

Today is Friday, it meas the weekend is coming, I give me one present watching a movie at night, now I assume it ‘pride and prejudice’ and have a date with my girlfriend ^_^.

9.12

  1. Read for 6 hours. (“last 20 years of Chenyinke”, “history of chinese philosophy”)
  2. Run for an hour.
  3. Review the past half year with Guo.
  4. Watch ‘where fathers to go’ for nearly 2 hours.

9.13

  1. Integration test and unit test for data service.
  2. Run for an hour.
  3. Visit Old streets in Shanghai, Fuxing middle road, Huaihai middle road, Yuyuan.

9.14

  1. Finish testng which can run in order.
  2. Agent service controller development.
  3. Document of Home Service.
  4. Run for an hour.
  5. Read for an hour. (‘Weird psychology’)

9.15

  1. Deploy home service on alpha server.
  2. Refactor home service focus on dependencies.
  3. Finish Agent Service controllers and biz modules development.
  4. Think about hadoop deployment on cluster.
  5. Read for an hour. (‘weird psychology’)

9.16

  1. Refactor home service focus on mongodb connection building.
  2. Combine agent controller with biz.
  3. Think about service arch with high performance.
  4. Review 23 design patterns. (Factory, Abstract-Factory, Beauty-Factory, Builder, Singleton)
  5. Concurrency testing of api, meeting problems about memory leak and duplicate connectors.
  6. Deployment scripts for home service.
  7. Read for an hour. (‘weird psychology’)
  8. Run for an hour.

9.17

  1. Think about multiple threads for statsd client. (done, one open source tool named NoneBlockingStatsdClient.)
  2. Learn about 23 design patterns. (Adapter)
  3. Init school service arch and develop controllers and biz interface.
  4. Think about spring boot with embedded logs.
  5. Run for an hour.
  6. Read for an hour. (‘weird psychology’)

9.18

  1. Refactor mongodb caller from agent service.
  2. Make java -jar effect and import multiple xml s under spring-boot frame for all services.
  3. Read for an hour. (‘Weird psychology’)
  4. Learn about 23 design patterns.(decorator, proxy)

9.19

  1. Read for 6 hours. (‘Peak of wave’)

With today’s reading, I leant a lot of financial knowledge, such as risk investment, operation of investment banks, how the company comes to finance, iop. I have one deeper understanding of equity’s distribution. Most of all, I feel sorry for the fall of giant financial institutions, such as Lehman brothers, Merril Lynch. About finance, is also one profound knowledge, neither too much not too little… In conclusion, If you want to be one better person with broad perspective, you should keep curiosity, desire to acquire knowledge.

9.20

  1. Solve problems of statsd client with multiple threads .
  2. Finish basic scripts including shutdown/startup/corrency_test/kill_all.
  3. Read for an hour. (‘Last 20 years of Chenyinke’)
  4. Learn about 23 design patterns. (Bridge, Facade)

9.21

  1. Learn about 23 design patterns. (Composite, Stragegy)
  2. Finish development of embedded tomcat access logs builder. (-_-)
  3. Run for an hour.
  4. Read for an hour. (‘Weird psychology’ and ‘last 20 years of Chenyinke’)

Today is about to the end, to make a brief review, embedded logs building took me almost the whole day, similar developments was made before, therefore, It’s necessary to think about why can’t control it well, 2 points I’ve found : I did’t conclude the key points in time and did not think deeper of the principle, so I hope it won’t happen again, sorry to myself.

9.22

  1. Simplify application startup steps, put them in order with configures.
  2. Record how embedded log4j works.
  3. Think about deploy home service on docker or via ansible, first install it on max OS X.
  4. Learn about 23 design patterns. (TemplateMethod, Observer)
  5. Refactor common beans adding count property.
  6. Init waijule ansible arch.

9.23

  1. Init wijule deployment tools including ansible and deploy scripts.
  2. Develop account apis.
  3. Think about index page UI and give some constructive suggestions.
  4. Run for an hour.
  5. Read for an hour. (‘Weird psychology’)

9.24

  1. Finish development of account api/biz layer.
  2. Improve ansible scripts for jdk env building.
  3. Read for an hour. (‘Weird psychology’)

9.25

  1. Think about how to deploy jar package in convenient way via ansible.
  2. Learn about 23 design patterns. (ChainOfResponsibility)
  3. Finish bin/logs/conf deployment of ansible and redirect logs output.
  4. Init integration of gerrit with gitweb.
  5. Read for an hour. (‘Weird psychology’)

9.26

  1. Read for 6 hours. (Peak of waves)
  2. Finish development of the integration about gitweb and gerrit.
  3. Run for an hour.

From gitweb/gerrit integration I leant quite a lot, such as nginx related, deeper principles of git and the strange knowledge of fcgiwrap, so I should record something I again, en, ^_^

9.27

Today is middler-autumn festival and I have one unforgettable time thinking a lot.

9.28

  1. Record how to integrate gitweb with gerrit .
  2. Development of account service focus on controller/biz modules .
  3. Improve gitweb with function combined with waijuleweb.git .
  4. Improve tech guide adding gitweb module.

9.29

  1. Development of Email sender using sendGrid.
  2. Change table name from account/Account to account/contact.
  3. Finish development of PwdUpdate development.
  4. Think about online deployment such as server configurations and init scripts.
  5. Read for an hour. (‘Weird psychology’)
  6. Run for an hour.

9.30

  1. Learn about 23 design patterns. (State)
  2. Deploy basic arch on cn-beta/jump-deployment.
  3. Account service development.
  4. Read for an hour.

From 10.1 to 10.7 is Chinese national day, I spent most of time with my family, in my persional position, family if one of the most import thing for me, we talked a lot, at least for me. However, I went to company 2 days in advance on 10.5, there were quite a few tasks to be done.

10.8

  1. Think about gitweb principles and to get rational operation method.
  2. Record how to use jekyll to build blogs.
  3. Account service development, focus on how to build Dao layer efficient and with high availabilities.

10.9

  1. Development of account service. (Till now, most of developments has been done, I should ensure business logic works well in the next period.)
  2. Read for an hour. (“Sophie’s world”)

10.10

  1. Finish account service development.
  2. Learn about 23 design patterns. (Visitor)
  3. Learn about how to change jekyll themes. (I chose Jekyll-bootstrap)
  4. Read for an hour. (Sophie’s world)

10.11

  1. Read for 5 hours. (Sophie’s world)
  2. Run for 30 minutes.
  3. Watch show ‘where is dad going to’
  4. Spend time with Guo and talk about what we have thought recently. Really thanks her for staying with me and doing a lot.

10.12

  1.  Finish development of school service (Detail & List)
  2. Fix remained problems of home/school services.
  3. Refactor agent service, especially dao layer.
  4. Read for an hour. (Peak of waves & Sophie’s world)

10.13

  1. Finish agent service and fix remained errors.
  2. Update ansible scripts using rsync instead of scp and compare these two tools.
  3. Initialize data servers.

10.14

  1. Improve and complete basic services.
  2. Think about the higher performance of ranking.
  3. Improve ansible scripts, mainly following closely dev_tools dependencies.

10.15

  1. Update school ranking method to use stateRanking.
  2. Update agent service to use AgentFilter as unit response for convenient usage.
  3. Update account service (unit common response; refactor request params; verify token usages; redefine business logic)

The most recent, I’ve done quite a few and the trival things occupeid much of my time,  which made me  lost necessary thoughts meanwhile, so I need to pay attention to the weakness.

From 10.16 to 10.17, the chief task was finish all service development and check deployment performance, also one important and significant thing happened.

10.18

  1. Refactor AgentService and AccountService, mainly modified the response constructor and redefine the object properties.
  2. Simulated as spider to fetch data.

 

11.2

  1. Fix pid recorder via supervisord startup.
  2. Agent service development of legacy functions.
  3. Read for an hour. (’Sophie’s world’, ‘Like I’m so clumsy’)
  4. Run for an hour.
  1. Today is my birthday, now I am 24. I think It is the moment to take more responsibilities, take care of my family, work harder. Now, I am no longer the individual , I need to bring hopes and supports to the people who love me.

11.10

  1. Discuss with partners what need to do next.
  2. Logrotate of all services.
  3. Learn more about deployment scripts.
  4. Think about how to monitor the services better and with higher performance.
  5. Read for an hour. (‘gladness’)

11.17

  1. Finish developement of ScheduleWechatTicketUpdate. (I learnt from it : how to keep codes clean; how to build get/post request in java; how to set timeout/retry times; how scheduled tasks work)
  2. Learn about design patterns. (Mediator design pattern)
  3. Learn about big data related informs.
  4. Arrange knowledges touched recently. (collectd/supervisord; ScheduledTasks; Build get/post request in java and set timeout, retry times)
  5. Read for an hour. (Fearless)
  6. Run for an hour.

11.18

  1. Review 23 design patterns.
  2. Fix online pros for widely expand.
  3. Research high performance arch.
  4. Proceed development of business module, mainly focus on 400 page handler and wechat signature generation.
  5. Read for an hour (‘Fearless’)

11.19

  1. Upload agent image named ‘Jennifer strohfus’
  2. Record development steps.
  3. Update generateWechatSignature data structure.
  4. Refactor custom bad request exception handlers.
  5. Read for an hour. (‘Fearless’)

11.20

  1. Review 23 design patterns. (Proxy & Factory)
  2. Learn about frontier dev ops tech.
  3. Finish development of request exception handlers of each service.
  4. Part of unit tests for account service.
  5. Read for an hour. (‘Fearless’)

11.21-11.22

On the weekend, I read Sophie’s world and almost finished it, learning about the history of Western Philosophy, one of significant influnces on me is that few of people are diligent and  could arrive the period immersing the work, after this period, some of them touched another aspect of life, it called the beauty of of life which they could not reject, so they lost themselves and the others could manage themselves well and apart from ruined they will go to the philosophy world which is full of exploration of the world and anatomy of themselves, the latter will finally get the meaning of life, the former is real unfortunate, however, you have to go through this kind of temptation which called beauty of life then you’ll know whether you’re a gentleman.

11.23

  1. Add preference property and search filter to agent/account service.
  2. Unit test of Account Service.
  3. Learn about high performance arch.
  4. Read for an hour. (‘Fearless’)

11.24

  1. Learn about lambda arch and combine it to kafka, samza.
  2. Refactor exception handlers of custom springboot framework.
  3. Unit tests for account service.
  4. Read for an hour. (‘Fearless’)

11.25

  1. Unit tests of AccountService.
  2. Deploy SchoolService/AgentService fixed Object conversion pros in controllers.
  3. Development of mongodb aggregate projection for large data process.
  4. Read for an hour. (‘Fearless’)

11.26

  1. Analysis of bad crawlers. (In this part, I found out where the bad crawler comes from, such as client ip and user agent, what we can do more for it ? to prevent the event in advance? or if there is one open source for the scene?)
  2. Development of unit test for account service. [LoginBiz, getAccountByTokenBiz]
  3. Update index page recommend homes.
  4. Development of springboot exception handlers metrics and test is on cn-beta.
  5. Read for half an hour. (‘Fearless’)

11.27

  1. Learn about frontier science.(openstack, docker/spark, realtime-calculate)
  2. Development of AccountService MockTests and remained problems of Mortgage Service.
  3. Read for an hour and finish reading ‘Fearless’.

11.28-29

These two days, mainly reading and talking with Guo, reviewed and gave imagination free rain about futrue. My reading task is about the biography of Sushi, he is one honest and upright person who I learnt a lot from.

11.30

  1. Unit test of getAccountInformsByToken.
  2. Learn about frontier technologies, focus on arch and cdh.
  3. Run for an hour.
  4. Deploy mortgage service online.

12.1

  1. Development of AccountService unit tests.
  2. Read 2 frontier technologies articles, focus on arch and cdh.
  3. Run for an hour.
  4. Read for an hour. (“You’re so beautiful today”, this book is really interesting and pleasant, talking about the details of life which centres on some lovely animals, such as bear, rabbit, dinosaur, pig… made me understanding smile multiple times, recommend it.)

12.2

  1. Deploy homeservice for [mapsearch, home detail not found response, spring frame exceptions]
  2. Unit tests of Account Service.
  3. Development of index page recommend.
  4. Learn about the frontier tech.

12.3

  1. Read some interesting articles about life or frontier tech.
  2. Development of AccountService unit tests.
  3. Help my new parterner to configure environment.
  4. Read for an hour. (‘Freedom is on the sky’)
  5. Run for an hour.

Today, I knowed about that the nba team ‘warrior’ won their the 20th match,  Stephen·Curry scored 40+ points during 3 periods again, it’s wonderful ! So I think the time of Curry is coming.

12.4

  1. Learn about docker and think about how to think and design different.
  2. Account service unit tests development.
  3. Read for an hour. (‘Freedom is on the sky’)

12.7

  1. Account service unit tests development.
  2. Refactor redis client and deep develop service view count.
  3. Review redis installation and redis common operation.
  4. Read for an hour. (‘Freedom is on the sky’)
  5. Run for an hour.

12.8

  1. Learn about frontier tech.
  2. Deep research docker/openresty.
  3. Development of Account Service unit tests.
  4. Read for an hour. (‘Freedom is on the sky.’)

12.9

  1. Finish account service unit test development. [In this part, how to refactor codes well and readable, easy to keep high degree of stability and continuity are the key points. ]
  2. Initialize post service architecture.
  3. Deep research docker tech.
  4. Read for an hour. (“Freedom is on the sky”)

12.10

  1. Development of post service and refactor great school modules.
  2. Deep research of docker tech.
  3. Read for an hour. (“Freedom is on the sky”)

12.11

  1. Deep research about docker tech.
  2. Development of post service.
  3. Learn about frontier tech.
  4. Read for an hour. (“Freedom is on the sky”)

12.12 – 12.13

This weekend, I’ve read the book ‘biographies of  Sushi’, learning about the life he live and the thoughts he owned, principles he hold on, some view points left me deep impression and I will exact them few days later, more about this book, it is written by Lin Yutang who is a great Chinese cultural researcher. Besides reading, I played one basketball game with Chengsheng and talked closely with Guo which gave me plenty of  happiness.

12.14

  1. Discuss post service arch.
  2. Development of post service base framework.

 

12.15

  1. Refactor log modules.
  2. Development of post service, focus on building service architecture and combine biz with state machine well.
  3. Walk for an hour.
  4. Read for half an hour. (These days I am a little tired, think deeply of my career life and daily life, how to think out of the box and think with one higher perspective.)

12.16

  1. Development of post service, better finish import agent review modules.
  2. To exact error logs from application logs.
  3. Think about arch with high performance and research docker principles.
  4. Read for an hour. (‘Freedom is on the sky.’ & ‘Biographies of Sushi’)

12.17

  1. Development of post service, deep learning state machine and rule engine.
  2. Record try-catch notes and exact error logs notes.
  3. Read for an hour.
  4. Think about arch with high performance and research docker principles.

12.18

  1. Development of post service, finish avg action and refactor dao layer.
  2. Find out  seo launching problems and analyze the reasons.
  3. Read for an hour.

This weekend, most of the time I used to read (Finish reading ‘Biographies of SuShi’, and I began to read some philosophy books, I learned about Shu Benhua, most of his thoughts gave me a lot of inspiration.) and work, much less time to accompany Guo to go somewhere, I believe that everyone is one independent individual, we need to learn about how to live the life ourselves, with strong-willed, more independent and fearless. Also these two days, I spent one hour each day to run and think deeply, It was really one relax period for me, sure, new weekdays are coming, let’s make more possibilities.

12.21

  1. Development of post service, focus on agent review part and finish import module mock tests.
  2. Read for an hour. (‘A Brief History of Humankind’, it’s very interesting, recommend it.)
  3. Run for an hour.

12.22

  1. Development of post service, including agent review modules and mock tests of them. (I think the development is also very helpful to me to master java better.)
  2. Read some frontier view points including technology, economy, life to learn the world better.
  3. Read for an hour. (‘A Brief History of Humankind’)
  4. Run for an hour.

12.23

  1. Development of post service, machine state and action modules.
  2. Read some frontier view points.
  3. Run for an hour.

12.24

  1. Development of post service, finish action modules and refactor average score calculation.
  2. Read for an hour. (‘A Brief History of Humankind.’)

12.25

  1. Finish unit/api test of createImportReviewService/updateImportReviewService/createAgentReviewService/updateAgentReviewService.
  2. Research and choose one api test python frame work. [pyresttest is wonderful, recommend it.]
  3. Run for an hour.
  4. Read for an hour. ['Brief history of humankind']

This weekend I read ‘Brief history of humankind’ for half day, company Guo to health check. The second day I worked all day and talked with Guo for hours, I told her, we should be opsitive and kind-hearted no matter how the world treats us.

12.28

  1. Finish development and unit/api test of searchImportReviewService.
  2. Read for an hour. (Brief history of humankind.)

2016

1.5

  1. Integration tests of post system.
  2. Run for an hour.
  3. Read for an hour. (Brief history of humankind.)

1.6

  1. PyRestTest development of post system. (PyRestTest is one very useful end to end tool, I recommend it.)
  2. Deep research visitor pattern.
  3. Read for an hour. (Brief history of humankind)
  4. Run for an hour.

1.7

  1. Finish PyRestTest development of post system.
  2. Init school post service framework.
  3. Apply visitor pattern and think more about it.
  4. Read for an hour. (Finished reading ‘Brief history of humankind’ and began ‘Man’s search for meaning’)

1.8

  1. Read for an hour. (Man’s search for meaning)
  2. Development of upvote/email sender.
  3. Walk for an hour.
  4. Deep research adapter pattern.

This weekend I spent most of time reading and learning basic computer science, finish reading ‘Brief history of Humankind’, how to realize our ambitions? Work hard and deep concentrate on what we are working on, love somebody with true intention and overcome the difficulties as harder as possible. On the other hand, I played a basketball game and spent one pleasant time with Guo.

1.11

  1. Refactor mortgage service / ansible scripts and add error logs.
  2. Integration test of email templates and deployed it.
  3. Read for an hour. (‘Best tortoise exchanges wines’)

1.12

  1. Development of upvote modules and school review part.
  2. Read for an hour. (‘Best tortoise exchanges wines’)
  3. Run for an hour.
  4. Walk for an hour. (Yesterday I paid much time do exercise and now I am brimming with vigour)

This weekend I worked for hours and played basketball, also stayed with Guo. I spent a lot of time thinking about how to stay with the lover, sometimes the ego comes out and needs attention also excepting encouragements, how to keep balance of job and daily life? How to treat others then could be called responsible? What is the most important to me ? Always I seek perfect so that I can not accept some aspects of myself, if so, how to tolerate others ?

1.18

  1. Development of search school review modules.

1.19

  1.  Development of search school review modules finished, focus on the layer split algorithm.
  2. Learning about design pattern, command-pattern.
  3. Think about pyrest test of search school review. (it needs to rewrite basic class and the grammar is really a challenge for me)
  4.  Read and think for an hour, mission, life, job and so on.

1.20

  1. Read for an hour. (‘Best tortoise exchanges wines’)
  2. Refactor search school post and develop a python script to do complex test. (Pycurl and BytesIO experiments are precious for me, also review how to write beautiful and simple executed scripts.)

1.21

  1. Development of defining mongo db schema key.
  2. Development of python scripts to do data pretreatment.

1.22

  1. Development of refactor mongo db access modules.
  2. Read for an hour. (‘Best tortoise exchanges wines’)

This weekend I got sick with something serious, Guo accompanied me and took care of me. Most of the two days I worked and read something interesting, finished reading ‘Best tortoise exchanges wines’ and began to read ‘Travel of Asia’ which was written by Fuzhen also. So, health decorates the life and hope all of us have a healthy body, best wish to all.

1.25

  1. Development of refactor mongo db access and supply the necessary end to end tests.
  2. Read for an hour.(‘Travel of Asia’ writtern by Fuzhen)

1.26

  1. Refactor mongo db access and supply necessary end to end tests.
  2. Research strategy pattern and record the process.
  3. Review and write down cache practise.

1.27

  1. Refactor db access modules.
  2. Improve end to end tests.
  3. Fix url regex mapping of community details.
  4. Logrotate logs online.

1.28

  1. Refactor db access modules.
  2. Fix duplicate invited account modules.
  3. Read for an hour. (‘Travel of Asia’ writtern by Fuzhen)

1.29

  1. Deploy invited account duplicate errors version.
  2. Development of data access modules.

2.1

  1. Development of mortgage modules refactor.
  2. Async email sender of mortgage modules.

2.2

  1. Finish development of mortgage modules refactor. (Add cityArea & loanAmount fields)
  2. Development of data access modules refactor.
  3. Development of ops scripts for service convenient management.

2.3

  1. Learn about linux basic knowledge.
  2. Refactor data access modules.
  3. Development of agent activity score.

2.4

  1. Learn about linux basic knowledge.
  2. Finish development of agent activity score.

2.22

  1. Development of admin tool.
  2. Development of school reviews.
  3. Improve deploy steps to make process more automatic.
  4. Deep learning python grammar.

Show the best of you to your lover, but not the worst to test how much one loves you.

2.23

  1. Finish development of admin tools.
  2. Update data source of recommend modules.
  3. Read for an hour.
  4. Deep learning python details, especially grammar and oop related.
  5. Recheck service archived, deployment steps.

2.24

  1. Recheck service archive process online.
  2. Ignore deployment tags online.
  3. Refactor data access modules for MortgageService/SunService.
  4. Improve admin tools and record sensitive fields update, record mortgage created/update time, then  deployed.
  5. Clean up and improve deployment steps.
  6. Finish development of agent approve/reject email sender.

2.25

  1. Data access refactor for HomeService.
  2. Deploy the data access refactored services and monitor them. (MortgageService/SunService)
  3. Record python details about oop.

2.26

  1. Development of data access refactor for AgentService.
  2. Development of data access basis.

2.29

  1. Development of data access refactor for AccountService.
  2. Re check deployment and archive scripts functions, performances.
  3. Find out some online pros(act links called so much)
  4. Improve and refactor data access basis.

3.1

  1. Check school post / deployment scripts / archive scripts functions and performance.
  2. Development of filter access logs.
  3. Improve data access basis to support multiple algorithms.
  4. Observe and do operations for db servers.
  5. Do a research of linux memory cache.

3.2

  1. Re check data access basis functions and deploy SunService/AgentService.
  2. Data access refactor for AccountService.
  3. Check school post / deployment scripts / archive scripts functions and performance.
  4. Read for an hour.
  5. Run for an hour.

3.3

  1. Check status about school post / agent active score / development scripts / archive scripts.
  2. Development of health check acc_log filters.
  3. Development of data access refactor for AccountService.
  4. Ensure app/error log format [time] consistency.
  5. Deploy data access refactor for HomeService.
  6. Deep research strategy investment & financial investment.
  7. Add metrics for SMS services.
  8. Run for an hour.

3.4

  1. Check school post / agent score / deployment scripts / archive scripts.
  2. Deployment of health check filter.
  3. Deployment of data access refactor for AccountService.
  4. Development of refactor for  agent post data structure.

This weekend, I went home to see my family, they are all healthy.

3.7

  1. Check school post / agent score / deployment scripts / archive scripts.
  2. Deployment of Account Service data access verification.
  3. Refactor Pyresttest Service, to make the codes clean and simple.

3.8

  1. Refactor pyresttest service to extract all configs.
  2. Research and resolve gerrit memory leak problems.
  3. Deploy Account Service to cn-beta and finish the left verifications.
  4. Check school post / agent score / deployment scripts / archive scripts.
  5.  Improve Waijule Tech Guide.
  6. Check save operations to update…set to avoid time difference.
  7. Fix gerrit commit closed errors. (The last one was abandoned, so needs to reset and commit/push another.)

3.9

  1. Check school post / agent score / deployment scripts / archive scripts.
  2. Development of biz tests for AccountService.
  3. Deep research effective java and take perception notes.
  4. Run for an hour.

3.10

  1. Check school post / agent score / deployment scripts / archive scripts.
  2. Development of biz tests for AccountService.
  3. Deep research effective java and take perception notes.

Today, I think about the relationship with the lover who loves you and the one you deep love. It is really different with the wordly success. This is what I most apprieciate the current environment including the collegues and Guo, they look love, family, emotion as the most important thing of their life which deeply affect me.

3.11

  1. Check school post / agent score / deployment scripts / archive scripts.
  2. Supply biz tests for account service.
  3. Research effective java.
  4. Run for an hour.

3.14

  1. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status.
  2. Improve biz tests for account service and deploy it.

3.15

  1. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status.
  2. Research effective java.
  3. Improve pyrest test service.
  4. Improve email sender as async module.
  5. Run for an hour.

3.16

  1. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status.
  2. Research effective java.
  3. Development of IndexPageRecommendHomes search .
  4. Improve email sender modules, add integration tests and deploy it.
  5. Refactor PostService biz tests.

3.17

  1. Check school post / agent score / deployment scripts / archive scripts / wjl-cb status / wjl-test status.
  2. Research effective java.
  3. Refactor Post Service biz tests.
  4. Run for an hour.

3.18

  1. Check school post / agent score / deployment scripts / archive scripts / wjl-cb status / wjl-test status.
  2. Refactor Post Service biz tests.

3.21

  1. Improve Post Service biz tests.
  2. Build dao constructors so that makes it configurable.
  3. Check school post / agent score / deployment scripts / archive scripts / wjl-cb status / wjl-test status.
  4. Run for an hour.

3.22

  1. Set up supervisord  to manage gerrit/jenkins.
  2. Check school post / agent score / deployment scripts / archive scripts / wjl-cb status / wjl-test status.
  3. Improve post service biz tests.

3.23

  1. Check school post / agent score / deployment scripts / archive scripts / wjl-cb status / wjl-test status.
  2. Improve post service biz tests.(I need to pay more attention to data structure, especially the mockito modules)
  3. Run for an hour.

3.24

  1. Improve post service tests.
  2. Research effective java.
  3. Use supervisord to manage dev tools. [jenkins & gerrit]

3.25

  1. Research effective java.
  2. Development of reduce save entity operation if necessary.
  3. Improve Agent Service tests.
  4. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status.
  5. Development of extract HTTP_MSG_NOT_READABLE from BAD_REQUEST.

3.28

  1. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status / error logs.
  2. Research effective java.
  3. Improve Home Service Biz tests.
  4. Review adapter pattern.
  5. Add memory for dev-tool machine .
  6. Deployment of log modules to unify time zone.

3.29

  1. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status / error logs.
  2. Research effective java.
  3. Improve Home Service Biz tests and ensure the final version.
  4. Refactor mongo client builder, it is not safe or controversial to use singleton pattern, try to writer a report about this on 30.
  5. Run for an hour.

3.30

  1. Make version control for services, deployment version configurable.
  2. Improve School Service biz tests.
  3. Refactor mongo client builder.
  4. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status / error logs.

3.31

  1. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status / error logs.
  2. Improve School / Mortgage Service biz tests.
  3. Development of mongo client builder.
  4. Run for an hour.
  5. Read for an hour.

4.1

  1. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status / error logs.
  2. Improve Mortgage Service biz tests and make parent layer integration tests work.
  3. Design wechat modules.
  4. Development of mongo client builder.

4.4

  1. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status / error logs.
  2. Research effective java.

4.5

  1. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status / error logs.
  2. Research and record effective java notes.
  3. Development of wechat post.
  4. Refactor mongo client builder.
  5. Walk for over an hour.

4.6

  1. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status / mortgage /c contact / error logs.
  2. Development of wechat post.
  3. Walk for over an hour.

4.7

  1. Development of wechat post.
  2. Development of python scripts to monitor key indicators.
  3. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status / mortgage / contact / error logs.
  4.  Walk for over an hour.
  5. Read for an hour.

4.8

  1. Development of wechat post.
  2. Development of python scripts to monitor key indicators. (Keep strict requirements to the quality of codes, even as tools only )
  3. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status / mortgage /c contact / error logs.
  4. Walk for over an hour.
  5. Read for an hour.

4.11

  1. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status / mortgage /c contact / error logs.
  2. Development of wechat post integration tests.
  3. Walk for over an hour.
  4. Analysis of agents contacted.
  5. Run for an hour.

Please not live up to the time.

4.12

  1. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status / mortgage /c contact / error logs.
  2. Development of wechat post integration tests.
  3. Walk for over an hour.
  4. Development of crawler used to grab wechat articles.

4.13

  1. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status / mortgage /c contact / error logs.
  2. Development of crawler used to grab wechat articles.
  3. Research crawler4j client and think deep of spider principles.
  4. Walk for over an hour.

4.14

  1. Finish development of crawler used to grab wechat articles.
  2. Walk for an hour.

These days I paid much attention to design patterns and service structure, deep research crawler principles and did sports as much as possible, I walked to office, walked home, run at night and accompanied with Guo, read books whole day in the Pudong library,  the books we read include technology and life experience which brought us much spirits and expanded our field of vision, thanks for her coming to my life, It’s really exciting life. At last, these days about job is piece, I regard the period as one precious time to precipitate overlooking the life from another angel, wait for a better me.

4.18

  1. Finish development of wechat posts.
  2. Refactor crawler arch.
  3. Walk for an hour.

4.19

  1. Rank hot tags of wechat posts.
  2. Improve community informs about high education and median income.
  3. Walk for an hour.

4.20

  1. Open pull request of crawler4j and provide cookie spec description. (STADARD is the better choice)
  2. Learn about java 8 characteristics.
  3. Finish development of  wechat posts, improve community informs.
  4. Walk for an hour.
  5. Research effective java.

4.21

  1. Ensure nexus configuration.
  2. Finish development of sensitive informs update.
  3. Deploy wechat posts / community informs.
  4. Walk for over an hour.
  5. Run for an hour.
  6. Read for an hour. (‘misses society’)

4.22

  1. Extract and migrate sensitive data.
  2. Walk for over an hour.
  3. Automatically generate account token.
  4.  Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status / mortgage /c contact / error logs / wechat share.
  5. Configure nexus service.

4.25

  1. Research and record effective java notes.
  2. Finish development of home list version change.
  3. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status / mortgage /c contact / error logs / wechat share.
  4. Walk for over an hour.
  5. Run for an hour.

After the labor holiday precipitation, to meet new time.

5.3

  1. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status / mortgage /c contact / error logs / wechat share.
  2. Refactor home list to guarantee version unification.
  3. Development of share update modules.
  4. Walk for over an hour.
  5. Read for an hour.
  6. Run for an hour.

5.4

  1. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status / mortgage /c contact / error logs / wechat share.
  2. Finish development of share update modules.
  3. Deep research observer pattern.
  4. Development of share statistics basis.
  5. Read for an hour.
  6. Walk for over an hour.
  7. Run for an hour.

5.5

  1. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status / mortgage /c contact / error logs / wechat share.
  2. Finish development of share statistics basis.
  3. Refactor pyrest tests to extract common configs.
  4. Read for an hour.
  5. Walk for over an hour.
  6. Run for 40 minutes.

5.6

  1. Finish periodical refactor of pyrest tests.
  2. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status / mortgage /c contact / error logs / wechat share.
  3. Improve share statistics basis and its unit tests.
  4. Refactor data access object client.
  5. Read for an hour.
  6. Walk for over an hour.
  7. Run for an hour.

5.9

  1. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status / mortgage /c contact / error logs / wechat share.
  2. Refactor mortgage mongo client.
  3. Deep research observer pattern.
  4. Refactor mongo data access object base to support inner list update.
  5. Walk for over an hour.
  6. Read for an hour.

5.10

  1. Check school post / agent score / deployment scripts / archive scripts / wjl-cb & wjl-test status / mortgage /c contact / error logs / wechat share.
  2. Refactor sun mongo client.
  3. Development of key points search, such as homeId and mlsNumber(support small applications). Research morphia basis codes and refactor data access object.
  4. Design notification systems.
  5. Run for an hour.
  6. Walk for over an hour.

5.16

  1. Sync wechat articles to all ends.
  2. Do basic data analysis of wechat tags.
  3.  Refactor search modules to improve performance, focus on the result accuracy and more more intelligent about word segmentation.
  4. Walk for over an hour.

5.17

  1. Refactor search engine. (Today I found mongodb full text search is really powerful and with good performance.)
  2. Walk for over an hour.

About the search engine, to improve the search performance and result accuracy, I think there are two main solutions:

One is to use mongo projection keyword and record the access during the search process each time, the other is to use mongo full text search, and the only thing needs to improve is making the regularation work.

5.23

  1. Improve and refactor search engine.
  2. Research CoreOS / Dockerized services / fabric.
  3. Read for an hour.
  4. Walk for over an hour.

Last week, our group went to MoGan Mountain and had a good rest, the only thing after that is to keep our entrepreneurship steps faster and more firm.

Till now, the search engine refactor module has done, not bad, the achievements I got are more familiar with mongo shell scripts and deep learnt about full text search principles, thanks to my persistence.

5.24

  1. Improve search engine, combine regular expression with full text search to enhance user experience.
  2. Research Docker / CoreOS / Fabric.
  3. Import Boston data for new business modules.
  4. Read for an hour.
  5. Run for an hour.
  6. Walk for over an hour.

5.25

  1. Import Boston data.
  2. Refactor data etl scripts.
  3. Read for an hour.
  4. Walk for over an hour.

5.26

  1. Development of admin privileges allocation.
  2. Research swagger-codegen.
  3. Read for an hour.
  4. Walk for over an hour.

5.27

  1. Development of admin privileges allocation.
  2. Read for an hour.
  3. Walk for over an hour.

This weekend I went to friend xcs’s wedding, best wish to him. Besides I helped Han to move house, read some interesting articles about experimental psychology, run as always, and met my family, the most of all, I deep thought about my life, companion, job and the future, really helps me a lot.

5.30

  1. Development of admin privileges allocation.
  2. Clean up sub packages related from nexus and deploy the newest version from local.
  3. Read for an hour.
  4. Walk for over an hour.

5.31

  1. Finish development of admin privileges allocation.
  2. Improve integration tests for admin privileges.
  3. Read for an hour.
  4. Walk for over an hour.

6.1

  1. Import community data of Boston and refactor community data format.
  2. Crawl wechat articles after 5.15.
  3. Read for an hour. (Finish reading ’40 studies changed the psychology’)
  4. Run for an hour.
  5. Walk for over an hour.

6.2

  1. Refactor admin privileges allocation.
  2. Build scala docker container.
  3. Read for an hour.
  4. Walk for over an hour.
  5. Run for an hour.

6.3

  1. Development of subscription system.
  2. Record scala container build process.
  3. Read for an hour.
  4. Walk for over an hour.

6.6

  1. Development of subscription system.
  2. Build and refactor scala env ops from docker.
  3. Read for an hour.
  4. Run for an hour.
  5. Walk for over an hour.

6.7

  1. Finish development of subscription system.
  2. Review aspectj and record development notes.
  3. Research java8 characters focus on flatmap.
  4. Walk for over an hour.

These days we are having Dragon Boat Festival.

6.12

  1.  Refactor subscription system.
  2. Development of changing contact status.
  3. Read for an hour.
  4. Run for an hour.
  5. Walk for over an hour.

6.13

  1. Finish development of changing contact status.
  2. Finish development of changing home subscription status.
  3. Read for an hour. (‘Lost Games’)
  4. Walk for over an hour.
  5. Run for an hour.

6.14

  1. Finish development of updating home subscription status.
  2. Complete integration tests for subscribe service.
  3. Walk for over an hour.

6.15

  1. Finish development of updating home subscription.
  2. Improve integration tests for subscribe service.
  3. Think about extract micro services.
  4. Record observer pattern research.
  5. Walk for over an hour.
  6. Read for an hour. (‘Lost Games’)
  7. Run for 40 minutes.

6.16

  1. Finish development of changing subscription destination status.
  2. Fixed error occurred during password hash coding.
  3. Development of agent app device modules.
  4. Read for an hour. (‘Lost Games’)
  5. Run for an hour.
  6. Walk for over an hour.

6.17

  1. Finish development of agent app device modules.
  2. Check the metrics divided.
  3. Research and record java 8 characters.
  4. Read for an hour.
  5. Run for an hour.
  6. Walk for over an hour.

To be professional.

6.20

  1. Refactor destination data structure of home subscription.
  2. Extract daobase to common package.
  3. Development of article crawler. (We use tika tool)
  4. Read for an hour.(‘Lost Games’)
  5. Run for an hour.
  6. Walk for over an hour.

6.21

  1. Development of article crawler.
  2. Read for an hour. (‘Lost Games’)
  3. Run for an hour.
  4. Walk for over an hour.

6.22

  1. Development of article crawler, mainly finish the api modifications and focus on the grab process, structure.
  2. Read for an hour. (‘Lost Games II’)
  3. Run for an hour.
  4. Walk for over an hour.

6.23-26

  1. Refactor article crawler to grab from docx and xlsx, mainly fix problems and make the codes good smell.
  2. Research design patterns.
  3. Read as always at weekday night, also on the weekend.
  4. Run if possible.

6.27

  1. Finish development of article share.
  2. Refactor article source: expand with date / cityArea.
  3. Run for an hour.
  4. Read for an hour. (‘Chronicles economic’)
  5. Walk for over an hour.

7.6

  1. Development of recording article visited count.
  2. Some preparation work for notification/XGBuyerInfo on-line.
  3. Research python grammar. (List comprehension, Decorator)
  4. Run for an hour.
  5. Walk for over an hour.

7.7

  1. Configure swagger client for notification service and push informs to fe.
  2. Development of contact note modules.
  3. Walk for over an hour.

7.8

  1. Deploy buyerinfo/notification services on-line.
  2. Introduce article visited-count to fe.
  3. Learn about python gramma.(Generator)
  4. Walk for over an hour.

7.11

  1. Finish development of mortgage intention module.
  2. Python grammar learning.(Iterator,  map/reduce)
  3. Backup for notification/buyerinfo services, matual backup.
  4. Import latest articles, 20 from docx(wechat), 6 from xlsx(internet).
  5. Read for an hour.
  6. Run for an hour.
  7. Walk for over an hour.

7.12

  1. Email sender for contact email to know who have mortgage intentions.
  2. Added gender property for buyerinfo module.
  3. Read for an hour.
  4. Run for an hour.
  5. Walk for over an hour.

7.13

  1. Analysis of mixpanel events and aggregate original data.
  2. Refactor contact note module. (Unite the api responses, rename some keywords and sort the notes by modified time)
  3. Finish development of article tag count.
  4. Read for an hour.
  5. Walk for over an hour.

7.18

  1. Development of buyerinfo duplicate check.
  2. Refactor mongo client to support multiple collection building and move singleton to frame layer.
  3. Make notification push scheduled and think about the system design.
  4. Run for an hour.
  5. Walk for over an hour.

7.19

  1. Development of push notification schedule.
  2. Learn about mongodb transaction.
  3. Refactor mongoclient.
  4. Walk for over an hour.
  5. Basketball.
  6. Read for an hour.

7.20

  1. Refactor scheduler structure and add notification archive schedule.
  2. Update data access object, add more common basic methods. (findAndModify, updateFirst, deleteMany, delete)
  3. Import articles.
  4. Read for an hour.
  5. Walk for over an hour. (Basketball on 19th really makes me muscle ache, it’s months since last game.)

7.21

  1. Development of qrCode decoder. (Use zebra crossing)
  2. Import articles. (Think about automatic model)
  3. Read for an hour.
  4. Walk for over an hour.

7.22

  1. Finish development of qrCode decoder. (The rate of recognization approaches 90%, still room here to improve)
  2. Find out article upload exception. (It was caused by an unformat picture, we need to unite the format next.)
  3. Read for an hour.
  4. Walk for over an hour.

At weekend, I spend most of time reading which made me calm down and peace. I talked to Guo, leave some space is quite good.

7.25

  1. Finish development of parse push notifications.
  2. Import articles.
  3. Read for an hour.
  4. Walk for over an hour.
  5. Run for an hour.

7.26

  1. Implement order function in data access object.
  2. Improve zxing decoder, more extract implementations provided.
  3. Import articles.
  4. Read for an hour.
  5. Walk for over an hour.
  6. Run for an hour.

7.27

  1. Test performance of schedule while experiencing heavy currency.
  2. Improve notification arch to notice currency errors. (Record the machine execution process)
  3. Import articles.
  4. Read for an hour.
  5. Walk for over an hour.

8.1

  1. Added new version of extracting xlsx format articles.
  2. Finish development of email schedule archive.
  3. Update swagger client of school service.
  4. Import articles.
  5. Check notifications.
  6. Read for an hour.
  7. Walk for over an hour.

8.2

  1. Sort articles by release time.
  2. Refactor email notification system mainly rename email schedule related modules, try to use notification as mark.
  3. Development of push email notification module.
  4. Development of send message client for BuyerInfo Service.
  5. Import articles.
  6. Check notifications.
  7. Run for an hour.
  8. Read for an hour.
  9. Walk for over an hour.

8.3

  1. Refactor article service, mainly remove useless qrCode.
  2. Import articles.
  3. Development of sendMsg client for BuyerInfo Service.
  4. Check notification and fixed installation miss.
  5. Walk for over an hour.

8.4

  1. Development of push email notifications. Focus on structure adjustment.
  2. Import articles.
  3. Check notifications.
  4. Fixed expired logic of notification archive.
  5. Read for an hour.
  6. Run for over an hour.
  7. Walk for an hour.

8.5

  1. Provide one skeleton class for extract interface.
  2. Import articles.
  3. Check notifications.
  4. Improve notification system, think deep about command pattern and generic type usages.
  5. Walk for over an hour.

On the weekend, I read some books and thought about the recent life which a little hard for me, I believed that whether fortunately or not, I should be justice and not lose dignity to live, live deep, meet the misery.

8.8

  1. Improve article extract process, filter ‘learn more about’ and extract ‘table’ label.
  2. Extract base notification archive service using singleton.
  3. Check notifications.
  4. Deep research command pattern.
  5. Import articles.
  6. Read for an hour.
  7. Walk for over an hour.

8.9

  1. Added monitor of notification service.
  2. Check notifications.
  3. Import articles.
  4. Refactor entity/dao generic type usages for notification service.
  5. Learning effective java and write down something.
  6. Added XGSendMessage client using retrofit2.
  7. Read for an hour.
  8. Run for an hour.
  9. Walk for over an hour.

8.10

  1. Finish development of sendMsg client caller, waiting for configs all added.
  2. Import articles.
  3. Learn about effective java.
  4. Add reports for notification/article services.
  5. Walk for over an hour.

8.11

  1. Automatically upload articles.
  2. Added part of email clients.
  3. Import articles.
  4. Read for an hour.
  5. Walk for over an hour.

8.12

  1. Added push email client.
  2. Automatically upload docx articles.
  3. Import articles.
  4. Integrated tests for notification clients.
  5. Walk for over an hour.
  6. Read for an hour.

8.15

  1. Added push email clients.
  2. Think about command pattern.
  3. Learn about effective java.
  4. Check notifications.
  5. Import articles.
  6. Read for an hour.
  7. Walk for over an hour.

8.16

  1. Refactor basic data access object to return UpdateResults.
  2. Migrate mongo base to common package.
  3. Research command pattern.
  4. Import articles.
  5. Check notifications.
  6. Read for an hour
  7. Run for an hour.
  8. Walk for over an hour.

8.17

  1. Improve SubscribeService/ContactService adding extra properties.
  2. Migrate mongo clients / dao base.
  3. Import articles.
  4. Check notifications.
  5. Read for an hour.
  6. Walk for over an hour.

8.18

  1. Migrate mongo clients and db related modules.
  2. Import articles.
  3. Check notifications.
  4. Data etl for contactAgents/deviceInfo.
  5. Read for half an hour.
  6. Run for an hour.
  7. Walk for over an hour.

8.19

  1.  Migrate model and db related modules.
  2. Import articles.
  3. Check notifications.
  4. Research command pattern.
  5. Read for half an hour.
  6. Run for an hour.
  7. Walk for over an hour.

8.22

  1. Migrate common modules.
  2. Research command pattern.
  3. Import articles.
  4. Check notifications.
  5. Read for an hour.
  6. Run for an hour.
  7. Walk for over an hour.

8.23

  1. Migrate common packages to make micro service arch work.
  2. Finish reading ‘folding Beijing’.
  3. Import articles.
  4. Check notification.
  5. Walk for over an hour.

8.24

  1. Migrate common packages to make micro service arch work.
  2. Read for an hour.
  3. Run for an hour.
  4. Import articles.
  5. Check notifications.
  6. Walk for over an hour.

8.25

  1. Migrate common packages.
  2. Import articles.
  3. Check notifications.
  4. Research micro services.
  5. Read for an hour.
  6. Walk for over an hour.

8.26

  1. Finish common package migration.
  2. Import articles.
  3. Check notifications.
  4. Research micro services.
  5. Read for an hour.
  6. Walk for over an hour.

At weekend, I read on the first day and attend classmate’s marriage, best wishes to them. The second day, I was coding all day long, also recalled things about life, works happened recent, for me stay alone is relax. Besides, I run, talked with Guo, called home as usual.

8.29

  1. Refactor notification push mechanism.
  2. Development of recording mortgage informs while contact agents and put it online.
  3. Import articles.
  4. Check notifications.
  5. Read for an hour.
  6. Run for an hour.
  7. Walk for over an hour.

8.30

  1. Update mechanism of notification push.
  2. Research template pattern.
  3. Import articles.
  4. Check notifications.
  5. Upgrade article upload scripts. more automatic and smarter.
  6. Read for an hour.
  7. Walk for over an hour.

8.31

  1. Update mechanism of notification push.
  2. Import articles
  3. Check notifications.
  4. Refactor email alias/title.
  5. Check mortgage service load balance.
  6. Split major child service.
  7. Check health checks from cabot and improve the insufficient.
  8. Upgrade notification push monitor.
  9. Read for an hour.
  10. Run for an hour.
  11. Walk for over an hour.

9.1

  1. Extract share service.
  2. Analysis of device/agent data.
  3. Refactor notification service, mainly adjust inheritance.
  4. Import articles.
  5. Check notifications.
  6. Read for an hour.
  7. Walk for over an hour.
  8. Watch ‘Pacific War’.

9.2

  1. Extract and archive share service as clild service.
  2. Deploy new notification push system and check it out.
  3. Read for an hour.
  4. Run for an hour.
  5. Walk for over an hour.

9.5

  1. Release new notification system and check it out.
  2. Finish ShareService migration.
  3. Migrate SunService.
  4. Generate swagger client for ShareService.
  5. Research effective java.
  6. Import articles.
  7. Read for an hour.
  8. Run for an hour.
  9. Walk for over an hour.

9.6

  1. Finish SunService migration.
  2. Import articles.
  3. Check notifications.
  4. Initialize SunService deployment steps.
  5. Research and record effective java.
  6. Read for an hour.
  7. Run for an hour.
  8. Walk for over an hour.

9.7

  1. Learn about akka.
  2. Import articles.
  3. Check notifications.
  4. Read for an hour.
  5. Run for an hour.
  6. Walk for over an hour.

9.8

  1. Learn about akka.
  2. Refactor fabric scripts for micro services.
  3. Import articles.
  4. Check notifications.
  5. Run for an hour.
  6. Walk for over an hour.

9.9

  1. Refactor deployment scripts, mainly extract the complicate process and shutdown service safely.
  2. Import articles.
  3. Check notifications.
  4. Read for an hour.
  5. Walk for over an hour.
  6. Research akka.
  7. Record jvmtop development notes.

9.12

  1. Improve article monitor scripts to record increase rate.
  2. Learn about spark/mongodb framework.
  3. Development of upload docx article api.
  4. Read for an hour.
  5. Walk for over an hour.

9.13

  1. Development of upload docx article api.
  2. Import articles.
  3. Check notifications.
  4. Data etl about account/contact informs.
  5. Learn about @SpringBootApplication annotation and refactor the codes. (http://docs.spring.io/spring-boot/docs/current/reference/html/using-boot-using-springbootapplication-annotation.html)
  6. Read for an hour.
  7. Run for an hour.
  8. Walk for over an hour.

9.14

  1. Data for agents / device informs.
  2. Development of article upload, mainly about data migration.
  3. Import articles.
  4. Check notifications.
  5. Run for an hour.
  6. Read for an hour.
  7. Walk for over an hour.

~ mid-autumn festival ~

9.18

  1. Finish development of article transform.
  2. Configure log archive for log4j using maxBackupIndex property.
  3. Import articles.
  4. Check notifications.
  5. Refactor article monitor, mainly focus on the increase rate.
  6. Added collectd for notification/buyerinfo services, learn more about docker registry.
  7. Read for an hour.
  8. Run for an hour.
  9. Walk for over an hour.