When you think about the black market, I’m sure the majority of you will think of prohibition days.  When alcohol was made illegal, it did two things: It made the bad guys more money, and it put the average joe in a dangerous position while trying to acquire it.  Bring in the 21^stcentury. Sure, there still is a black market… but come on, who is afraid of mobsters anymore? Today, we have a gaming black market. It has been around for years, but will it survive? With more and more games moving towards auction houses, could game companies “tame” the gaming black market?

In the old days of gaming on the internet, we spent most of our online time playing hearts, spades… whatever we could do while connected to the internet. As the years went by, better and better games came about. Then, suddenly, interactive multiplayer games came into the picture. These interactive games, mainly MMORPGS, allowed for characters to pick up and keep randomly generated objects known as “loot”. This evolution of gaming created the black market.

In the eyes of the software companies, the game is only being leased/rented by the end user. You don’t actually have any rights to the game. This is where the market becomes black.  The software companies don’t want you making money of “virtual” goods that are housed on the software or servers of the game you are playing on.  The software companies, at this point, started to get smarter.

Where there is a demand…

Unlike Java, Python does not have a string contains method.  Instead, use the in operator or the find method.  The in operator finds treats the string as a word list whereas the find method looks for substrings.  In the example shown below, 'is' is a substring of this but not a word by itself.  Therefore, find recoginizes 'is' in this while the in operator does not.

s = "This be a string"
if s.find("is") == -1:
    print "No 'is' here!"
else:
    print "Found 'is' in the string."
    
if "is" in s:
    print "No 'is' here!"
else:
    print "Found 'is' in the string."

#prints out the following:
Found 'is' in the string
No 'is' here!

Google is one of the most popular websites in the entire world that gets millions of views each day. Therefore, it should come as no surprise that it needs a strong and reliable programming language that it can rely on to run its searches and many of the apps that Google has created. Because of this, Google uses Python to ensure that every time a user uses one of their products, it will work smoothly and flawlessly. That being said, Google uses Python in a variety of different ways, outlined below.

Code.Google.Com
Since its creation, Google has always used Python as part of its core for programming language. This can still be seen today considering the strong relationship the two have with one another. Google supports and sponsors various Python events, and Python works to better itself so that Google remains on top of cutting edge material. One way that they do this is by working with code.google.com. This is the place where Google developers go to code, learn to code and test programs. And with it being built on Python, users can experience exactly what it is that they should expect once they start using the real site.

Google AdWords
Google AdWords is a great way for people to get their websites out there, through the use of advertising. Each time a person types in a certain string of keywords, or if they have history in their cookies, then they’ll come across these AdWords. The way that these AdWords are broadcasted to online web surfers is built on the foundation from Python. Python also helps clients access their AdWord accounts, so that they can tailor where they want their advertisements to go.

Beets
If you have loads of music, but some of it is uncategorized or sitting in a music player without a name or title, Beets is for you. This Google project uses Python and a music database to help arrange and organize music. The best part about Beets is that even if it doesn’t run exactly the way that you want, you can use a bit of Python knowledge to tailor it to be more specific to your desires.

Android-Scripting
Not only does Google run off Python, but Android also has its own value for the language. Whether you are someone who is just creating your own app for your phone or if you are someone who is looking to create the next app that gets downloaded multiple millions of times, you can use Python and Android-Scripting to create an app that does exactly what you want it to do.

YouTube
YouTube one just started as a video viewer on its own, but is now a billion-dollar company that is owned by Google. YouTube uses Python to let users view and upload video, share links, embed video and much more. Much like Google itself, YouTube relies heavily on Python to run seamlessly for the amount of traffic it gets daily.

Python is not your average coding language. Instead, it is a valuable and integral part of some of the biggest websites in the world, one of which is Google. And the resources listed here are just a fraction of what Google uses Python for in total.

Related:

What Are The 10 Most Famous Software Programs Written in Python?

The Future of Java and Python

Ranking Programming Languages: Which are Gaining Popularity?

Top 10 Software Skills for 2014 and Beyond

Working With Strings In Python

Working With Lists In Python

Conditional Programming In Python

Millions of people experienced the frustration and failures of the Obamacare website when it first launched. Because the code for the back end is not open source, the exact technicalities of the initial failings are tricky to determine. Many curious programmers and web designers have had time to examine the open source coding on the front end, however, leading to reasonable conclusions about the nature of the overall difficulties.

Lack of End to End Collaboration
The website was developed with multiple contractors for the front-end and back-end functions. The site also needed to be integrated with insurance companies, IRS servers, Homeland Security servers, and the Department of Veterans Affairs, all of whom had their own legacy systems. The large number of parties involved and the complex nature of the various components naturally complicated the testing and integration of each portion of the project.

The errors displayed, and occasionally the lack thereof, indicated an absence of coordination between the parties developing the separate components. A failed sign up attempt, for instance, often resulted in a page that displayed the header but had no content or failure message. A look at end user requests revealed that the database was unavailable. Clearly, the coding for the front end did not include errors for failures on the back end.

Bloat and the Abundance of Minor Issues
Obviously, numerous bugs were also an issue. The system required users to create passwords that included numbers, for example, but failed to disclose that on the form and in subsequent failure messages, leaving users baffled. In another issue, one of the pages intended to ask users to please wait or call instead, but the message and the phone information were accidentally commented out in the code.

While the front-end design has been cleared of blame for the most serious failures, bloat in the code did contribute to the early difficulties users experienced. The site design was heavy with Javascript and CSS files, and it was peppered with small coding errors that became particularly troublesome when users faced bottlenecks in traffic. Frequent typos throughout the code proved to be an additional embarrassment and were another indication of a troubled development process.

NoSQL Database
The NoSQL database is intended to allow for scalability and flexibility in the architecture of projects that will use it. This made NoSQL a logical choice for the health insurance exchange website. The newness of the technology, however, means personnel with expertise can be elusive. Database-related missteps were more likely the result of a lack of experienced administrators than with the technology itself. The choice of the NoSQL database was thus another complication in the development, but did not itself cause the failures.

Another factor of consequence is that the website was built with both agile and waterfall methodology elements. With agile methods for the front end and the waterfall methodology for the back end, streamlining was naturally going to suffer further difficulties. The disparate contractors, varied methods of software development, and an unrealistically short project time line all contributed to the coding failures of the website.