Google have published their internal AngularJS Style Guide. It contains language and style rules, a basic naming convention (i.e. don’t use $ as a variable prefix), test-driven recommendations (use Jasmine and Karma), a link to newly-published directory structure recommendations, a guide to scope and prototypal inheritance and an ngInject example.
Google web performance engineer Ilya Grigorik has put together the definitive tome on bleeding-edge, high speed web apps. The book is packed with information on performance optimization best practices for TCP, UDP, and TLS protocols, and explains unique wireless and mobile network optimization requirements:
How prepared are you to build fast and efficient web applications? This eloquent book provides what every web developer should know about the network, from fundamental limitations that affect performance to major innovations for building even more powerful browser applications—including HTTP 2.0 and XHR improvements, Server-Sent Events (SSE), WebSocket, and WebRTC.
A truly superb list of aspirational qualities for software developers. It includes symptoms of each particular quality and guidelines on how to acquire the desired traits.
Signs that you’re a good programmer
1. The instinct to experiment first
2. Emotional detachment from code and design
3. Eager to fix what isn’t broken
4. Fascinated by the incomprehensible
5. Compelled to teach
Signs that you’re a fantastic programmer
1. Incorruptible patience
2. A destructive pursuit of perfection
3. Encyclopedic grasp of the platform
4. Thinks In Code
5. When In Rome, Does As Romans Do
6. Creates their own tools
Signs that you’re destined for more
1. Indifferent to Hierarchy
2. Excited by failure
3. Indifferent to circumstances
4. Unswayed by obligations
5. Substitutes impulse for commitment
6. Driven by experiences
Antipatterns (styles of design or process that may proliferate, but are ineffectual or counter-productive) can confound even the most battle-hardened of developers. Only knowledge can set us free, and to that end Source Making’s list of antipatterns is a welcome reminder.
Good software structure is essential for system extension and maintenance. Software development is a chaotic activity, therefore the implemented structure of systems tends to stray from the planned structure as determined by architecture, analysis, and design.
First, from your editor, as from your butler, there are no secrets. If you have allowed yourself to be lazy, careless, turgid, or sloppy, there is no concealing it.
Second, everyone – everyone – is capable of shoddy work, especially in the first draft. That is why writers need editing, not just self-editing, but editing from an independent set of eyes.
Third, humility should be the outcome. The writer should understand the human propensity toward error, and the editor should not assume some snooty sense of superiority for having ferreted out errors, because the editor is equally prone to them.*
* Anyone who doubts the fallibility of editors should see these confessions at the Subversive Copy Editor Blog.
Deadliest Web Attacks has published an article rallying against the dearth of high quality, secure code. Although most code is never seen by anyone but the core development team, in light of the recent Symantec source code theft the article is particularly pertinent:
How would you alter the risks associated with your web site if its source code were stolen? Hard-coded passphrases? String concatenation of SQL statements? How much security relies on secrecy of functionality versus secrecy of data? Think of it in terms of Kerchoff’s Principle, roughly “The system must not require secrecy and can be stolen by the enemy without causing trouble”. Kerchoff was writing about cryptography, but the concept applies well to software.