Programming insights to Storytelling, it's all here.
A year alone in a new country. A year I couldn't turn to a friend. A year I saw into darkness. A voice whispered in my ears. A voice shouted into my ears. A voice reached out and kept me going.
In April in 2016, I joined a start-up. It was my very first, I didn't know the first thing about it. What I found exciting was the idea of bootstrapping every thing from the ground up. One year later, we were standing on the podium, presenting our start-up in the Techcrunch Disrupt Battlefield. It's a success, it's an experience, it is the source of great confusion. I would like to tell you how we got there and about the unexpected things that we learned along the way. tl;dr: If you want to know about our experience, you gonna have to read. Sorry
This may not be relevant to most people but I just have to say it. I love perl.
4 years ago, I carved a little place on the web for myself. No, I did no create a new social media profile. I created a blog. This old thing in the age of videos, tweets, and one-click-create-a-website. I chose a medium that is being phased out by the mainstream, not intentionally, but because it made sense at the time. And here we are today reading it. This little place is the only place I have somewhat control of, so I will use it to tell you what has happened in the 4 year span.
I used MD5 as my password hashing back in the days (few years ago). I used it in combination with a salt and it was enough to secure the web applications I worked on at the time. Now, MD5 is broken. Not that the algorithm it used to generate one-way hashing was updated or is broken, but techniques have been developed to create the same hash using arbitrary input. Also, GPUs are powerful enough to brute force passwords. Ask Linked in about that. But the question now is, since we are all moving to more secure cryptographic methods to secure passwords, are there any uses left for good Old MD5?
Looking back at the last 10 years, I can say with great confidence that programming is creating a list of functions that perform a task. Those functions become your portfolio, toolkit, or resources. They never grow stale because you can always improve them over time.
A quick question. Do you need to know what Web Server I am running? Your answer is yes? I know, your answer is "I don't really care." Yes, I know you don't care, but I am sending you this information anyway with each web request.
Web development differs from environment to environment. If you are a .Net developer, you may have a different mindset than a person who works with PHP or ruby. In .Net, when you compile and deploy your code, an application is started and waits for web requests. It is up and spinning in a loop until a request comes. Not so in PHP. Before you make the request, there is nothing.
I'm in the category of people who are in a permanent leave of absence when it comes to college, or the more technical term a school dropout. This could be the start of a great narrative, or the source of many rejections.
Every time I look at code that obviously looks copied-and-pasted from the web, I cringe. They didn't even bother to update the variables to make sense in their own code. Why are people still using deprecated functions, SQL injection vulnerable code, or freely opening up their computer to the whole world?
