FrontEnd: Challenges and Strategy

FrontEnd: Challenges and Strategy

Situation:

I have a fairly complex system {link}

• more than 500 tables
• FrontEnd has its own set of Challenges

At a high level, there are 2 Teams:

• Team A
  • Design - Business Process
    • Documentation files
  • Design - UI, using:
    • figma.com
    • moqups.com
• Team X
  • Developer

note: I wrote this article with the spirit of Writing for ‘Future of Me’

Strategy

To create a smooth working rhythm, I need a set of guidelines:

• define several Big Tasks, each with a specific goal
• CI / CD {Continuous Improvement / Continuous Development}

FrontEnd

• HTML
  • convert Design - UI to HTML
  • can be done using the tools above
  • or Request: to AI effectively and efficiently {the right Tone}
• JavaScript
  • the part that handles HTML
  • the part that connects to the end-point on the BackEnd

BackEnd

• Part 1: Read Data
  • simple data for Dropdown
  • data in Tabular
  • using guideline as written in article Data Model part 2 - DTO {Data Transfer Object}
• Part 2: CRUD
  • Simple data
  • Header - Detail data
  • data with columns in JSON format
• Part 3:
  • the BackEnd part that implements the Design - Business Process

notes for BackEnd:

• building each Part of the BackEnd separately helps avoid getting “stuck” on the BackEnd as a whole
• BackEnd Code can be started from the easiest part first
• in reality, some parts of the BackEnd only need “Read Data”