SCM
Source Code Management. A system where versions of a code can be versioned and history tracked, potentially across multiple engineers contributing to the same code base. Multiple flavors of SCM exist, such as Git, SVN, CVS, etc.
shadowing (Java)
In Java, shadowing a variable name means giving a method’s input parameter or local variable the same name as an instance or static/class-level variable within the same class. When this occurs, the instance or static/class level variable is shadowed by the method’s variable. Additional context is required (this. or ClassNameHere.) is needed to refer to the shadowed variable.
short (Java)
A primitive data type that stores integer values, where -32,768 <= value <= 32,767.
sub-class (Java)
A child class that extends the parent class.
sunset (code)
When code is sunset, it means it is deleted from the application’s code base, or, if it is an application, it is removed from any deployments. No longer used. See also code retirement.
First is deprecation, then follows sunset / retirement.
super (Java)
The parent class, which a child class extends it.
SVN
Subversion. A flavor of SCM where adding new commits / changes to the source code requires connectivity to wherever the potentially shared code repository is hosted. A commit / version potentially spans multiple files, which can be viewed as a single unit. I have seen this used as an interim step when migrating from CVS to git, as it contains some of the concepts of commits being multiple files, but lacks the complexity of maintaining local repository caches that comes with git.
syntax
The way to say something in a programming language (such as Python, Java, etc.) or markup language (such as HTML, JSON, MD, XML, YAML, etc.) so that what you want to convey is correctly understood. These are the strict rules of formatting those commands / data.