Programming insights to Storytelling, it's all here.
There is nothing worse than having errors you don't see. There are mistakes we make and IDEs do their best to notify us as we type. Things like syntax errors, missing semi colons, wrong data type assignment. These things happen and the compiler throws an error before we launch our application. The worse kind of errors are those that only happen in specific conditions.
When I'm in a restaurant, there is nothing that scares me more than a waiter that doesn't write down my order. Especially when we come in as a group. What if they forget? What if they charge me for something I didn't order? For that matter what if I say I didn't order anything and they just brought me food? There is no paper trail to prove otherwise. The stakes are just too high to make a mistake.
We did it, we killed popups. Most of the time I don't even notice that some websites are trying to load a popup because the browser automatically blocks them. For those that manage to circumvent the browsers rules, I have an extra popup add-on that blocks them too. We should celebrate. We won the war!
One of the biggest problem we have in programming is: It doesn't work. When you talk to a mechanic, telling him "My car doesn't work" will not help him find a solution. You may say, the car doesn't turn on, I have a flat, the fog lights are always off. Not only this tells the mechanic that your car doesn't work, but it also gives him an idea of what is not working, helping him find a solution faster.
Developers are so nice. They want to do all the work for you so you don't have to lift a finger. If you look at modern video games, you press a single button and the character runs, jumps, shoots all the enemies while in the air, tackles the big boss, saves the world and is home in time for supper. Then when you press 2 buttons together... you get the point.
Every article you read will tell you to use external files for your CSS and JavaScript. Is this rule warranted for? Are there any advantages to it? Is it considered best practice? Yes, yes, yes. There are quite some good reasons to do so, but when we leave the world of web pages and enter applications, the rule is not so strict.
You can't keep up with the new things that technology brings to the table. Everyday, there are new things that come out and despite how much you try to ignore them, the whole world is taking them seriously. When there is a new JavaScript framework that comes out, you ignore it. Rightfully so. But every job post you look at requires a minimum 3 years experience using it.
The answer to this question has ended friendships, ruined relationships and lives. OK maybe not, but I am certain for the friendship parts. Just like people call themselves PC or Mac, the mobile industry has found a way to segregate us once more. We have the iPhone people, and the Android people. There are no Windows people, sorry. (Just like there are no Linux people)
A couple times a months, I play call of duty online. It is fascinating that when you are really into the game, you forget that the people you are playing with are no where near you. They could be thousands of miles away yet, playing the game feels instantaneous.
After the hello world application, the logical step for a beginner is to learn to build a CRUD. CRUD stands for Create Read Update and Delete. It refers to an application that can perform each of those tasks the name implies. The term is also often used to say a project is too simple, it's just a CRUD app. Most applications on the web do just that and after so many years of working as a web programmer, I can assure you that it is not so simple.
