edtsech

[  
  {
    "key": "cmd+s",
    "command": "macros.saveAndExitVimInsertMode"
  }
]

edtsech

This is a proposal for a lightning talk at Reactive Conf. Please 🌟 this gist to push the proposal!

Combining snapshot testing and component library

Do you test presentational logic of your components? No? Yes, but you feel like you are writing a lot of dummy tests? You even probably use snapshot tests for that, but don't feel like you make enought value from them..

If so, click 🌟 button on that Gist!

I'll talk how our team is using snapshot testing to iterate faster,

edtsech

h1 = { "a" => 100, "b" => 200 }
h2 = { "b" => 254, "c" => 300 }
h3 = h1.merge(h2)   
h3 #=> {"a"=>100, "b"=>254, "c"=>300}
h1 #=> { "a" => 100, "b" => 200 }

edtsech

import React from 'react'
import * as ReactQuill from 'react-quill'

import { merge } from 'lodash'

import 'react-quill/dist/quill.snow.css'

const QUILL_MODULES = {
  toolbar: [
    ['bold', 'italic', 'underline'],

edtsech

People frequently blame retrospectives being unproductive and boring. But it’s the same as blaming Vodka for getting drunk. Execution is the key.

Some stuff people say about retrospectives:

“I hate scrum and everything about it”

Retrospectives don’t come from Scrum. They don’t even come from Agile. If you know continuous improvement approach sometimes fancy called Kaizen, initially implemented in Toyota it comes from there. But the idea of retrospectives is probably as old as the world.

![cycle](https://ucbbfb7ed7b11596645e3b3e61d6.previews.dropboxusercontent.com/p/thumb/AA0DNRBX2JC_7hLLhtGWL-2__rgfZ00Bjj6-P-AGHaIOWLemQIrmKczW-EbDd4tjIwcMJji2sJrLMK-Y8QR-efkTMu85MDYFNqcn8Fd6wM6uMnYpggcwuA5VhGnqhnB7ZMDv7LdFiDb_HAtWfiAMRShbuQOuJKp0hxBe33IkkRBypRDnpfesZo03oTg5Jjyu9oqJpXSETDJTxE4Lap6tEJ9etX8gc79S9arkLXJj_aUTHq17YCNBTOhyiTKbvs6PyrEPdmH3jTazRF1NAIwrKUhm4f5oT1PbRAXELsveGFQthOFs91Pb3DOt73NsznSAPefL-EGofeL-TfKfj_5YsBejpphwg4aaaA5oT1ci3AVfJWrGdsLVkQtT7k4uzAtu1ETn6dua7Hpb_2LKBuElgKFT/p.jpeg?fv_content=true&s

edtsech

title	published	description	tags
Thoughts on Retrospectives	false		agile, scrum, retro

People frequently blame retrospectives being unproductive and boring. But it’s the same as blaming Vodka for getting drunk. Execution is the key.

edtsech

/// <reference types="cypress"/>
import createEmptyDb from '../../../back-end/test/create-empty-db'

describe('Demo test', () => {
  before(async () => {
    await createEmptyDb()
  })

  ...
})

edtsech

  @Field({
    type: () => TopicEnrolmentModel,
    description: `creates a new enrolment if retries are allowed`
  })
  async reEnrol(
    @Context ctx: UserSessionModel
  ) {
    const tv = await this.$relatedQuery('currentTopicVersion')

    if (tv.allow_retry) {

edtsech

const _ = require('lodash')
const ts = require('typescript')
const config = require('./tsconfig.json')

let exitStatus = 0
const files = process.argv.slice(2)
const compilerOptions = _.omit(config.compilerOptions, ['moduleResolution'])
compilerOptions.noEmit = true
compilerOptions.lib = ['lib.dom.d.ts']

edtsech

Weekly update 17.08.2018

FlyPrivate

DiamondBank & GTBank integration

- We went through couple of iterations regarding API design with both banks.
- We were able to unify the API so we don't have to develop it twice.
- We've provided demo API gateway to them. They can use it for integration process.
- On Monday we starting to develop API according to the specification we discussed with them.