DannyDannyDanny/Methodology

This guide focuses on designing, developing and delivering Data-Processing Sytems, written primarily in python, deploying to Linux servers, optionally communicating with external interfaces (APIs or DBs). The repo is actively being updated; bookmark 🔖 it, leave a Star ⭐ or Watch 👁️ the repo.

• repo roadmap
  • 🔴🟡🟢 example process roadmap
• gitmoji
• planning
• ideation / design (coming soon)
  • design process
• development
• documentation
• Deployment (coming soon)
• Launch (coming soon)
• Maintenance (coming soon)
• cloud engineering
• data management
• tools 🚧
• philosophy
• scripts
  • emoji_shortlist

roadmap

• 2022Q3: Consultancy & Delivery Methodology
  • Planning
  • taiga.ai learning lessons Contract clauses, Project phases, Deliverables
• 2023Q1: Data Management Methodology

gitmoji reference

Use the format :gitmoji: <commit message> in your commit messages. Or follow conventional commits. Only proper nouns, CamelCase and class names should have uppercases letters. Use several gitmojis if it makes sense.

emoji	code	description
✨	:sparkles:	add new feature / function
🎨	:art:	refactor / type hinting / restructuring / linting
🥅	:goal_net:	try/raise/handle errors or warnings
⚡	:zap:	improve performance / coverage / profiling
🐛	:bug:	bug fixing
🚚	:truck:	moving / renaming
♻️	:recycle:	CI/CD, pre-commit hooks, auto-tests and environments
💥	:boom:	work in progress / breaking changes
📝	:memo:	doc / logging / verbosity / code comments
🔥	:fire:	remove (dead) code / file
👽	:alien:	changes related to APIs, Databases, Network etc.
🔑	:key:	security, user access, roles
🎉	:tada:	clean / transform / validate data
👀	:eyes:	UI / UX / CLI / visualizations (previously 💄)
🧠	:brain:	statistical modelling, training and prediction
📌	:pushpin:	dependency and environment versioning
🐳	:whale:	docker, VMs, containerization and architecture changes
🙈	:see_no_evil:	changes to .*ignore or local files
🔍	:mag:	PR-review change-requests

Missing a gitmoji? Take a look at word emojis with short shortcodes made by this script this script Submit an issue (or Pull Request).

git version control

• repo naming conventions
  • lowercase
  • dashes not underscores
  • name pattern: <prefix>_<suffix>
    • <prefix> i.e. drug, condition, indication, area (reserach, clinical)
    • <suffix> i.e. project name, tool, exploration name
• init repo with README
  • must have sections: purpose, usage and stakeholders sections
  • good to have: install, contributing
• git rules for simple development
  • no branching
  • no rebasing
  • no public repos
  • no data in repo