Controversy was recently courted as Southern California Edison (SCE) prepares to cut their own staff while looking to meet their staffing needs with offshore employees skilled in the field of “IT” or Informational Technology. This has been the second major utility company in the United States to take this path towards providing services to its consumers while holding current rates at consistent levels. SCE does not disclose the exact numbers of expected lay-offs, but the LA Times reports that it is in the hundreds.  Utility companies tell their consumers that these moves are necessary as a hedge against inflation and to keep their services at rates that their customers can easily afford. Critics claim that the use of foreign workers is the first step to using an entirely foreign workforce and promoting large scale unemployment amongst American citizens. Often this has been seen as a conflict between national and international workers for the same jobs, salaries and careers.

It has been noted that this State of California utility company, much like other corporations that hire foreign workers does so primarily when there is a shortage of national citizens that can perform these jobs well. IT workers that are brought in with H-1B Visa work permits usually are college educated and hold expertise in technical areas and studies that local employees may not be especially trained in. Once again, critics decry the fact that these employees are not hired directly. On shore contracting companies operating in the continental United States are directly hired by the utility companies. These contracted companies then serve as “middle-men” and hire a wide range of foreign workers with H-1B paperwork so that they can move to the United States. The workers then perform a variety of jobs instead of American workers who were either born in the country or have achieved American citizenship on their own.

Needless to say, the amount of visas issued in a given year is a concern for U.S workers in various fields but particularly in Information Technology. As large corporations stack the employment deck with foreign workers who put in the hours for a fraction of the pay-rate for local employees, local IT professionals are finding it more difficult to find work nationally.  They encounter rejections, endless interview processes or low –ball offers from companies and recruiting agencies looking to fill positions at a bare minimum cost for coveted skill-sets.  

Meanwhile, an H-1B worker is a worker brought in on a temporary basis with a visa allowing them to work freely in the United States. Much like a student or travel visa, it is issued for on a calendar oriented basis.  Applicants who successfully renew the visa for an extended period of time can expect to work in the United States for up to ten years.  Although U.S companies hiring these employees may pay them less than their local employees, the salaries earned by H-1B Visa workers are almost always higher than these workers would earn in their own country of origin.

Both sides can agree on several issues. When it comes to these H-1B Visa workers, their assignments are generally of a contractual nature and require them to reside in this country for a period of months to years. However it is also an accepted fact that while they are in this country, they are responsible for paying rent, utilities and all other living expenses. As residents of the United States on a permanent basis, they are also liable for taxes on any salary they have earned while living here.

Dr. Norman Matloff, a professor at the University of California, Davis and writer on political matters believes the shortage to be fiction. In his writing for the University of Michigan Journal of Law Reform, he claims that “there has been no shortage of qualified American citizens to fill American computer-related jobs, and that the data offered as evidence of American corporations needing H-1B visas to address labor shortages was erroneous. The American Immigration Lawyers Association (AILA) agrees with him and describes the situation as a crisis. Likewise, other studies from Duke, Alfred P. Sloan Foundation and Georgetown University have disputed that in some years, the number of foreign programmers and engineers imported outnumbered the number of jobs created by the industry

Studying a functional programming language is a good way to discover new approaches to problems and different ways of thinking. Although functional programming has much in common with logic and imperative programming, it uses unique abstractions and a different toolset for solving problems. Likewise, many current mainstream languages are beginning to pick up and integrate various techniques and features from functional programming.

Many authorities feel that Haskell is a great introductory language for learning functional programming. However, there are various other possibilities, including Scheme, F#, Scala, Clojure, Erlang and others.

Haskell is widely recognized as a beautiful, concise and high-performing programming language. It is statically typed and supports various cool features that augment language expressivity, including currying and pattern matching. In addition to monads, the language support a type-class system based on methods; this enables higher encapsulation and abstraction. Advanced Haskell will require learning about combinators, lambda calculus and category theory. Haskell allows programmers to create extremely elegant solutions.

Scheme is another good learning language -- it has an extensive history in academia and a vast body of instructional documents. Based on the oldest functional language -- Lisp -- Scheme is actually very small and elegant. Studying Scheme will allow the programmer to master iteration and recursion, lambda functions and first-class functions, closures, and bottom-up design.

Supported by Microsoft and growing in popularity, F# is a multi-paradigm, functional-first programming language that derives from ML and incorporates features from numerous languages, including OCaml, Scala, Haskell and Erlang. F# is described as a functional language that also supports object-oriented and imperative techniques. It is a .NET family member. F# allows the programmer to create succinct, type-safe, expressive and efficient solutions. It excels at parallel I/O and parallel CPU programming, data-oriented programming, and algorithmic development.

Scala is a general-purpose programming and scripting language that is both functional and object-oriented. It has strong static types and supports numerous functional language techniques such as pattern matching, lazy evaluation, currying, algebraic types, immutability and tail recursion. Scala -- from "scalable language" -- enables coders to write extremely concise source code. The code is compiled into Java bytecode and executes on the ubiquitous JVM (Java virtual machine).

Like Scala, Clojure also runs on the Java virtual machine. Because it is based on Lisp, it treats code like data and supports macros. Clojure's immutability features and time-progression constructs enable the creation of robust multithreaded programs.

Erlang is a highly concurrent language and runtime. Initially created by Ericsson to enable real-time, fault-tolerant, distributed applications, Erlang code can be altered without halting the system. The language has a functional subset with single assignment, dynamic typing, and eager evaluation. Erlang has powerful explicit support for concurrent processes.

Computer Programming as a Career?

What little habits make you a better software engineer?

Back in the late 90's, there were a number of computer scienctists claiming to know java in hopes of landing a job for $80k+/year.  In fact, I know a woman you did just that:  land a project management position with a large telecom and have no experience whatsoever.  I guess the company figured that some talent was better than no talent and that, with some time and training, she would be productive.  Like all gravey train stories, that one, too, had an end.  After only a year, she was given a pink slip.

Not only are those days over, job prospects for the IT professional have become considerably more demanding.  Saying you know java today is like saying you know that you have expertise with the computer mouse; that's nice, but what else can you do.   This demand can be attributed to an increase in global competition along with the introduction of a number of varied technologies.   Take .NET, Python, Ruby, Spring, Hibernate ... as an example;  most of them, along with many others, are the backbone of the IT infrastructure of most mid-to-large scale US corporations.  Imagine the difficulty in finding the right mix of experience, knowledge and talent to support, maintain and devlop with such desparate technologies.

Well imagine no more.  According to the IT Hiring Index and Skills Report, seventy percent of CIO’s said it's challenging to find skilled professionals today.  If we add the rapid rate of technological innovation into the mix of factors affecting more businesses now than ever before, it’s understandable that the skill gap is widening.  Consider this as well:  the economic downturn has forced many potential retires to remain in the workforce.  This is detailed in MetLife's annual Study of Employee Benefits which states that“more than one-third of surveyed Baby Boomers (35%) say that as a result of economic conditions they plan to postpone their retirement.”  How then does the corporation hire new, more informed/better educated talent?    Indeed, the IT skills gap is ever widening.

In order to compensate for these skill discrepencies, many firms have resorted to hire the ideal candidates by demanding they possess a christmas wish list of expertise in a variety of different IT disciplines.  It would not be uncommon that such individuals have a strong programming background and are brilliant DBA's.  What about training?  That is certainly a way to diminish the skills gap.

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.