Sign up for the newsletter by clicking this link

I’d like to once again start this week with thank you for those of you who already subscribed to the new newsletter. I’m hoping you are enjoying the new look.
The clock is ticking down until November 7 when, I’m dropping the old version for the new one. If you want to continue your subscription after November 7 click the link here I also have an updated link on the makeapppie website. Please subscribe to the new improved newsletter. I really think it will be worth it.

This week I’ll start with the tip of the week then a bit more about what is going on around here. This is somewhere between a tip and a rant this time. I want to talk about professional writing and conversation on the internet. Due to an experience in the last few weeks, I’ve come to a decision to drop a conversation under two circumstances: The writer uses profanity or the writer uses leading questions. I’d expect that the first of these is obvious. It simply is not professional to use profanity when conversing. IF you want to turn off your audience, drop an F-bomb. If you want to lose your audience in a professional setting use them every sentence. There is no reason to use such words. ZERO. I’ve heard excuses about passionate oratory and cultural norms. Both are not excuses in a professional setting.

The second thing that will make me drop an on-line conversation is a leading question. Leading questions force the person answering to answer in a certain way. Often the answer validates the quenstioner. Questions that begin with “Don’t you agree that..” or “You dont believe in..” are leading questions. They are traps. Why I drop a conversation is that the questioner has already has made up thier mind. They just want people to agree with them, not get differing opinions. If they have made up thier mind, then I have no chance to say anything instructive to the contrary: my opinion doesn’t count. To disagree is to get into a time wasting argument, and I just don’t have the time or energy to waste.

I can’t speak for you, but I suspect that most of us don;t want to waste our time in fruitless, angry conversations that sap our energy. The leading question is my red flag that things will go badly shortly. I for one am not going to play that game.

On to books…

Well the draft for Practical Autolayout got to chapter 8. That’s actually chapter 9 in the Xcode 7 version: I dropped a chapter on the assistant editor preview modes since it is very buggy in Xcode 8 and redundant as well. I hope to finish this week.

This will probably be the last Kindle edition. As I explained last week, much of the editing I have to do and the way I have to do it is because of the Kindle. While I get exposure, I’m making less in royalties on Amazon than iBooks. Unless thing go really wrong when I upload it this month, I will be doing some serious evaluation for the Xcode 9 version in 2017 if it is worth the work to make a new one. iBooks will continue without a doubt, and I’ll be continuing my policy of updated the book to the current edition.

This week’s post on makeapppie.com concludes the theme of table views with a tutorial of custom table view cells. I add four labels to the cell, and show two of them under certain conditions. I think more than a few of you who want more then the factory method table cells will find it very useful.

That’s it for this week. I’ll be talking to you next week

Keep Coding

Podcast: Play in new window | Download

Subscribe: Apple Podcasts | RSS