Skip to content

Latest commit

 

History

History
94 lines (80 loc) · 3.84 KB

acronyms-terms-and-concepts.md

File metadata and controls

94 lines (80 loc) · 3.84 KB
Raw

Acronyms, terms and concepts

Warning

There are thousands of sources that provide better explanations than my notes. However, it is helpful if you know the keywords to search for. Merge with topicfinders

Important

heavy WIP even if it may not look like it at first

The world of software developers is full of abbreviations and strange terms. This list should be a summary of the terms I have encountered so far. Some with my own explanation others with a link to further information. I hope the list helps you. Please link to the document, it may be that the document structure can change fundamentally over time. Before you can understand a technical term, you must at least have read or heard it before so that you can look it up.

  • AC, acceptance criteria Definition
  • Bol, Bill of labour aka Bill of work => Arbeitsplan
  • Dependency injection, programming technique. Definition
  • DoD, definition of Done (Scrum). Definition
  • DoR, Definition of Ready (Scrum). Definition
  • Hexagonal architecture, architecture pattern. Combine components in a way so that you can replace them "easily" e.g. grep and rg or type and cat. Definition
  • JTBD, jobs to be done: framework with focus on customer. Customers buy a product to do a job/task, solve a problem. Understand what job this is and what is needed to sell your solution to the customer.
  • Lean coffee, strcutered format for a unstructured meeting without agenda, duration limited to the time you need to drink a cup of coffee (5 to 10 minutes). Definition
  • MoSCoW method (project management) Definition
  • RACI matrix (project management). Definition
  • SBOM, Software bill of materials
  • SDLC, Systems (Software) development life circle, Definition
  • SOLID, five design principles of oop. Even you don't code oop, know them or tell at least you have heared of them. Definition
  • Stakeholdermanagement, stakeholders are the ones who can influence the project the most from the outside (e.g. money). Get in good with them and understand their needs so that the project keeps going and you don't get kicked. Note to myself: stop using steakholder management as a gag - it's not funny

A better source is Dev Encyclopedia: https://devpedia.pages.dev/

TODO

  • gts, short for google that shit

  • rlhf, short for reinforcement learning from human feedback

  • dpo direct policy optimization

  • sft supervised finetuning

  • ppo proximal policy optimization

  • hyperparameter

  • unfix https://unfix.com/

  • FaST Agile https://www.fastagile.io/fast-guide

  • Design Thinking https://en.wikipedia.org/wiki/Design_thinking

  • cynefin

  • Big o notation

  • monkey patching

  • duck typing

  • mocking

  • complex vs complicated

  • value stream mapping

  • murphys law

  • conway law

  • rest api

  • protobuf

  • grpc

  • graphql

  • effective vs efficient vs productivity

  • Dasselbe vs. das gleiche

  • mono repo

  • seed parameter

  • supervised learning

  • unsupervised learning

  • hdi, human development index alternative approach to gross domestic product

  • zen

  • koan

  • haiku

  • fuzzying

  • mutex

  • xsrf

  • cqrs

  • backpropagation

  • random forests

  • binary tree

  • Stereotype vs Prejudice (Stereotyp vs Vorurteil)

  • RAD

  • Markov Chains

  • Monte Carlo Simulation

  • Bayesian

  • Bayes' theorem

  • scafollding

  • Proof of Work (PoW)

  • Proof of Stake (PoS)

  • Proof of Concept (PoC)

  • code coverage

  • seed paramter