Standard are nice, but sometimes a misguided implementation attempting to protect people completely invalidates the benefit. Read the rest of this entry »
When people first learn object oriented programming (is there any other way) they seem to want to abandon all non-member methods (such as static methods) as being anti-object-oriented. This is foolish. There are times for objects, and times for static methods. Read the rest of this entry »
Long ago I worked on a project where we needed to specify the hours that a business was going to be open, and to account for all the various difficulties around holidays and other special days. This is what we came up with and it still stands today. Read the rest of this entry »
It is well recognized that long routines with a lot of nesting can create code that is difficult to read. Even if indented correctly, it is hard over many lines to accurately match the indent amount, particularly if indented a lot. Read the rest of this entry »
In making a simple authentication service, I ran into a myriad of strange, incomprehensible requirements that someone obviously through was a good security idea, but essentially misses the mark, has all the marks of “design by committee,” and makes everything else difficult. I am recording them here, because this seems like the kind of thing I am going to need to refer back to.
This is a suggestion for how to design the JSON/REST protocol between the Angular application and the server, to handle creation of items easily and conveniently. Use a special ID value to indicate that the object does not exist on the server, and update like normal. The server detects this and creates it on demand. Read the rest of this entry »