If you are a software engineer, you’ve probably been in a job interview where you were asked, “Have you ever used [Insert some awesome technology you may have heard of but certainly never used professionally here]?” You hear the question, and inside you’re basically like “Uh ohhh.” Your mind races for a reasonable response that won’t kill your chances. The best you can come up with is some sheepish variation on these:
Vidya is proud to be working with Neustar, a leading telecommunications and cloud platform company. You may not realize it, but every phone call, fax, and computer connection in North America depends on Neustar. Why? In 1998, Neustar saved the 10-digit telephone number system from becoming a 14-digit system with a solution mandated by the FCC, so every telephone company in North America has a physical interface into Neustar’s directory system.
Please take a look at my latest column for Government Computing News where I discuss the strengths and weaknesses of relational databases and describe circumstances where document databases or graph databases may actually be a better fit. Just to give you an idea, here is the unedited introduction. One of my current projects is to review an application built by a contractor for a major federal government agency. The code relies heavily on queries and stored procedures against a relational database management system (RDBMS).
While in the middle of his Jedi training with Master Yoda, Luke Skywalker discovers his ship has sunk into the Dagobah swamp. Ever the whiner, Luke complains about how difficult it will be to salvage the ship. That’s when an exasperated Yoda bestows some unforgettable wisdom. The iconic line from this scene in The Empire Strikes Back is “Do. Or do not. There is no try.” That’s an awesome line worthy of every t-shirt and Big Bang Theory reference.