You are here |
nomotherships.com | ||
| | | |
regulargeek.com
|
|
| | | | I have talked abouthuman filtersandmy plan for digital curation. These items are the fruits of those ideas, the items I deemed worthy from my daily reading. These items are a combination of tech business news, development news and programming tools and techniques. You will note that some of the formatting has changed, and that is... | |
| | | |
cutebouncingbunnies.wordpress.com
|
|
| | | | Programs need human written comments. Neither literate programming, nor type systems suffice. Conditions that demand comments: Why? - Explanations of why something is how it is. "Requiring the caller to provide a buffer prevents multiple allocations when calling in a loop". Clever - Explanations of code that is not obvious on a casual read by... | |
| | | |
icoderman.wordpress.com
|
|
| | | | Don't resign just because you are angry with your boss. Give an advanced notice - verbally and in writing. Do not accept a counter-offer. Do not resign until you've found another job. Do not give advices to your boss on the way out. Don't post negative blogs about the company you quit. © Yakov Fain... | |
| | | |
enterprisecraftsmanship.com
|
|
| | Hard coding is often considered an anti-pattern. Having values that can change over time hard-coded in the source code requires recompilation every time these values actually change. While this statement is true, I think that hard coding should be the default choice when developing an application. Hard coding vs configuration file When you work on a project or feature, there always are some magic numbers or strings that potentially can change in future. |