Standard

Naming Guidelines for Professional Programmers. / Hilton, Peter; Hermans, Felienne.

2017. Abstract from PPIG 2017: 28th Annual Workshop , Delft, Netherlands.

Research output: Contribution to conferenceAbstractScientific

Harvard

Hilton, P & Hermans, F 2017, 'Naming Guidelines for Professional Programmers' PPIG 2017: 28th Annual Workshop , Delft, Netherlands, 1/07/17 - 3/07/17, .

APA

Hilton, P., & Hermans, F. (2017). Naming Guidelines for Professional Programmers. Abstract from PPIG 2017: 28th Annual Workshop , Delft, Netherlands.

Vancouver

Hilton P, Hermans F. Naming Guidelines for Professional Programmers. 2017. Abstract from PPIG 2017: 28th Annual Workshop , Delft, Netherlands.

Author

Hilton, Peter ; Hermans, Felienne. / Naming Guidelines for Professional Programmers. Abstract from PPIG 2017: 28th Annual Workshop , Delft, Netherlands.1 p.

BibTeX

@conference{840e02626e604f288a779b7efa84b56e,
title = "Naming Guidelines for Professional Programmers",
abstract = "Programmers acknowledge the difficulty of naming things, whatever their experience level and wherever they work, but relatively few use explicit naming guidelines. Various authors have published different kinds of identifier naming guidelines, but these guidelines do little to make naming easier, in practice. Meanwhile, professional programmers follow diverse conventions and disagree about key aspects of naming, such as acceptable name lengths. Although few teams write their own coding standards, let alone naming guidelines, many teams use code review and pair programming to maintain code quality. We believe that these teams could use third-party naming guidelines to inform these reviews, and improve their coding style. This paper examines various sources of naming guidelines, in the context of the first author’s twenty years’ experience as a professional programmer. This paper then presents a consolidated set of naming guidelines that professional programmers can apply to the code they write.",
author = "Peter Hilton and Felienne Hermans",
year = "2017",
language = "English",
note = "PPIG 2017: 28th Annual Workshop ; Conference date: 01-07-2017 Through 03-07-2017",

}

RIS

TY - CONF

T1 - Naming Guidelines for Professional Programmers

AU - Hilton, Peter

AU - Hermans, Felienne

PY - 2017

Y1 - 2017

N2 - Programmers acknowledge the difficulty of naming things, whatever their experience level and wherever they work, but relatively few use explicit naming guidelines. Various authors have published different kinds of identifier naming guidelines, but these guidelines do little to make naming easier, in practice. Meanwhile, professional programmers follow diverse conventions and disagree about key aspects of naming, such as acceptable name lengths. Although few teams write their own coding standards, let alone naming guidelines, many teams use code review and pair programming to maintain code quality. We believe that these teams could use third-party naming guidelines to inform these reviews, and improve their coding style. This paper examines various sources of naming guidelines, in the context of the first author’s twenty years’ experience as a professional programmer. This paper then presents a consolidated set of naming guidelines that professional programmers can apply to the code they write.

AB - Programmers acknowledge the difficulty of naming things, whatever their experience level and wherever they work, but relatively few use explicit naming guidelines. Various authors have published different kinds of identifier naming guidelines, but these guidelines do little to make naming easier, in practice. Meanwhile, professional programmers follow diverse conventions and disagree about key aspects of naming, such as acceptable name lengths. Although few teams write their own coding standards, let alone naming guidelines, many teams use code review and pair programming to maintain code quality. We believe that these teams could use third-party naming guidelines to inform these reviews, and improve their coding style. This paper examines various sources of naming guidelines, in the context of the first author’s twenty years’ experience as a professional programmer. This paper then presents a consolidated set of naming guidelines that professional programmers can apply to the code they write.

M3 - Abstract

ER -

ID: 67237290