I've been thinking on HTTP API versioning lately. Troy Hunt's Your API versioning is wrong... is the 1st hit when googling "HTTP API versioning" but I think it's limited in its scope to dealing just with GET verb in public non-authenticated APIs. This isn't explicit in the article but Troy…
If I could program myself: I would make my eating habits strictly fit my actual needs, both calorie-wise and taste-wise. Unfortunately, my eating habits are overriden with other superficially-non-functional impulses (e.g. if I'm anxious/tired/sleepy I'll eat more and without much thought re what I eat, trying to…
TL;DR: I tried to build a company in order to build a culture, failed to do it beyond giving me a very nice and easy-going living; then lucked out and found a compatible culture where my contributions are greatly amplified by contributions that other make; then won the Salesforce's…
For when nothing else will to place a warning, in your code, to your future self or your fellow developers paste this: // // NOTE NOTE NOTE NOTE NOTE NOTE NOTE NOTE NOTE // NOTE NOTE NOTE NOTE NOTE NOTE NOTE NOTE // NOTE NOTE NOTE NOTE NOTE NOTE NOTE NOTE NOTE // NOTE NOTE…
In the wild I sometimes see the following as implementation of NSCopying:copyWithZone: -(id)copyWithZone:(NSZone*)zone { MYClass* copy = [MYClass new]; copy.property1 = self.property1; ... copy.propertyN = self.propertyN; return copy; } This is wrong as accessing the copy and the original objects through . during the copying process itself must…
I just figured out what bothers me the most (among several other things) about Objective-C: in its current incarnation it is being to too clever with names. It heavily breaks the principle of least surprise (in this case being: "name things as I wrote them, don't make stuff up") I…