Магикология

Brian W. Kernighan, in the paper Unix for Beginners (1979)

Today I want to talk a little about scope in JavaScript and the `this` variable. The idea of "scope" is that it's where certain functions or variables are accessible from in our code, & the context in which they exist & are executed in.

 HTML5 localStorage provides us with the ability to store named key/value pairs locally within a users browser, this means that the data stored in localStorage is still there even after a user has closed the browser, deleted their cookies or turned off their machine/device. The HTML5 localStorage attribute is supported by most modern browsers including Firefox 3.5+, Chrome 4+, Safari 4+, Mobile Safari, Android 2+ and Internet Explorer 8+. Now lets dive into some code and create a basic working example. In this example we are going to create a simple form which stores the data entered into the form so that if the form isn’t submitted but the browser is closed the data is still store and then retrieved when the user returns to the form.

I write a lot of low-level C code dealing with Unix processes and the like. I have seen a few folks roll their own spawn function, and do it wrong, so this page is meant to serve as an overview of your options when writing programs using only core Unix functions.

 There has been a lot of discussion on the [Go Nuts](https://groups.google.com/forum/#!forum/golang-nuts) mailing list about how to manage versioning in the nascent [Go](http://golang.org/) package ecosystem. We muttered about it at first, and then muttered about it some more when `goinstall` came about, and there has been a pretty significant uptick in discussion since the `go` tool began to take shape and the [Go 1](http://golang.org/doc/go1.html) release date approached. In talking with other Gophers at the GoSF meet-up recently, there doesn’t seem to be anyone who really has a good solution.

 Improved productivity is the goal of every freelancer. Ever since I started my one-man business, I have looked for ways to improve my productivity and get things done faster. There were a couple of methods that seemed to lead to small improvements, but overall none of them proved efficient. That is, until I discovered agile techniques. In this post, I’ll discuss some of the ways that agile techniques can help improve a freelancer’s productivity. Specifically, I’ll look at agile methods in general and at Scrum methodology.

 Testing your code is annoying, but the impact of not doing so can be orders of magnitude more annoying! In this article, we’ll use test-driven development to write and test our code more effectively.

Since I'm working with _Erlang/OTP_ and _Go_ and point out their powerful handling of _concurrency_ I've often been asked what's special with it and how it can be used. Additionally many people just mixup concurrency and parallelism. So to make it more clear I have to start by leaving computer — don't panic, I'll return later.

Don Knuth is writing an impressive book series called "The Art of Computer Programming" since the 1960s. In 1977 he created TeX, to produce high-quality documents independently of the current printing technology. In the 1980 Leslie Lamport built LaTeX on top, which provides a lot convenient macros. For producing text-heavy pdfs TeX is the tool, which sucks least.

**Understanding MVVM – A Guide For JavaScript Developers** MVVM (Model View ViewModel) is an architectural pattern based on MVC and MVP, which attempts to more clearly separate the development of user-interfaces (UI) from that of the business logic and behaviour in an application. To this end, many implementations of this pattern make use of declarative data bindings to allow a separation of work on Views from other layers.

Getters and setters are a means of providing an arm's-length way of getting or setting certain data, whilst keeping private other data, and are common of most languages. In JavasScript, setters are also a good way of ensuring your UI stays up to date as your data changes, which I'll show you an example implementation further down.

 This page explains how to write websites that do not break when new browser versions are released. This is especially important for intranets and other non-public websites; if we can't see your code, we can't see that it broke. It's not always possible to follow all of these, but following as many of them as possible will help future-proof your website