Programming insights to Storytelling, it's all here.
When designing a database abstraction layer, it is very tempting to fall into the trap of wanting to create a single module that handles MySQL, Postgres, MSSQL or any other database engine. I know I did.
When dealing with software bugs, how you ask the question determines how likely you are to get a good answer. To me programming is talking with a computer. The computer understands zeroes and ones, nothing in between. So when someone has a bug and tells a story instead of giving the relevant zeroes and ones, chances are they will never find a solution.
When you start programming and you find that you enjoy it so much, you can only wish that you had started it when you were younger. In the tech world, young has always been the new black. Young kids like Bill Gates and Zuckerberg tamed the world before they got rid of their acne. The rest of us, who didn't know what to do in our teen years, are left to suffer in our own eternal internal humiliation.
If you recorded yourself talking for ten minutes then sent it to all your team, do you think they would listen to it?
Every once in a while I am reminded that I am doing the right thing by sticking to PHP in the year 2015. If you don't know already, the majority of websites run on PHP. That is to say, PHP is a tested technology. It has a vibrant community, it is expanding, and it is very, very boring.
If SQL Injection allows a user to make a full copy of your database, Cross Site Scripting will give an attacker full control over your users. Both are equally dangerous and relatively easy to protect against. Not long ago, I wrote about the dangers of SQL Injection, today I want to focus on Cross Site Scripting.
You've been browsing reddit for a while. You think you have waited long enough, and accumulated enough courage to finally post your opinion again. When you get to the commenting section. You want to format your creative thoughts but it says, it only supports Markdown formatting. "Never heard of it!"
This should be a short post because I am just trying to document a small observation. I don't contribute to stack overflow as much as I used to. Many times I suggested code that I wouldn't normally use on a daily basis. Well documented standards thoroughly explained in hope of making everyone a better programmer. But if I was to solve the same problem, chances are I wouldn't use my own approach.
A very simple concept yet so easy to screw up. When I worked on my first website, it took me a while to understand how to deal with this favicon thing. I noticed how a lot of websites had this cool little icon when I bookmarked them but mine didn't. So I started my quest on finding how to create my own little cool icon. Today, I will save you that trouble and show you all I learned over the many years.
A few months ago I updated my PHP version. PHP 5.4 to 5.5 . I never had any problems updating PHP before. I follow its development closely and try to remove my deprecated functions long before they are officially removed. But this time I was caught off guard. It silently broke part of my website for the silliest reason.