Code Monkey home page Code Monkey logo

jgoerner / corona-hackathon Goto Github PK

View Code? Open in Web Editor NEW
12.0 0.0 0.0 15.47 MB

🦠🤖🧪#WirVsVirus Corona-Crisis Hackathon - organized by the German government. SWAG (Smart Workforce Allocator Germany) helps to mitigate this imbalance and directly connects employer and employees, building on the principles ease of use, flexibility & optimized allocation.

Home Page: https://swag-vs-virus.herokuapp.com/

Java 11.44% Dockerfile 0.24% Makefile 0.16% Python 1.15% JavaScript 71.70% TypeScript 10.94% HTML 3.87% CSS 0.50%
corona covid-19 wirvsvirus swag hackathon ant-design spring-boot ddd knowledge-is-power ports-and-adapters

corona-hackathon's Introduction

Just do nail it 👌

ℹ️ TL;DR

// Staff Product Engineer // Ex Data-Scientist // Online Tutor // Open Source Enthusiast // Father //


🎯 Personal Mantra

Bias towards action + excellent execution = Just do nail it 👌


📜 Experience

I the past decade was able to work with smart & humble people...
    ... across various industries like pharma & health care in general, automotive or aerospace
    ... within global organizations (100.000+ people) as well as seed-funded startups
    ... on throw-away POCs as well as customer facing and globally used applications


🦸‍ Personal Superpower

I would describe myself as a T-shaped generalist working between product & engineering.

So Josh, what makes you special?

I guess my personal niche of expertise is relentless innovation. While I'm not the best product manager, engineer or designer I do excel when pulling methods & tools from all of them together to craft new and delightful experiences 👌


🔑 Key Achievements

Some of my personal professional highlights include that I ...
    ... bootstrapped a x-functional team & led full the full product lifecycle, launching a new product in < 6 months with ~ 30% WAU
    ... co-authored a patent for keyless car access - deployed in global BMW fleet since mid 2020
    ... authored the MOOC Beyond Jupyter Notebooks - as of today ~ 3.000 students and 4.9 ⭐️ rating

corona-hackathon's People

Contributors

delsner avatar floro91 avatar jgoerner avatar lschlesinger avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

corona-hackathon's Issues

CI/CD Pipeline

📃 Description

To be able to better understand what an issue is about, one shall provide some further guidance.
This is what the Description is about

This issue deals with ...

🚧 Definition of Ready

To be able to parallelise the work, one has to ensure, that the issues are atomic and contain all information that are needed. The Definition of Ready is a checklist which has to be completed, before the issues should be worked on.

The issue ...

  • ... has an expressive title
  • ... has a concise description
  • ... has a content label (e.g. infrastructure, frontend, backend, ...)
  • ... has a difficulty label (e.g. easy, medium, hard, ...)
  • ... is linked to the global task board
  • ... has a definition of done

✅Definition of Done

To be able to objectively judge, whether a task is done or not, certain acceptance criteria have to be defined. This is what the Definition of Done is about.

  • ...

Define Schema

📃 Description

To be able to better understand what an issue is about, one shall provide some further guidance.
This is what the Description is about

This issue deals with the domain schema of the application.

🚧 Definition of Ready

To be able to parallelise the work, one has to ensure, that the issues are atomic and contain all information that are needed. The Definition of Ready is a checklist which has to be completed, before the issues should be worked on.

The issue ...

  • ... has an expressive title
  • ... has a concise description
  • ... has a content label (e.g. infrastructure, frontend, backend, ...)
  • ... has a difficulty label (e.g. easy, medium, hard, ...)
  • ... is linked to the global task board
  • ... has a definition of done

✅Definition of Done

To be able to objectively judge, whether a task is done or not, certain acceptance criteria have to be defined. This is what the Definition of Done is about.

  • high level schema in place
  • convert to db schema

FE setup with framework and dependencies + project structure

📃 Description

To be able to better understand what an issue is about, one shall provide some further guidance.
This is what the Description is about

The initial setup of a FE project with application framework, necessary libraries and infrastructure (e.g. container).

🚧 Definition of Ready

To be able to parallelise the work, one has to ensure, that the issues are atomic and contain all information that are needed. The Definition of Ready is a checklist which has to be completed, before the issues should be worked on.

The issue ...

  • ... has an expressive title
  • ... has a concise description
  • ... has a content label (e.g. infrastructure, frontend, backend, ...)
  • ... has a difficulty label (e.g. easy, medium, hard, ...)
  • ... is linked to the global task board
  • ... has a definition of done

✅Definition of Done

To be able to objectively judge, whether a task is done or not, certain acceptance criteria have to be defined. This is what the Definition of Done is about.

  • subdirectory in main project repository for FE
  • dependency management (via npm) in place with framework (Angular) and dependencies (NG ZORRO Ant Design)
  • Dockerfile for containerization of FE (with NGINX)
  • Update ADRs for decisions taken

DB Schema Requirements

📃 Description

To be able to better understand what an issue is about, one shall provide some further guidance.
This is what the Description is about

This issue deals with information that should come from the database.

What tables? What columns? What Information?

🚧 Definition of Ready

To be able to parallelise the work, one has to ensure, that the issues are atomic and contain all information that are needed. The Definition of Ready is a checklist which has to be completed, before the issues should be worked on.

The issue ...

  • ... has an expressive title
  • ... has a concise description
  • ... has a content label (e.g. infrastructure, frontend, backend, ...)
  • ... has a difficulty label (e.g. easy, medium, hard, ...)
  • ... is linked to the global task board
  • ... has a definition of done

✅Definition of Done

To be able to objectively judge, whether a task is done or not, certain acceptance criteria have to be defined. This is what the Definition of Done is about.

  • list of required tables / columns / etc.

Create Rule-based Matching Module

📃 Description

To be able to better understand what an issue is about, one shall provide some further guidance.
This is what the Description is about

This issue deals with the module for matching employees and jobs based on selection rules and returning a score for the the employee-job combination

🚧 Definition of Ready

To be able to parallelise the work, one has to ensure, that the issues are atomic and contain all information that are needed. The Definition of Ready is a checklist which has to be completed, before the issues should be worked on.

The issue ...

  • ... has an expressive title
  • ... has a concise description
  • ... has a content label (e.g. infrastructure, frontend, backend, ...)
  • ... has a difficulty label (e.g. easy, medium, hard, ...)
  • ... is linked to the global task board
  • ... has a definition of done

✅Definition of Done

To be able to objectively judge, whether a task is done or not, certain acceptance criteria have to be defined. This is what the Definition of Done is about.

  • Module queries mock-data from postgresql db
  • Module calculates a score based on hard-rules (e.g. german speaking, drivers license)
  • Module calculates the distance between job and employee zip code
  • Module returns a df with employee_id, job_id and score

Implement Real Persistence

📃 Description

To be able to better understand what an issue is about, one shall provide some further guidance.
This is what the Description is about

This issue deals with implementing real services & outgoing ports.

🚧 Definition of Ready

To be able to parallelise the work, one has to ensure, that the issues are atomic and contain all information that are needed. The Definition of Ready is a checklist which has to be completed, before the issues should be worked on.

The issue ...

  • ... has an expressive title
  • ... has a concise description
  • ... has a content label (e.g. infrastructure, frontend, backend, ...)
  • ... has a difficulty label (e.g. easy, medium, hard, ...)
  • ... is linked to the global task board
  • ... has a definition of done

✅Definition of Done

To be able to objectively judge, whether a task is done or not, certain acceptance criteria have to be defined. This is what the Definition of Done is about.

Implement real services and all needed downstream Ports & Adapters, which are currently mocked here:

Prepare Submission Process

📃 Description

To be able to better understand what an issue is about, one shall provide some further guidance.
This is what the Description is about

This issue deals with official guidelines on how to submit the project.

🚧 Definition of Ready

To be able to parallelise the work, one has to ensure, that the issues are atomic and contain all information that are needed. The Definition of Ready is a checklist which has to be completed, before the issues should be worked on.

The issue ...

  • ... has an expressive title
  • ... has a concise description
  • ... has a content label (e.g. infrastructure, frontend, backend, ...)
  • ... has a difficulty label (e.g. easy, medium, hard, ...)
  • ... is linked to the global task board
  • ... has a definition of done

✅Definition of Done

To be able to objectively judge, whether a task is done or not, certain acceptance criteria have to be defined. This is what the Definition of Done is about.

  • edit project on DevPost
  • documentation is ready
  • demo is ready
  • delta to production readiness

Adjust USP of Readme

📃 Description

To be able to better understand what an issue is about, one shall provide some further guidance.
This is what the Description is about

This issue deals with refining the USP section of the readme.

🚧 Definition of Ready

To be able to parallelise the work, one has to ensure, that the issues are atomic and contain all information that are needed. The Definition of Ready is a checklist which has to be completed, before the issues should be worked on.

The issue ...

  • ... has an expressive title
  • ... has a concise description
  • ... has a content label (e.g. infrastructure, frontend, backend, ...)
  • ... has a difficulty label (e.g. easy, medium, hard, ...)
  • ... is linked to the global task board
  • ... has a definition of done

✅Definition of Done

To be able to objectively judge, whether a task is done or not, certain acceptance criteria have to be defined. This is what the Definition of Done is about.

  • Include "batteries included" character
  • Refine section about Matching Algorithm

Define REST API in BE to be used from FE

📃 Description

To be able to better understand what an issue is about, one shall provide some further guidance.
This is what the Description is about

We need to define the REST API with (i) endpoints and (ii) types early, to start developing the FE stubs (or be able to generate them).

🚧 Definition of Ready

To be able to parallelise the work, one has to ensure, that the issues are atomic and contain all information that are needed. The Definition of Ready is a checklist which has to be completed, before the issues should be worked on.

The issue ...

  • ... has an expressive title
  • ... has a concise description
  • ... has a content label (e.g. infrastructure, frontend, backend, ...)
  • ... has a difficulty label (e.g. easy, medium, hard, ...)
  • ... is linked to the global task board
  • ... has a definition of done

✅Definition of Done

To be able to objectively judge, whether a task is done or not, certain acceptance criteria have to be defined. This is what the Definition of Done is about.

  • list of required endpoints

Napkin Drafts for UI

📃 Description

To be able to better understand what an issue is about, one shall provide some further guidance.
This is what the Description is about

This issue deals with sketching very basically the UI, supporting the core domain story.

(In the times of 🧻 shortage a digital sketch should also work)

🚧 Definition of Ready

To be able to parallelise the work, one has to ensure, that the issues are atomic and contain all information that are needed. The Definition of Ready is a checklist which has to be completed, before the issues should be worked on.

The issue ...

  • ... has an expressive title
  • ... has a concise description
  • ... has a content label (e.g. infrastructure, frontend, backend, ...)
  • ... has a difficulty label (e.g. easy, medium, hard, ...)
  • ... is linked to the global task board
  • ... has a definition of done

✅Definition of Done

To be able to objectively judge, whether a task is done or not, certain acceptance criteria have to be defined. This is what the Definition of Done is about.

  • drafts for UI

Create initial routing structure in FE

📃 Description

To be able to better understand what an issue is about, one shall provide some further guidance.
This is what the Description is about

This issue builds upon #11 to put the napkin draft into a routing structure.

🚧 Definition of Ready

To be able to parallelise the work, one has to ensure, that the issues are atomic and contain all information that are needed. The Definition of Ready is a checklist which has to be completed, before the issues should be worked on.

The issue ...

  • ... has an expressive title
  • ... has a concise description
  • ... has a content label (e.g. infrastructure, frontend, backend, ...)
  • ... has a difficulty label (e.g. easy, medium, hard, ...)
  • ... is linked to the global task board
  • ... has a definition of done

✅Definition of Done

To be able to objectively judge, whether a task is done or not, certain acceptance criteria have to be defined. This is what the Definition of Done is about.

  • every route mentioned in napkin draft is included (no auth yet)
  • top nav bar
  • side bar
  • heading for each route

Remodel core domain story

📃 Description

To be able to better understand what an issue is about, one shall provide some further guidance.
This is what the Description is about

This issue deals with remodelling the core domain domain story.

🚧 Definition of Ready

To be able to parallelise the work, one has to ensure, that the issues are atomic and contain all information that are needed. The Definition of Ready is a checklist which has to be completed, before the issues should be worked on.

The issue ...

  • ... has an expressive title
  • ... has a concise description
  • ... has a content label (e.g. infrastructure, frontend, backend, ...)
  • ... has a difficulty label (e.g. easy, medium, hard, ...)
  • ... is linked to the global task board
  • ... has a definition of done

✅Definition of Done

To be able to objectively judge, whether a task is done or not, certain acceptance criteria have to be defined. This is what the Definition of Done is about.

  • reformat existing process steps
  • optimize reuse of icons
  • add notes where needed
  • rewrite title and description
  • upload new png & dst file
  • adjust readmde

Aftermath Documentation

📃 Description

To be able to better understand what an issue is about, one shall provide some further guidance.
This is what the Description is about

This issue deals with creating a dignified aftermath post on our approach, our setup, lessons learned, etc.

🚧 Definition of Ready

To be able to parallelise the work, one has to ensure, that the issues are atomic and contain all information that are needed. The Definition of Ready is a checklist which has to be completed, before the issues should be worked on.

The issue ...

  • ... has an expressive title
  • ... has a concise description
  • ... has a content label (e.g. infrastructure, frontend, backend, ...)
  • ... has a difficulty label (e.g. easy, medium, hard, ...)
  • ... is linked to the global task board
  • ... has a definition of done

✅Definition of Done

To be able to objectively judge, whether a task is done or not, certain acceptance criteria have to be defined. This is what the Definition of Done is about.

  • Small intro about Hackathon
  • Short bio about us
  • PM & Comms Tool Setup (Slack, GH, ADR, Domain Stories)
  • Technology Stack
  • Main Learnings
  • Individual Feedback
  • AOB

Application Component Container

📃 Description

To be able to better understand what an issue is about, one shall provide some further guidance.
This is what the Description is about

This issue deals with major container that the application is composed of.

A possible first best guess (to be approved/rejected/refined):

  • Frontend: Nginx Container
  • Backend: Java Container
  • Matcher AI: Flask Container
  • Database: Postgres Container

🚧 Definition of Ready

To be able to parallelise the work, one has to ensure, that the issues are atomic and contain all information that are needed. The Definition of Ready is a checklist which has to be completed, before the issues should be worked on.

The issue ...

  • ... has an expressive title
  • ... has a concise description
  • ... has a content label (e.g. infrastructure, frontend, backend, ...)
  • ... has a difficulty label (e.g. easy, medium, hard, ...)
  • ... is linked to the global task board
  • ... has a definition of done

✅Definition of Done

To be able to objectively judge, whether a task is done or not, certain acceptance criteria have to be defined. This is what the Definition of Done is about.

  • specify application structure
  • setup a docker-compose.yml accordingly
  • setup flask API & handler skeletons

Create Mock Dataset / Data Service

📃 Description

To be able to better understand what an issue is about, one shall provide some further guidance.
This is what the Description is about

This issue deals with a minimal BE setup to enable development on the FE & Matching components.

This issue depends on #18 and #13

🚧 Definition of Ready

To be able to parallelise the work, one has to ensure, that the issues are atomic and contain all information that are needed. The Definition of Ready is a checklist which has to be completed, before the issues should be worked on.

The issue ...

  • ... has an expressive title
  • ... has a concise description
  • ... has a content label (e.g. infrastructure, frontend, backend, ...)
  • ... has a difficulty label (e.g. easy, medium, hard, ...)
  • ... is linked to the global task board
  • ... has a definition of done

✅Definition of Done

To be able to objectively judge, whether a task is done or not, certain acceptance criteria have to be defined. This is what the Definition of Done is about.

  • Overview of implemented controllers, mapped to the requirements from #18 and #13

Zusammenfassung Infos zu Arbeitslosigkeit

📃 Description

To be able to better understand what an issue is about, one shall provide some further guidance.
This is what the Description is about

This issue deals with ...

🚧 Definition of Ready

To be able to parallelise the work, one has to ensure, that the issues are atomic and contain all information that are needed. The Definition of Ready is a checklist which has to be completed, before the issues should be worked on.

The issue ...

  • ... has an expressive title
  • ... has a concise description
  • ... has a content label (e.g. infrastructure, frontend, backend, ...)
  • ... has a difficulty label (e.g. easy, medium, hard, ...)
  • ... is linked to the global task board
  • ... has a definition of done

✅Definition of Done

To be able to objectively judge, whether a task is done or not, certain acceptance criteria have to be defined. This is what the Definition of Done is about.

  • ...

Split Core User Story into Bounded Contexts

📃 Description

To be able to better understand what an issue is about, one shall provide some further guidance.
This is what the Description is about

This issue deals with splitting the core domain story into smaller bounded contexts

This issue depends on #8

🚧 Definition of Ready

To be able to parallelise the work, one has to ensure, that the issues are atomic and contain all information that are needed. The Definition of Ready is a checklist which has to be completed, before the issues should be worked on.

The issue ...

  • ... has an expressive title
  • ... has a concise description
  • ... has a content label (e.g. infrastructure, frontend, backend, ...)
  • ... has a difficulty label (e.g. easy, medium, hard, ...)
  • ... is linked to the global task board
  • ... has a definition of done

✅Definition of Done

To be able to objectively judge, whether a task is done or not, certain acceptance criteria have to be defined. This is what the Definition of Done is about.

  • define different bounded contexts
  • document each bounded context (may get some inspirations from this canvas)
  • map the core domain story steps to the bounded contexts

Branching Mode

📃 Description

To be able to better understand what an issue is about, one shall provide some further guidance.
This is what the Description is about

This issue deals with the question, how we branch during development.

🚧 Definition of Ready

To be able to parallelise the work, one has to ensure, that the issues are atomic and contain all information that are needed. The Definition of Ready is a checklist which has to be completed, before the issues should be worked on.

The issue ...

  • ... has an expressive title
  • ... has a concise description
  • ... has a content label (e.g. infrastructure, frontend, backend, ...)
  • ... has a difficulty label (e.g. easy, medium, hard, ...)
  • ... is linked to the global task board
  • ... has a definition of done

✅Definition of Done

To be able to objectively judge, whether a task is done or not, certain acceptance criteria have to be defined. This is what the Definition of Done is about.

  • have a branching mode & rules in place
  • document the branching mode via a new ADR

Adjust Getting Involved section of Readme

📃 Description

To be able to better understand what an issue is about, one shall provide some further guidance.
This is what the Description is about

This issue deals with adjusting the "Getting Involved" section of the readme.
As of now it includes concrete steps for the users to follow - whereas it should rather be guided towards potential collaborators, pointing them to the issue list of this GH project.

🚧 Definition of Ready

To be able to parallelise the work, one has to ensure, that the issues are atomic and contain all information that are needed. The Definition of Ready is a checklist which has to be completed, before the issues should be worked on.

The issue ...

  • ... has an expressive title
  • ... has a concise description
  • ... has a content label (e.g. infrastructure, frontend, backend, ...)
  • ... has a difficulty label (e.g. easy, medium, hard, ...)
  • ... is linked to the global task board
  • ... has a definition of done

✅Definition of Done

To be able to objectively judge, whether a task is done or not, certain acceptance criteria have to be defined. This is what the Definition of Done is about.

  • remove old section
  • write appreciating paragraph about how to give us feedback

Add basic functionality to FE

📃 Description

To be able to better understand what an issue is about, one shall provide some further guidance.
This is what the Description is about

For each empty page in the FE, create the basic functionality sketched on the wireframes.

🚧 Definition of Ready

To be able to parallelise the work, one has to ensure, that the issues are atomic and contain all information that are needed. The Definition of Ready is a checklist which has to be completed, before the issues should be worked on.

The issue ...

  • ... has an expressive title
  • ... has a concise description
  • ... has a content label (e.g. infrastructure, frontend, backend, ...)
  • ... has a difficulty label (e.g. easy, medium, hard, ...)
  • ... is linked to the global task board
  • ... has a definition of done

✅Definition of Done

To be able to objectively judge, whether a task is done or not, certain acceptance criteria have to be defined. This is what the Definition of Done is about.

  • Each page has its basic structure and functionality

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.