Programming insights to Storytelling, it's all here.
My little niece will do whatever it takes to stay up as late as possible and wake up on the first light of day. Her reason? She doesn't want to miss a second of the day. She wants to be there when everything happens. At night, her eyes will be closing but when asked if she is sleepy, her answer is always, No! Followed by a sudden burst of energy.
Even if you know the rule, you will still be frustrated. The first hundred hours are full of surprises, full of confusion, full of frustration. No matter how many times I start learning new things, I have a hard time dealing with this frustration. But that's ok.
In a programming environment like PHP, there are chances you are dealing with strings all over your code. Whether it is to throw an error, or simply notify your users of something that happened, you have to send text messages as strings.
Programming, or coding, is marketed as the skill you need to build the next big thing. Although it can be true, we can say the same about fishing. By learning how to catch fish, you get to put food on the table. You can also become the dedicated fisherman company in a small town, raking in millions of dollars.
Today, anything that is not instant is not worth it. The title of the book is "Don't make me think!" If you make me think than you are doing it wrong. Not to say that intuitive design is bad, but if done wrong it can be a direct contributor to the microwave mentality.
As programmers, we tend to neglect the side of the business where there are people involved. You see great programmers that won't dare touch frontend code even with a yard stick. I worked as a frontend developer and I am still afraid of the user interface.
I rarely go inside a bank anymore. I limit all my transactions directly to the ATM. On my last visit, I spent at least five minutes looking at their new machines. At Bank Of America, there were only a couple human tellers. On the ATM you pick up the phone piece and you are connected in real time with a teller, possibly on the other side of the world.
There are things in the programming world that we spend too much time fighting for. Each programmer does things a certain way. Maybe they got their style from a combination of books from an author they admire, maybe they just like a particular style of programming. No matter what it is, they defend their way religiously, firmly believing that it is the right way.