Programming insights to Storytelling, it's all here.
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.
As programmers, we work in a field where it is hard to claim to be an expert. Technology constantly changes, and readjustment is a necessity. I read an interesting experiment on nautilus just the other day, here is how it goes.
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.
DRM is an important word in the world of technology. It is the control of content long after it has been distributed. Many files are distributed in DRM formats. What this means is that they can only read by applications controlled by the content proprietor. This doesn't even work in theory because the computer is designed to read everything. What these application do is tell the computer not to show the user what it just read.
I'm glad we stopped hearing people say "the computer is so stupid that it can't even <insert something simple here>". I used to have a teacher in college that would start every class with one of those remarks he would think is clever.
Imagine working for 12 hours straight, without talking any break. You build modules, tools, and your to do list keeps getting shorter and shorter. You don't want to stop because you are in the zone. Your mojo is up the roof. But suddenly you get this Error:
