19,387 reputation
94673
bio website ericlippert.com
location Seattle, WA
age 41
visits member for 4 years, 1 month
seen Nov 18 at 0:15

Eric Lippert develops C# analyzers at Coverity. During his sixteen years at Microsoft he was a developer of the Visual Basic, VBScript, JScript and C# compilers and a member of the C# language design committee; he is now a C# MVP. He is on Twitter at "@ericlippert" and writes a blog about programming language design and other fabulous adventures in coding at http://ericlippert.com.


Sep
2
answered The Definition of “Strong Type Systems”
Aug
23
answered Why does void in C mean not void?
Jun
6
answered Is this method pure?
Jun
3
answered Overriding GetHashCode in a mutable struct - What NOT to do?
May
11
answered Can recursion be done in parallel? Would that make sense?
May
9
answered Why would Square inheriting from Rectangle be problematic if we override the SetWidth and SetHeight methods?
May
2
answered If null is bad, why do modern languages implement it?
Apr
28
answered How did programmers implement Linked list ideas before the object oriented paradigm?
Apr
24
answered Learning to investigate bugs
Apr
2
answered Zero behavior objects in OOP - my design dilemma
Mar
24
answered Should I expose a “computed” value as a property or a method?
Feb
13
answered What is the benefit of having the assignment operator return a value?
Jan
14
answered How has an increase in the complexity of systems affected successive generations of programmers?
Jan
3
answered Adding a new method to a class library for its new version and exposing a version option the users can select
Dec
26
answered Which way to terminate reading loop is the preferred approach?
Dec
17
answered Why do dynamic languages make it more difficult to maintain large codebases?
Nov
29
answered What if I will not use Software Design Patterns?
Sep
27
answered Is it poor practice to name a property/member the same as the declaring type in C#?
Aug
29
answered Are too many if-else statements for validation bad?
Mar
23
answered Stroustrup and the C++ complexity admission