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?

It is hard not to wonder how current technology would have altered the events surrounding the tragic death of John F. Kennedy. On the afternoon of November 22, 1963, shots rang out in Dallas, TX, taking the life of JFK, one of the most beloved Americans. Given the same circumstances today, surely the advances in IT alone, would have drastically changed the outcome of that horrible day. Would the government have recognized that there was a viable threat looming over JFK? Would local and government agencies have been more prepared for a possible assassination attempt? Would the assortment of everyday communication devices assisted in the prevention of the assassination, not to mention, provided greater resources into the investigation? With all that the IT world has to offer today, how would it have altered the JFK tragedy?

As many conspiracy theories have rocked the foundation of the official story presented by government agencies, realization of the expansive nature of technology provides equal consideration as to how the event would have been changed had this technology been available during the time of the shooting. There were T.V. cameras, home 8mm recorders, even single shot-hand held cameras snapping away as the car caravan approached. Yet, there remains little documentation of the shooting and even less information pertaining to the precautions taken by officials prior to JFK's arrival. Theorists consider these possibilities along with how the world would have turned out had the great John F. Kennedynever been assassinated on that day.

Python and Ruby, each with roots going back into the 1990s, are two of the most popular interpreted programming languages today. Ruby is most widely known as the language in which the ubiquitous Ruby on Rails web application framework is written, but it also has legions of fans that use it for things that have nothing to do with the web. Python is a big hit in the numerical and scientific computing communities at the present time, rapidly displacing such longtime stalwarts as R when it comes to these applications. It too, however, is also put to a myriad of other uses, and the two languages probably vie for the title when it comes to how flexible their users find them.

A Matter of Personality...

That isn't to say that there aren't some major, immediately noticeable, differences between the two programming tongues. Ruby is famous for its flexibility and eagerness to please; it is seen by many as a cleaned-up continuation of Perl's "Do What I Mean" philosophy, whereby the interpreter does its best to figure out the meaning of evening non-canonical syntactic constructs. In fact, the language's creator, Yukihiro Matsumoto, chose his brainchild's name in homage to that earlier language's gemstone-inspired moniker.

Python, on the other hand, takes a very different tact. In a famous Python Enhancement Proposal called "The Zen of Python," longtime Pythonista Tim Peters declared it to be preferable that there should only be a single obvious way to do anything. Python enthusiasts and programmers, then, generally prize unanimity of style over syntactic flexibility compared to those who choose Ruby, and this shows in the code they create. Even Python's whitespace-sensitive parsing has a feel of lending clarity through syntactical enforcement that is very much at odds with the much fuzzier style of typical Ruby code.

For example, Python's much-admired list comprehension feature serves as the most obvious way to build up certain kinds of lists according to initial conditions:

a = [x**3 for x in range(10,20)]
b = [y for y in a if y % 2 == 0]

first builds up a list of the cubes of all of the numbers between 10 and 19 (yes, 19), assigning the result to 'a'. A second list of those elements in 'a' which are even is then stored in 'b'. One natural way to do this in Ruby is probably:

a = (10..19).map {|x| x ** 3}
b = a.select {|y| y.even?}

but there are a number of obvious alternatives, such as:

a = (10..19).collect do |x|
x ** 3
end

b = a.find_all do |y|
y % 2 == 0
end

It tends to be a little easier to come up with equally viable, but syntactically distinct, solutions in Ruby compared to Python, even for relatively simple tasks like the above. That is not to say that Ruby is a messy language, either; it is merely that it is somewhat freer and more forgiving than Python is, and many consider Python's relative purity in this regard a real advantage when it comes to writing clear, easily understandable code.

And Somewhat One of Performance