Checking to see if a file exists is a two step process in Python. Simply import the module shown below and invoke the isfile function:

import os.path
os.path.isfile(fname)

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.

1. The IRS is enabling taxpayers to download their tax transcripts over the internet from the Internal Revenue Service. The official secure URL for the transcripts download followed immediately after The White House fact sheet confirmed the decision. According to the Tech Crunch You Can Now Download Your Tax Returns From The IRS  article, there are some minor bug issues when registering. Given that security has long been problematic with the IRS, the best course of action for the public is to take some precautions when downloading personal information on mobile devices, pc’s and laptops. Installing disk encryption software on all your devices will protect your files reduce risk
2. Have an awesome Start-Up with products in ‘stealth or private beta” that you want like to pitch for a chance to get a table at Disrupt NY? TechCrunch is heading to Atlanta and New Orleans February 18^th and 20^th 2014 and will host a beer fest night in exchange for your thoughts and pitches. Tickets are $5, and all entrepreneurs, investors, dreamers or tech enthusiast are welcome.
3. Cloutex, a cloud computing future enabler has just secured their first round of seed funding.  Cloutex is an Estonian tech startup, which connects and syncs various web applications such as e-marketing, CRM and accounting tools under one convenient hub. The United Partners, SmartCap and EstBan business angels seeded the start-up with $6000, 000.
4. Could you get everything important that you need to know about living successfully from a computer program? Ryan Dube seems to think so. In his 6 Life Habits That Programming Could Teach You Today  he speaks in flow charts, loops and program modules, in the same breath as paying off debt or buying a house.  How can your programming skills help in life skills by modeling some of the same principles?
5. 10 Incredibly Simple Things You Can Do To Protect Your PrivacyPassword protect your devices.  Put alerts on your name in Google; simple tasks that can be significant in protecting your privacy.
6. Adobe Brings 3D Printing Support to PhotoshopAmong the latest updates in Adobe, Photoshop users have the ability to design 3D models from scratch as well as being able to toy around with color, shape and angles.

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