ACK | ACKnowledgement | Agreed/accepted change. A loose ACK can be confusing. It's best to avoid them unless it's a documentation/comment only change in which case there is nothing to test/verify; therefore the tested/untested distinction is not there | Humanizer, Bitcoin |
AFAICT | As Far As I Can Tell | | |
AFAIK | As Far As I Know | | Diffract |
AOA | Analysis of Alternatives | | /r/programming |
ASAP | As Soon As Possible | It is an informal way to say that who wrote it is busy at the moment and will reply as soon as he can. | Britannica |
BBL | Brown Bag Lunch | It is an informal training meeting usually performed during lunch. It is a nice way to share knowledge, train on technical, business or any kind of skills. The speaker does not have to be an expert of the topic. | brownbaglunch on Github (French) |
CCW | Comment and Criticism Welcome | | |
CLA | Contributor License Agreement | | Play Framework, Microsoft |
CMV | Change My View | | |
CoC | Code of Conduct | | |
Concept ACK | Concept ACKnowledgement | Agree with the idea and overall direction, but haven't reviewed the code changes or tested them | Bitcoin |
DRY | Don't Repeat Yourself | This is used in couple with modular programming, and emphasize on code reusability | Wikipedia |
ETA | Estimated Time of Arrival | To ask when something will be ready | /r/fsharp |
FOSS/FLOSS | Free & Open Source Software | That is both free software and open-source software where anyone is freely licensed to use, copy, study, and change the software in any way, and the source code is openly shared so that people are encouraged to voluntarily improve the design of the software | FOSS/FLOSS |
FOUC | Flash Of Unstyled Content | When a web page appears briefly with the browser's default styles prior to loading an external CSS stylesheet | md-block, Wikipedia |
FP | Functional Programming | | |
FYI | For Your Information | | ArduPilot, F#'s slack |
IANAL | I Am Not A Lawyer | Used often before talking about licensing issues | HackerNews, CUPS |
ICYMI | In Case You Missed It | | |
IIRC | If I Recall Correctly | | |
IMO | In My Opinion | | |
ITT | In This Thread | | |
KISS | Keep It Simple, Stupid | KISS is a design principle stating that most systems work fine if it is built/kept simple than making the system complex. | Wikipedia |
LGTM | Looks Good To Me | See ACK | Cardidy, Simple Icons, proposal-array-grouping |
LOC/SLOC | (Source) Lines Of Code | Above each file on GitHub you can find something like `50 lines (43 sloc)`. The difference is the empty lines. | GitHub |
MPA | Multi-Page Application | | /r/web_design |
MR | Merge Request | See PR | |
MVP | Minimum Viable Product | A prototype version of a product with the minimum required feature set | Wikipedia |
NACK/NAK | Negative ACKnowledgement | Disagree with the code changes/concept. Should be accompanied by an explanation | Bitcoin |
NIH | Not Invented Here | NIH Syndrome is a decision-making error where we tend to value our own ideas above those conceived by people outside of our group | learnosity |
NP | No Problem | No stress, it is fine | |
OOP | Object Oriented Programming | | |
OP | Original Post/Original Poster | Original Poster (who started a thread) or Original Post (the message that started it) | /r/ProgrammerHumor, StackExchange |
PR | Pull Request | Tell others about changes you've pushed to a branch in a repository | /r/vuejs |
RFC | Request For Comments | | |
RTFM | Read The F*****g Manual | Originally a way for the _gurus_ to get rid of trivial questions from newbies, now a humble way to state that a mistake or a waste of time can be avoided by reading the freaking manual first (assuming it exists). | XKCD comic, Github commits |
SCM | Source Code Management | See VCS | |
SOLID | Single responsibility, Open-closed, Liskov substitution, Interface segregation and Dependency inversion | 5 (of many) software design principles, promoted by Robert "Uncle Bob" Martin | Wikipedia |
SPA | Single-Page Application | | /r/web_design |
SRP | Single-Responsibility Principle | The single-responsibility principle is a computer-programming principle that states that every module, class or function in a computer program should have responsibility over a single part of that program's functionality, and it should encapsulate that part. wikipedia | /r/csharp/ |
TBD | To Be Defined/Done | | Software Craft Website |
tested ACK | Tested ACKnowledgment | Reviewed the code changes and have verified the functionality or bug fix | Bitcoin |
TIL | Today I Learned | TIL that TIL is Today I Learned | /r/ProgrammerTIL/ |
TYSM | Thank You So Much | | Cyber Definitions |
utACK | UnTested ACKnowledgment | Reviewed and agree with the code changes but haven't actually tested them | Bitcoin |
VCS | Version Control Software | A way to keep a track of the changes in the code so that if something goes wrong, we can make comparisons in different code versions and revert to any previous version that we want. Git, SVN or Mercurial are VCS | /r/ProgrammerHumor, softwaretestinghelp.com |
WIP | Work In Progress | Do not merge yet | GitLab's blog |
YAGNI | You Ain't Gonna Need It | | |
YMMV | Your Mileage May Vary | | |