Group items tagged

the minimum documentation for a piece of code is the list and description of: inputs - names, types and purposes outputs -  types being the most important piece algorithm descriptions

The old line is that the job is not done until the paperwork is done. For programming documentation is the paperwork.

My axim is write documentation ONLY when it hurts to not have it

Interesting comment about IntelliSense encouraging a bottom-up approach. I think that is true if you start with programming and not with design. What I mean by that is that some people create their design in code rather than working out the full design before starting to code. I think that if you create a design using a top down approach it takes longer to get to the building blocks. that is frustrating to many, especially students, but in the long run results in a much better design. With a complete design in place one does know what the little blocks of code will be at least from the standpoint of names and interfaces. Creating those little blocks early on in the programming is fine as long as the design is complete

arrays of reference types are covariant in their element type, but not safely

where did that exception come from? It came from the runtime, which was in a unique position to know what the real type of the array object was, and the real type of the element. It needed to determine if the assignment was allowable and throw if not. Now if you think about this for a minute, you can see that it’s going to have to perform that check for every assignment to an array element

By default, SqlClient attempts to make the connection using the following protocol order[1]: Shared Memory TCP/IP Named Pipes