Businesses “Going Green” is so commonplace now it’s more than just an encouraging a trend; it’s become expected of companies big and small. In fact, consumers frequently place more of an obligation on companies to go green than they do themselves. The last few years—the infancy of what may turn out to be a green revolution—have really proven that there are many ways to go green, and that some of these ways are much more financially sound than others. But rather than providing a cut and dry list of green options and their pros and cons, I’d like to take a look at the bigger picture incentives for businesses going green and how consumers are responding.

What does it mean to be green?

It is said that spoken languages shape thoughts by their inclusion and exclusion of concepts, and by structuring them in different ways. Similarly, programming languages shape solutions by making some tasks easier and others less aesthetic. Using F# instead of C# reshapes software projects in ways that prefer certain development styles and outcomes, changing what is possible and how it is achieved.

F# is a functional language from Microsoft's research division. While once relegated to the land of impractical academia, the principles espoused by functional programming are beginning to garner mainstream appeal.

As its name implies, functions are first-class citizens in functional programming. Blocks of code can be stored in variables, passed to other functions, and infinitely composed into higher-order functions, encouraging cleaner abstractions and easier testing. While it has long been possible to store and pass code, F#'s clean syntax for higher-order functions encourages them as a solution to any problem seeking an abstraction.

F# also encourages immutability. Instead of maintaining state in variables, functional programming with F# models programs as a series of functions converting inputs to outputs. While this introduces complications for those used to imperative styles, the benefits of immutability mesh well with many current developments best practices.

For instance, if functions are pure, handling only immutable data and exhibiting no side effects, then testing is vastly simplified. It is very easy to test that a specific block of code always returns the same value given the same inputs, and by modeling code as a series of immutable functions, it becomes possible to gain a deep and highly precise set of guarantees that software will behave exactly as written.

Further, if execution flow is exclusively a matter of routing function inputs to outputs, then concurrency is vastly simplified. By shifting away from mutable state to immutable functions, the need for locks and semaphores is vastly reduced if not entirely eliminated, and multi-processor development is almost effortless in many cases.

Type inference is another powerful feature of many functional languages. It is often unnecessary to specify argument and return types, since any modern compiler can infer them automatically. F# brings this feature to most areas of the language, making F# feel less like a statically-typed language and more like Ruby or Python. F# also eliminates noise like braces, explicit returns, and other bits of ceremony that make languages feel cumbersome.

Functional programming with F# makes it possible to write concise, easily testable code that is simpler to parallelize and reason about. However, strict functional styles often require imperative developers to learn new ways of thinking that are not as intuitive. Fortunately, F# makes it possible to incrementally change habits over time. Thanks to its hybrid object-oriented and functional nature, and its clean interoperability with the .net platform, F# developers can gradually shift to a more functional mindset while still using the algorithms and libraries with which they are most familiar.

Related F# Resources:

F# Programming Essentials Training

I remember the day like it was yesterday. Pac Man had finally arrived on the Atari 2600.  It was a clear and sunny day, but it was slightly brisk. My dad drove us down to the video store about three miles from our Michigan house. If I remember correctly, the price for the game was $24.99.  It was quite expensive for the day, probably equaling a $70 game in today’s market, but it was mine. There *was* no question about it. If you purchase a game, it’s your game… right?

You couldn’t be more wrong.  With all the licensing agreements in games today, you only purchase the right to play it. You don’t actually “own” the game. 

Today, game designers want total control over the money that comes in for a game. They add in clauses that keep the game from being resold, rented, borrowed, copied, etc. All of the content in the game, including the items you find that are specifically for you, are owned by the software developer. Why, you ask, do they do this? It’s all about the money.

This need for greed started years ago, when people started modifying current games on the market. One of the first games like this was Doom. There were so many third part mods made, but because of licensing agreement, none of these versions were available for resale. The end user, or you, had to purchase Doom before they could even install the mod.  None of these “modders” were allowed to make any money off their creation.

Many individuals are looking to break into a video game designing career, and it's no surprise. A $9 billion industry, the video game designing business has appeal to gamers and non-gamers alike. High salaries and high rates of job satisfaction are typical in the field.

In order to design video games, however, you need a certain skill set. Computer programming is first on the list. While games are made using almost all languages, the most popular programming language for video games is C++, because of its object-oriented nature and because it compiles to binary. The next most popular languages for games are C and Java, but others such as C# and assembly language are also used. A strong background in math is usually required to learn these languages. Individuals wishing to design games should also have an extensive knowledge of both PCs and Macs.

There are many colleges and universities that offer classes not only in programming but also classes specifically on game design. Some of these schools have alliances with game developing companies, leading to jobs for students upon graduation. Programming video games can be lucrative. The average game designer's salary is $62,500, with $55,000 at the low end and $85,000 at the high end.

Programmers are not the only individuals needed to make a video game, however. There are multiple career paths within the gaming industry, including specialists in audio, design, production, visual arts and business.

Designing a video game can be an long, expensive process. The average budget for a modern multiplatform video game is $18-$28 million, with some high-profile games costing as much as $40 million. Making the game, from conception to sale, can take several months to several years. Some games have taken a notoriously long time to make; for example, 3D Realms' Duke Nukem Forever was announced in April 1997 and did not make it to shelves until July 2011.

Video game programmers have a high level of job satisfaction. In a March 2013 survey conducted by Game Developer magazine, 29 percent of game programmers were very satisfied with their jobs, and 39 percent were somewhat satisfied.

If you're interested in a game development career, now's the time to get moving. Take advantage of the many online resources available regarding these careers and start learning right away.