saurabh2590

Talk was in general was quick walkthrough of cool features of Webpack 2. Mentioning some of the stuff not used in our code and very cool guidelines for improving production code in terms of output, assembly, assets, css etc. In summary, we might need an expert on Webpack2 to review for us later to apply best possible techniques.

• The content was based on the book authored by Juho Vepsäläinen (https://github.com/bebraw) who is the core team member of Webpack and main driver behind @SurviveJS effort.
• All the things he talked are explained in detail on https://survivejs.com/webpack/introduction/

Cool plugins mentioned

• webpack-merge: Cool plugin for merging and selecting configuration specially for production & development mode config files.
• purify-css/ purify-css-webpack / uncss: To removed unused CSS in the output code.
• stylelint/csslint : To applying linting rules on CSS files similarly to our code.
• AggressiveSplittingPlugin/http2-aggressive-splitting : Cool plugin to take advan

saurabh2590

Good
- good introduction about the project.
- Clear specifications on the priorities of the tasks
- On boarding process seems to be more robust.
- Pair programming sessions with colleagus.
- Opennes to innovation.
Bad
- Focus on finishing the stories & ambiguity, lagging behind MVP.
- Less focus on UX/UI
- Less comfortable with esitmations due to no background knowledge.

saurabh2590

const settings = (mode === 'production') ? JSON.stringify(require('./src/config/settings.prod.json')) : JSON.stringify(require('./src/config/settings.dev.json'));

module.exports = {
  context: path.resolve('./src'),
  entry: {
    vendor: ['react', 'pouchdb', 'redux', 'whatwg-fetch'],
    demo_app: './init.tsx'
  },
  output: {
    path: path.resolve('./dist'),

saurabh2590

1. Certain namespace and naming was repeated and hence proposal for folder structure:

• Every ts(x) file have it's sibling as .spec.ts(x) file.
• gizmos
  • fraction-pie
    • renderer
      • styles.scss
      • internal files such as index etc.
      • sub-renderers
    • editor
• styles.scss

saurabh2590

Facilitator: Ya'ar
Circleci FYI: Only PR linked commits are build.
Components proposal: Proposed separate components in trac for the seriesplayer, gizmos, components etc. Not put everything in Worksheet&Generator.
Need to inform other teams. Product and Dev.
- Identifying the stake holders is important.
- Create new components => YXY/MKL
Converting MathCore:
- Kotlin: Details => very modern language, translation to JS is nearly perfect with it's own tool from original code.
- Backed by stronger company, design of language is better.
- With JSWeet: Looks like writing JS with Java.

saurabh2590

• Write a ReactComponent, which displays the (x, y) values in a table.
  • Assume, the values are provided by API in redux store, implying that they are available initialState. The value for x and y are calculated as follow:
    • x : any random number between 1-10
    • y : random combination of x characters from [a-z,A-Z].
    • Example: [{x: 3, y: 'aie'}, {x: 7, y: 'Zaqopkl'}, {x: 4, y: 'ASDU'}]
  • Implement the following functionality on table:
    • When clicked on the column header, values are sorted first incrementally, and each click then toggles the sort order.
• If have time, then write tests for the code we created. (If prefers test driven approach and can start with TDD.)

saurabh2590

Example:

• We might need to first align our goals and end state and then come up with project plan + task list.
• This is just an example template to say that we can try to get such list of tasks in order of priority and if possible efforts.

Dev tasks:

• Make apps configurable to work with Mongo or DynamoDB
• DWH connector changes?
• Chaning report architecure to make on Demand?

Create build jobs as container based for current active jobs on Jenkins to enable migration to Codebuild/Codepipeline

saurabh2590

optimization: {
    minimize: isProductionMode,
    minimizer: [
      getUglifyJSplugin()
    ],
    runtimeChunk: 'multiple',
    splitChunks: {
      cacheGroups: {
        vendor: {
          test: /[\\/]node_modules[\\/]/,

saurabh2590

• KEM UI specifications/FEM UI Specifications.
• UI specifications for Desktop screens for all the stories.
• Review mode for student/teacher is missing for the specification. (Story?/Spec?)
  • Shall we only show single attempts?
  • Mutliple attempts?
• Calculator specifications:
  • UI?
  • Functional?

saurabh2590

• KEM UI specifications/FEM Specifications.
  • FEMs: Feasible to use Gizmo. simple and possible to use same as hints
  • KEMs:
    • Old history of design elements
    • Need adjustments from ConDev potentially to fit new design concepts from Sven.
    • Structure vs design are not matching?? => Need clean up from ConDev as well. (Can we estimate the effort for ConDev?)
    • Action Item:
      • Prepare the plain text version and style with minimal effort.
      • Discuss if when we should trigger this conversation with ConDev.