Thread by @jpluimers

@Felienne @neverworktheory My pet-peeve here is two fold:

1. if you want/need to mix technology and semantics in names, start with the most meaningful semantics and end with the least meaningful technology

This applies to any development environment, taking Delphi as that's what I taught most:

1/

@Felienne @neverworktheory In a Delphi GUI application you always have:
- a main form that is a class combined with a variable that both need to go into the same unit file (which in more generic terms is a module) with extensions .dfm and .pas
- a main program file with extension .dpr

Names then are:

2/

@Felienne @neverworktheory * CalculatorProgram.dpr (or just Calculator.dpr)
* CalculatorMainFormUnit.pas
* CalculatorMainFormUnit.dfm
* TCalculatorMainForm (the Delphi class for the main form)
* CalculatorMainForm (the Delphi variable for the main form)

The last two are both in the .dfm and .pas file

3/

@Felienne @neverworktheory 2. Avoid abbreviations whenever possible as abbreviations are always context sensitive. Since in an application you can have both technical context and semantic context it is easily to confuse both

4/

@Felienne @neverworktheory This goes against how most Delphi programmers are being taught with names like these:

* Calc.dpr
* uFrmMain.pas
* uFrmMain.dfm
* TMainFrm
* MainFrm

or if you are even less lucky saving with IDE auto-numbering:

* Calc.dpr
* Unit1729.pas
* Unit1729.dfm
* TForm1729
* Form1729

5/

@Felienne @neverworktheory The 1729 is a tribute to @ionicasmeets

Welcome back from the long Heidelberg-Leiden train trip Ionica!

6/6