Skip to content

Instantly share code, notes, and snippets.

View blueoc-phucpham's full-sized avatar

blueoc-phucpham

View GitHub Profile
@blueoc-phucpham
blueoc-phucpham / main.py
Last active January 25, 2024 04:05
POC import / export
from fastapi import FastAPI, Depends, UploadFile
from fastapi.responses import StreamingResponse
import xlsxwriter
import io
from openpyxl import load_workbook
from openpyxl.worksheet.worksheet import Worksheet
from typing import List, Dict
class ExcelService:
./app/api/admin_v2/comments.py: status.HTTP_404_NOT_FOUND, "The current time period don't have this employee"
./app/api/admin_v2/comments.py: status.HTTP_404_NOT_FOUND, "You are not the reviewer of this employee in current time period"
./app/api/admin_v2/comments.py: status.HTTP_404_NOT_FOUND, "You are not allowed to create comment"
./app/api/admin_v2/comments.py: status.HTTP_404_NOT_FOUND, "Comment not found"
./app/api/admin_v2/comments.py: status.HTTP_404_NOT_FOUND, "You are not authorized to update this comment"
./app/api/admin_v2/comments.py: status.HTTP_404_NOT_FOUND, "You are not authorized to delete this comment"
./app/api/admin_v2/sessions.py: status.HTTP_400_BAD_REQUEST, "Time period already exists"
./app/api/admin_v2/sessions.py: status.HTTP_400_BAD_REQUEST, "Can't create time period for past year"
./app/api/admin_v2/sessions.py: status.HTTP_400_BAD_REQUEST, "Can't create time period for past quarter"
./app/api/admin_v2/sessions.py: status.HTTP_404_NOT_FOUND, "Time period not found"
@blueoc-phucpham
blueoc-phucpham / draft.md
Created January 31, 2024 04:04
Table design

GoalKR

  • Cần có attachment và comment riêng
  • Cần có status (các status nào?)
  • Cần có weight

Câu hỏi

  • Có cần duedate riêng không?
  • Có cần được approved bởi manager?
@blueoc-phucpham
blueoc-phucpham / main.py
Last active February 29, 2024 09:56
autogen report
# against jira.atlassian.com.
from __future__ import annotations
from jira import JIRA
from enum import Enum
from typing import DefaultDict, List
from collections import defaultdict
@blueoc-phucpham
blueoc-phucpham / postgresql_plus_arch-linux.md
Created March 27, 2024 01:40 — forked from NickMcSweeney/postgresql_plus_arch-linux.md
Getting postgresql running on Arch Linux

Setup Postgresql

run postgresql with systemctl

Install postgres

latest

sudo pacman -S postgresql

specific version

find version & build from source

Story points explained

This document describes what different story points mean in practice. By design, story points are not supposed to be connected to units of time (hours, days or weeks). They are meant to be relative units which give a rough understanding of the amount of work required to complete a story. Story points between different teams, departments and companies should never be compared.

Team A delivering 100 story points in a sprint might actually be much more than Team B delivering 200 story points because the teams don’t share a standardised definition what 1 story point means. By no means is this an attempt to create such a standardisation, but to give us a guideline what to follow when estimating stories.

For all stories, the pull request still needs to be reviewed, automated tests have to pass and a new version get deployed to be able to mark it as completed. This is an overhead that should be included in all estimates. Sometimes this overhead takes much more time than completing the ac