Skip to content

Dev Log 06.08~06.14 (en)

365kim edited this page Jun 14, 2020 · 2 revisions

12 June (Fri)

🐾 THINKING

  • Design a DB for the YEALY schedule page
    • Have to decide how to divide Fron and Back-end teams and which parts to take on.
    • In Front-end part, Have to decide whether to implement all of the parts purely using HTML, CSS or using bootstrap and library.
    • Have to decide whether to use a template such as jade, pug, or ejs for view.

🐾 LEARNED

  • Using express, I found that code is compact and I can simplify the connection with the database.
  • Can integrate MySQL in nodeJS and process the data through query statements.
  • Can write HTML, CSS using JavaScript.
  • Can write a table and understand elements(th, tr, td).
  • Understanding MVC patterns

🐾 DECIDED

  • Tue - Sat, screen sharing is progressed through google hangout until 10AM to 17PM, so we can respond anytime.
  • Efficient development is conducted using the design pattern.
  • Until next Monday, the common learning part is completed and development begins
  • Dev env
    • Framework : nodeJS express
    • Language : JavaScript
    • Database : MySQL
    • Database tool : workbench


09 June (Tue)

🐾 THINKING

  • Have to decide about painting the main page.
    • The default calendar standard is the YEARLY form.
  • Have to establish guidelines on how to progress of project after DB, server development.
  • Have to make a discussion for Dev Environment.

🐾 LEARNED

  • Learned the roles and functions of Github elements while writing issues, pull-request, and kanban board.

🐾 DECIDED

  • Meeting

    • Start : From 15 June 20, exception of weekend
    • Time : 10:00 ~
    • Location: youthzone, Gaepo-dong, Gangnam-gu, Seoul
    • Purpose : code review, conference
  • Establishing a wiki guideline

    • Integrated management of links to sharing useful links page on the Wiki.
    • Write dev-logs in one document and manage them in order of date.
    • As a rule, issues, pull requests, and comments should be written in English. Wiki be written in English and Korean versions.
    • Automatic deletion is not performed to keep branches or delete them freely.
  • GitHub Cooperation environment setting

    • Work process is managed by issue, pull request, and kanban board.
    • Established Git convention through discussion.
  • Assigning roles

    • taelee42 : Wrote our service introduction page.
    • 365kim : designed Wiki and page structure, gathered useful links.
    • hidaehyunlee: Wrote Git and code conventions.
    • seongsangCHO : Wrote this dev-log.
  • To do

    • Understand web, server and database.
    • Until the meeting (15 June (Mon), 5 tracks are implemented, and pull-requests are created.
    • Design while learning individual Database or for the page.
    • Server implementation and running server.
    • Let's write it from issue to pull request to get used to it!