Weekly interesting reads on science, self-development and maintaining a non-commercial open-source project

Today I share with you the list of non-development articles which I collected during the last few weeks. There's a very interesting narration by Remy Sharp about his experience in creating and maintaining JSBin, useful articles on time perception and human psycology, some intriguing physics discoveries and wonders of the nature and finally a link to the NYC pictures pinned to the map.

Proceed to reading

Developer's bookmarks #1: progressive web apps, automated testing pyramid, thoughts about good code and some CSS fun

This time I decided to separate all related to software development stuff from personal and other things that are interesting but are off the topic.

Here is a huge list of articles which I, by means of some unknown magic (even for me!), could read in the course of the past week. The most interesting and fun story which I'd like to start with is the history of the blink tag. This is an amazing read of the kind I like most of all: an amusing story on something very related to me and my experience (of course, technologies and guys who invented them). Must read for everyone!

Proceed to a huge list of notes on web apps, automated testing, CSS, variable declaration types in JavaScript and so on

Bookmarks #2

This week's bookmarks list can be way more interesting for programmers than the previous one because there's one very interesting historical narration and some links about front-end development. There're also some links for those who like science and is interested in world's experience of avoiding traffic jams.

Read more about e-mail history, birds and something else

The splice error pattern

Imagine you’re writing an algorithm which performs looping over an array with any type of pointer (for or while loop, forEach, map etc). Each iteration the pointer moves in any direction, but you never force it to come back in the most of cases. Why should you? This mode of manipulating data is so much usual that your probably have never ever thought of its liability to hard-to-find annoying errors which will lead you toward wearing debugging!

The erroneous pattern is very simple and obvious. Say you need to map some action to all array elements and write.

var arr = [1, 2, 3];

function act(item) {

Already understood what happens?