This section of our beginning python training class always stumps students.  Firstly, because they need to know the difference between a function and a method.  Secondly, they need to understand object oriented programming concepts.  Thirdly, they need to realize that python has three types of methods.  Then they need to know how to use each method, which means they need to know the purpose of each method type.  Then they have to understand mutable versus non-mutable types.  The list goes on.  As part of our python tutorial, I hope to shed some light on this confusing topic.

To begin, the difference between a function and a method in python is that a method is defined within a class.  Here is an illustration:

#function

	def greeting():
	                print "Hello, I hope you're having a great day!"

	class HSGPrinter(object):
	                #method
	                def greeting(self): 
	                                print "Hello, I hope you're having a great day!"

As should be obvious, the second definition of greeting is encapsulated within the HSGPrinter class and is , therefore, refered to as a method.

The astute reader will notice that the greeting method contains one parameter named self.  For those who know C++ , Java or C#, self is equivalent to this i.e. it is a reference to the invoking object:

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.

There are a lot of articles you will find on the internet that talk about the tenants of having a successful professional career. From soft-skills to job relevant skills, there is an unending list of the do’s and don’ts for establishing a great career. However, a successful career in information technology commands some specific efforts and focus. As a result, it is critical to focus on these 4 key tenants that can help you establish a promising and successful career in Information Technology.

·         Be Multi-lingual– This is the analogy of Steve Job’s famous quote ‘Stay Hungry, Stay Foolish’ as it applies to Information Technology. Gone are the days when you could train yourself on a specific programming language say Java or C++ and code your way to a successful career. The best programmers of today and tomorrow are pushing the limits and becoming experts in one of more languages. Knowing more than one programming language instantly makes you more employable since you can add value to multiple projects that require different languages. If you need proof, IT professionals knowing more than one language can attract a salary premium of £10,000 . Additionally, there is no telling how dynamic technology is and by being open to constantly learning new languages you will position yourself to get technology jobs that did not exist a few years ago

·         Go Beyond the ‘How’, Focus On ‘Why’: A common theme with most information technology professionals is their ability to figure out the HOW or, in other words, applying their technical know-how in achieving the solution to a problem. This is especially true when you are working for a service based IT organization where your key job is to develop a solution for the client’s business problem. Yes, you are and will get paid to be good at the ‘How’ but to advance a career in IT; it will help you immensely to also start focussing on the ‘Why’. This stems from a famous quote by Einsten “If I were given one hour to save the planet, I would spend 59 minutes defining the problem and one minute resolving it”. In essence, spend time in understanding ‘Why’ are your trying to solve the problem before you get down with figuring out the ‘How’ part. The reasons for developing this mindset are two-fold. One, you will instantly distinguish yourself from thousands of other IT peers who are content with the ‘How’ part. Two, there is a good chance that you want to get ahead in your career not only as a programmer but as a system architect or a business solution consultant. This is where the habit of asking the right questions pertaining to why a certain IT solution is requires will help you build the right solution.

·         Focus on the impact and results (Financial impact):This may not apply to IT professionals who are early in their careers but is paramount for senior IT professionals. For the most part, IT departments are required to make sure that the systems and the solutions function as desired and help the business run efficiently. In other words, the key metric for success for most IT professionals is being extremely good at technology, languages and Quality Assurance. However, the times are changing! No longer is the Chief Information Officer (CIO) in charge of making IT decisions. With organizations closely guarding the ROI of their investment in technology, CIOs are increasingly required to be cognizant of the financial benefits of technology so that they can justify the spending on IT. No wonder than that CFOs are increasingly pressurizing CIOs to get their act together

Toshiba has released a new line of solid-state drives (SSD) using 19 nanometers, which is currently the industry’s smallest lithography process.

The lineup will include mini-SATA and 2.5-inch form factors along with drives in 7mm and 9.5mm heights. All drives will use the most current serial ATA 6Gbps interface protocol.