Programming insights to Storytelling, it's all here.
Premature optimization is the root of all evil. But not optimizing your queries is a major bottle neck in your web application. During the building process, queries are written and rewritten. It would be cumbersome to write a query, index the fields needed for it, change the query for new requirement, drop the old index and create a new one. Even a simple blog like this one has more then 50 queries that have to be maintained. My strategy is simple. I don't index them right away.
Today, this blog is 5 years old. I started it secretly on April 1st, 2013. It wasn't something that I thoroughly planned. One day, I woke up with something to say, and in one sitting I wrote the first 5 posts. I had nowhere to post it. So I bought a domain name, built a quick CRUD engine, (which powers every website I build now) and posted them.
There is a story about a man who was walking around all day with his donkey. At mid day he was tired and decided to nap under a tree. Only, when he looked in his bag, he had forgotten the rope to tie the donkey to the tree. If he slept, he risked waking up to a missing donkey. A stranger passing-by saw his frustration. "Why don't you pretend to tie the donkey with an invisible rope?" the stranger said. "The donkey will not know the difference." So the man, who was too tired, followed the stranger's advice and fell asleep. To his surprise, when he woke up, the donkey was still there by the tree. He then decided to continue on his journey, but the donkey wouldn't move. Try as he may, the donkey just refused to move. So he went around the tree, untied the invisible rope, and the donkey finally followed.
I was working on a web app recently and I noticed that every time I clicked on a link, I couldn't tell if the next page was loading or not. On desktop browsers it was obvious enough with the browser queue, but not so much on mobile. So I decided to add a loading bar to let the user know.
If you count just the lines of code, CSS is probably the language I type the most in. Yet, it is also the language I share the least about on this website. So this is an attempt to fix that. I created a set of three state buttons that you can customize to your liking.
There is a moment in programming where you have to make the transition. From incompetent to competent, from worst to better, from junior to, well, less junior. Unfortunately there is no specific time when it occurs. For some it comes very early on, for others it comes very late. Some never even experience it. But the realization comes suddenly and often it is followed by shame. That moment is when you realize that you are the problem.
Only others can use the word "Smart" to describe you. They have to do it with their own will, in their own time. You can't force it. The smarter you feel, the more you want to use it. As you perform great deeds, the closer it comes to your lips. But you know you can't use it, because the more you want to say it, the less it describes you. And when you say it, you are no longer smart.
A few years ago, a meeting was held about an issue the QA team was facing. The JIRA work-flow had become too overwhelming. It was tedious to create the hundreds of sub-tasks that sometimes accompanied each feature development. The summer was approaching, so the decision was made to use the resources from the summer internship programs to snatch one of those under graduate and have him build a new system, independent of jira, to solve the problem.
Developers use the word crud to describe a very simple project. For example, Stackoverflow is just a crud, I can build it over the weekend. Facebook is just a crud, I can build it over the weekend. Even Snapchat is just a crud, I can build it over the weekend. In a sense, it is true. But as the project grows in importance, so does its complexity.
What happens when you can't work anymore? If you work at a company and your department is crippled because you were sick, it is a sign of bad management on their part.
