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…
Last night I presented a small introductory talk on Swift under hopefully-not-too-pretencious name of "Swift Design". I talked about what could have been the primary goals of Swift and how Apple has achieved them, doing sort of speculative reverse engineering of Swift design choices. I have uploaded the PDF and…
I'm going to classify this as Swift issue but only because it's a new language. The same problem exists in Objective-C. I've already reported it to Apple and it's on Open Radar as well. Description Consider a class implementing two protocols with clashing function declarations (name + all parameter types). Currently…