Python is an incredibly powerful and useful computer programming language that many of the biggest websites in the world rely on for their foundation. Python provides reliable results that are functional and involve a variety of dynamic scripted and non-scripted contexts. And because it is free and open source, it has remained a popular choice for a variety of different developers who are looking to build new sites on one of the most reliable languages available. Here is a look at 10 of the most famous software programs that are written in Python and what they do.

YouTube
If you love watching hours of homemade and professional quality video clips on YouTube, you can thank Python for giving you that option. The foundation for Python helped YouTube integrate streaming videos into their pages, as well as the ability to like videos and embed certain information. YouTube is one of the most popular sites on the Internet, and it runs off of one of the most powerful languages in Python.

DropBox
What started as a powerful app, DropBox is now used by a variety of individuals, businesses, companies, organizations and more. This program lets you save files to a cloud-based service, that you can then access from anywhere in the world. With Python at the root of DropBox, there is no longer a need for USB sticks or blank CDs, since you can now save and share everything with your cloud-based account.

Google
It takes a lot of power to be able to handle the most popular search engine in the entire world. That is why Google uses Python for its mainframe foundation, as well as in addition to various apps that it runs in conjunction with the main site. The ease that Google provides for finding certain information, would be impossible without Python at the core.

Quora
Got a question? Ask it on Quora. This site compiles a list of questions and answers that come from a community of individuals. Those questions are then organized by various members of the community, which puts the most relevant information at the top. The creators of Quora, who happened to be former Facebook employees, decided to use Python to help them create the world’s best Magic 8 ball in Quora.

Instagram
If you love taking photos of your food or a new outfit and posting it online for all of your friends to see, you can thank Python for that ability. Granted, Instagram has both a very powerful app and a website, but the latter runs on Python language. The system allows for users to browse, find and post pictures that they like on the site.

BitTorrent
BitTorrent has evolved quite a bit in recent years, but its foundation and earlier years were built on Python. When it comes to one of the largest databases of knowledge, media and content, BitTorrent is the way to go. But you wouldn’t be able to get any of those lectures or other legal stuff that you are downloading from BitTorrent, if it wasn’t for Python.

Spotify
Spotify changed the music game when it allowed you to listen to ad-free music of your choice. This wasn’t a program where you got to select a playlist, but rather full songs that you love, on repeat as many times as you can imagine, if you so desire. But whether you are rocking out to the latest K-Pop song from Psy or a classic jazz tune, you are doing so because Spotify was built on Python.

Reddit
Reddit is one of the biggest open communities on the web. You have a question, want to talk about something in specific, or find tons of information regarding a particular topic, you can just look on Reddit. The site relies on Python to help them store user names, categorize subreddits, upload links to GIFs and, of course, award gold to valued posters.

Yahoo Maps
Much like Google, Yahoo also uses Python for a variety of different resources. Most valued may be Yahoo Maps. The API and programming behind the maps program, which is built with Python, allows for users to find locations, get directions and even find reviews about local places.

Hipmunk
If you love to travel, you have likely come across Hipmunk. And while the site lets you save money on booking your itinerary through Hipmunk, it is Python that keeps everything organized. Python also helps sort the best discounts and rates, so you can get the best packages available.

Python is an incredibly powerful tool for web development. More and more sites rely on it, including 10 of the most powerful sites in the world that are listed here.

Related:

Current Active List of Organizations that use Python 

Working With Lists In Python

A business rule is the basic unit of rule processing in a Business Rule Management System (BRMS) and, as such, requires a fundamental understanding. Rules consist of a set of actions and a set of conditions whereby actions are the consequences of each condition statement being satisfied or true. With rare exception, conditions test the property values of objects taken from an object model which itself is gleaned from a Data Dictionary and UML diagrams. See my article on Data Dictionaries for a better understanding on this subject matter.

A simple rule takes the form:

if condition(s)

then actions.

An alternative form includes an else statement where alternate actions are executed in the event that the conditions in the if statement are not satisfied:

if condition(s)

then actions

else alternate_actions

It is not considered a best prectice to write rules via nested if-then-else statements as they tend to be difficult to understand, hard to maintain and even harder to extend as the depth of these statements increases; in other words, adding if statements within a then clause makes it especially hard to determine which if statement was executed when looking at a bucket of rules. Moreoever, how can we determine whether the if or the else statement was satisfied without having to read the rule itself. Rules such as these are often organized into simple rule statements and provided with a name so that when reviewing rule execution logs one can determine which rule fired and not worry about whether the if or else statement was satisfied. Another limitation of this type of rule processing is that it does not take full advantage of rule inferencing and may have a negative performance impact on the Rete engine execution. Take a class with HSG and find out why.

Rule Conditions

Anonymous reprint from Quora (career advice)

Occasionally we come across a unique profound perspective that makes one stop and really listen. The following advice is one such as this.

1. Small actions compound: Reputation, career trajectory, and how others perceive you in the workplace can come down to a handful of things/moments that seem inconsequential/small at the time but compound. Random Thought: Redwood trees come from small seeds and time. With every action you're planting small seeds and these seeds can grow into something bigger (sometimes unimaginably bigger) over time. Don't let small basic mistakes sabotage your reputation because it only takes a few small snafus for people to lose confidence/trust in your ability to do more important tasks. Trust is a fragile thing and the sooner people can trust you the faster they'll give you more responsibility. Some Examples: Being on time (always) or early (better); spending an extra 10-15 minutes reviewing your work and catching basic mistakes before your boss does; structuring your work so it's easy for others to understand and leverage (good structure/footnotes/formatting); taking on unpleasant schleps/tasks (volunteer for them; don't complain; do it even when there's no apparent benefit to you)  


2. Rising tide lifts all boats: Fact: You don't become CEO of a multi-billion dollar public company in your 30s based purely on ability/talent. Your career is a boat and it is at the mercy of tides. No matter how talented you are it's a lot harder to break out in a sluggish situation/hierarchy/economy than a go-go environment. Even if you're a superstar at Sluggish Co., your upside trajectory (more often than not) is fractional to what an average/below average employee achieves at Rocket Ship Co. There's a reason Eric Schmidt told Sheryl Sandberg to "Get on a Rocket Ship". I had colleagues accelerate their careers/income/title/responsibility simply because business demand was nose bleed high (go go economy) and they were at the right place at the right time to ride the wave. Contrast that to the 2008 bust where earnings/promotions/careers have been clamped down and people are thankful for having jobs let alone moving up. Yes talent still matters but I think people generally overweight individual talent and underweight economics when evaluating/explaining their career successes. Sheryl Sandberg Quote: When companies are growing quickly and they are having a lot of impact, careers take care of themselves. And when companies aren’t growing quickly or their missions don’t matter as much, that’s when stagnation and politics come in. If you’re offered a seat on a rocket ship, don’t ask what seat. Just get on.


3. Seek opportunities where the outcome is success or failure. Nothing in between! You don't become a star doing your job. You become a star making things happen. I was once told early in my career that you learn the most in 1) rapidly growing organizations or 2) failing organizations.  I've been in both kinds of situations and wholeheartedly agree. Repeat. Get on a rocket ship. It'll either blow up or put you in orbit. Either way you'll learn a ton in a short amount of time. Put another way; seek jobs where you can get 5-10 years of work experience in 1-2 years.


4. Career Tracks & Meritocracies don't exist: Your career is not a linear, clearly defined trajectory.  It will be messy and will move more like a step function.


5. You will probably have champions and detractors on day 1: One interesting byproduct of the recruiting & hiring process of most organizations is it can create champions & detractors before you even start the job. Some folks might not like how you were brought into the organization (they might have even protested your hiring) and gun for you at every turn while others will give you the benefit of the doubt (even when you don't deserve one) because they stuck their neck out to hire you. We're all susceptible to these biases and few people truly evaluate/treat folks on a blank slate.


6. You'll only be known for a few things. Make those labels count: People rely on labels as quick filters. Keep this in mind when you pick an industry/company/job role/school because it can serve as an anchor or elevator in the future. It's unfortunate but that's the way it is. You should always be aware of what your "labels" are.


7. Nurture & protect your network and your network will nurture & protect you: Pay it forward and help people. Your network will be one of the biggest drivers of your success.

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.