People often move their lips or make speech sounds as they read, which can make them project their own voice into the other person’s text

If Freud were alive and guiding 21st-century people through analysis today, he would have written “Virtually You: The Dangerous Powers of the E-Personality.” Aboujaoude’s patients’ notes (with all names changed to protect the innocent) provides a great baseline to begin discussing the strange and insidious new problems that come with living life online.

Ever think of the process communication goes through? How it’s groomed by those who benefit from it. And edited by those who want to come across a certain way?

Pay attention to the ways you reprocess communications. This includes text messages and emails.

Do you ever find yourself reading over text messages and saying them aloud? Do you notice how the voice, intention, and requests change as they become your voice?

In Virtually You: The Dangerous Aspects of the E-Personality, Aboujaoude writes:

“People often move their lips or make speech sounds as they read, which can make them project their own voice into the other person’s text. The result can be that the conversation is experienced as taking place in one’s own head, much more a soliloquy than the dialog that it really is between two separate entities.”  – Aboujaoude

Stop reading your own meanings, worries, and hangups into the text messages you receive.

“Since talking to oneself is generally considered safer than talking to someone else, the result is more indiscriminant openness and less responsible disclosures, not to mention a dissolution of boundaries between “self” and the “other.” This dissolution, we will see, does not help our universal goal of psychological independence and healthy autonomy.” – Aboujaoude

When I find myself rereading texts to search for hidden meanings I know it’s game over. Time to put down the phone. Time to go for a run. Time to lift weights. Time to do something that expends energy that I am wasting aggressively rereading text messages to get some kind of upper-hand, moral superiority, or to rewrite my views of how things “actually” went down.

Now I’d like to hear from you.

What do you do to keep yourself from revisiting old conversations, replaying them in your head, or envisioning how this all would have all turned out if you had just done this one thing differently?

I’d love to hear what works for you. Email me with your suggestions.

Moore’s Law is not about transistors it’s about the mechanics of human belief

I finished my undergraduate bachelors in Computer Science at the University of Hawaii at Manoa in 2007. Moore’s Law was drilled into our eager brains from the first day of class. It’s the kind of easy concept that is so simple no one bothers digging for deeper meaning. Let’s do it!

Here’s how Wikipedia explains it:

“Moore’s law is the observation that the number of transistors in a dense integrated circuit doubles approximately every two years. The observation is named after Gordon Moore, the co-founder of Fairchild Semiconductor and Intel, whose 1965 paper described a doubling every year in the number of components per integrated circuit, and projected this rate of growth would continue for at least another decade. In 1975, looking forward to the next decade, he revised the forecast to doubling every two years. The period is often quoted as 18 months because of Intel executive David House, who predicted that chip performance would double every 18 months (being a combination of the effect of more transistors and the transistors being faster).” – Wikipedia

Imagine how surprised I was reading Kevin Kelly’s What Technology Wants when he quotes Moore:

Moore says, “Moore’s law is really about economics.”

What does that mean? Sounds like Moore’s Law is a prophecy about the strength of the infrastructure surrounding the manufacturing of transistors.

Kelly goes on to say,

Carver Mead made it clearer yet: Moore’s law, he says, “is really about people’s belief system, it’s not a law of physics, it’s about human belief, and when people believe in something, they’ll put energy behind it to make it come to pass.”

Mead defines Moore’s Law further:

“After [it] happened long enough, people begin to talk about it in retrospect, and in retrospect it’s really a curve that goes through some points and so it looks like a physical law and people talk about it that way. But actually if you’re living it, which I am, then it doesn’t feel like a physical law. It’s really a thing about human activity, it’s about vision, it’s about what you’re allowed to believe.”

What concepts do you leave on the table? What beliefs have you actually tested? Hindsight’s 20/20. What predictions can you make to alter (and guide) the beliefs of your customers?

Hawaii iOS Developer Meetup – Session 7

https://youtu.be/sXsmHWvQGKM

We programmed Tetris yesterday at the meetup. I was surprised at how long it took to code up Tetris before the meetup. I used a single dimensional array to store the game piece and the game board. Bad move. Translating the index of an array to a differently sized array was a nightmare. An hour before the meetup I recoded Tetris with multidimensional arrays — Instant coordinate system.

There’s a technique Hemingway used when he wrote novels and short stories. He’d write until he caught a good tailwind, then, just as abruptly as he started, he would stop in the middle of writing.

Halfway through writing, his brain wouldn’t have the chance to fully express what it wanted to — no closure. This meant that his brain would continue to sift and sort his thoughts until the next day when he would dive into writing with gusto to finish what he started writing the day before.

I suspected the same effect exists in coding.

Stopping in the middle of implementing a function might not be the best place to stop. So I stopped when the game functioned well enough but contained a visual bug.

The bug gave us an opportunity to talk about Swift on a deeper level without being too invested in setting up a new project to have something specific to talk about.

If you’re interested in compiling, testing the code yourself, and checking out the bug, here’s a link to the repo.

This is a cool bug. It’s giving me ideas about other games that would benefit from this kind of visual oddity. Kind of like glitch art. The piece is placed on the screen then “melts” down the page. It’s kind of cool. How would you fix it?

We’ll be tackling piece rotation and scoring next week Thursday at the Hawaii iOS Developer Meetup. Please RSVP if you’re interested in attending.

Great leaders don’t innovate the product, they innovate the factory

My Mac Book Air (mid-2011) has been running slow during the meetup. It’s fine for light coding but it drags when I run a bunch of tests, swarm program on ScreenHero, or screenrecord during a presentation.

My product is suffering because I can’t upgrade the factory.

I wanted to upgrade the RAM from 4 gigs to 16 gigs. So I went to the Apple Store.

The Apple Store doesn’t do RAM upgrades on the model I have and they suggested that I contact Mac Made Easy, a third party apple store and repair shop.

“Hi, I have a mid 2011 Mac Book Air and I’d like to update the RAM.”

The tech on the phone said, “Hold on, did you say mid-2011? We could do it for you. But it’s going to be very expensive. They’ve soldered the RAM to the motherboard.

Not being able to update the RAM on my computer is infuriating. Especially because I love everything else about the computer.

My product is my code. My product is sharing information at the meetup. My product is connecting people through code. My product under-performs because my Mac Book Air can’t take on more RAM without undergoing a very expensive procedure.

In other words, the product suffers if you can’t innovate the factory.

I haven’t determined what I’m going to do from here. But I wanted to post a quote about the misguided goal of innovating the product when you should really be innovating the factory.

If you want to get the best out of individuals, make sure to treat them as members of a team and not as solo performers

“Knowledge workers, unlike manual workers in manufacturing, own the means of production: they carry that knowledge in their heads and can therefore take it with them.” – Peter Drucker

This quote may give white-knighting over-workers the feeling that they are indispensable.

Be wary of this quote. It’s not as simple as it seems.

In Under New Management, Burkus says,

“The fuel running most organizations today isn’t brute labor – it’s mental energy.” – David Burkus

All that energy does nothing if you don’t have the support you need to see your ideas through to completion, testing, and implementation! If you haven’t earned the support of your team you are the weakest link… Goodbye!

“A chain is only as strong as its weakest link.” – Unknown

The point of working on a team is to share your knowledge, have it pile up, build up, and perform better than anything a single individual with the same knowledge would ever be able to do alone.

“If you want to get the best out of individuals, make sure to treat them as members of a team and not as solo performers.” – David Burkus

How do you treat your team? Are you a lone wolf? It can be appealing to go it alone, pulling yourself up by your own bootstraps and feeling the power of accomplishment.

But with no Posse to rely on in times of need you might as well be lost in a desert with no water, no food, and only mirages of your perceived glory. And that won’t cut it. Build your posse. Focus on the team. And make all your decisions consider the greater good and the team’s efforts.

Hawaii iOS Developer Meetup – Session 6

https://www.youtube.com/watch?v=mlNRd8ufZho

Killing it. Finding that the more of a lead I take, the more energy, interest and enthusiasm it creates. Finding that I need to slow down in my delivery. Finding my moderation style is a bit short. Working on it.

Meetup page is shaping up and looking novel:

screen-shot-2017-01-05-at-11-28-22-pm

Set up is getting cleaner:

screen-shot-2017-01-06-at-12-22-08-am

Looking forward to the next meetup where I will live-code Tetris in Swift 3 for the command line. Sign up if you’d like to attend in person.