Re: Looking at self = [super init].
Re: Looking at self = [super init].
- Subject: Re: Looking at self = [super init].
- From: Michael David Crawford <email@hidden>
- Date: Tue, 02 Jun 2015 18:07:19 -0700
While there were numerous reasons for my protest resignation, the
reason I walked out - no notice given - was that I was the only one in
the company who was aware that there even was such a thing as a C++
Smart Pointer.
I knew something was up when I was told to stop referring to the
computer programmers as "the engineers". In Canada, it's a civil
offense to call yourself an engineer unless you're the Canadian
equivalent of an American Professional Engineer. At that company,
"the engineers" was taken to mean the industrial control system
engineers - those who worked with electrical and mechanical gadgets.
All the software was written by "computer programmers" for no reason I
can fathom.
In mechanical drawing - more commonly known as "drafting" - there is
always a very specific convention for documentation blocks in your
drawing. There will be the company name, maybe a logo, the
draftsman's name, revision numbers, a title, date and so on. I expect
their comment fetish evolved from that.
What horrified me was that they were completely unaware that their
product was likely to drop a pickup truck on top of an assembly plant
worker. While the overall architecture had all manner of
fault-tolerance engineered in, that fault-tolerance depended on
correct C++ code.
Michael David Crawford, Consulting Software Engineer
email@hidden
http://www.warplife.com/mdc/
Available for Software Development in the Portland, Oregon Metropolitan
Area.
On Tue, Jun 2, 2015 at 5:38 PM, Graham Cox <email@hidden> wrote:
>
>> On 3 Jun 2015, at 10:19 am, Michael David Crawford <email@hidden> wrote:
>>
>> If their coding conventions are
>> the sort that are likely to lead to correct code
>
>
> The reason for coding style guidelines is a) correctness b) maintainability. If it's just a fetish that the chief developer has and he can't back it up with reasoned argument then that's suspect.
>
> Having been handed several uncommented and undocumented messes and left to sort it out a couple of times in my career I'm very sensitive to the needs of developers coming to a codebase cold. I try to write code in such a way that I imagine a developer who's never seen it before could get up to speed in a relatively short time, even if 99% of the time that developer is me, several years removed. There's nothing worse than wasting hours wondering "what the hell was I thinking?" instead of just reading a comment that explains what I was thinking.
>
> --Graham
>
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden