This document originated from a bunch of most commonly used links and learning resources I sent to every new web developer on our full-stack web development team.
For each problem domain and each technology, I try my best to pick only one or a few links that are most important, typical, common or popular and not outdated, base on the clear trends, public data and empirical observation.
Prefer fine-grained classifications and deep hierarchies over featureless descriptions and distractive comments.
Ideally, each line is a unique category. The ” / “ symbol between the links means they are replaceable. The “, “symbol between the links means they are complementary.
I wish this document could be closer to a kind of knowledge graph or skill tree than a list or a collection.
It currently contains 2000+ links (projects, tools, plugins, services, articles, books, sites, etc.)
On one hand, this is one of the best single resources on the topic of web development that I’ve seen in a very long time. On the other hand, it re-confirms my belief in “there is no such thing as a full-stack web developer”. There’s just too many levels, and there’s too much depth to each level for a single individual to be an expert at. But you get bonus points for trying.
The discussion is far from finalized right now, so it’s particularly interesting to see how it develops, both in IRC/Slack chatrooms and in Make WordPress p2 comments.
Styles and color
Compositing and clipping
Hit regions and accessibility
It also provides a few useful tips, inspiration, and links to other resources.
There are days, when I feel jealous of all the young kids playing around with new technologies. I need a certain level of stability and acceptance of the technology before I can apply it to client projects. And I need time, which is a very scarce resource lately.
And yet there are days, when I feel good about being somewhat reserved and conservative in my technology stack choices. Reading this blog post makes me feel just that. Of course I need to try it out for myself and shape my own opinion, but with my lack of time, this should do.
Would I recommend it for large-scale products? Absolutely not. Do people do that anyway? Of course they do. I tried to.
I would also recommend Node for simple back-end servers mainly used for websockets or API relay.
Now if only somebody wrote a similar post about Docker …
Here’s something that came in helpful the other day at work – “Simple file upload using jQuery and AJAX“. We were on the right track, but this blog post helped iron out the last few details. In particular, this bit:
processData: false, // Don't process the files
contentType: false, // Set content type to false as jQuery will tell the server its a query string request
success: function(data, textStatus, jqXHR)
if(typeof data.error === 'undefined')
// Success so call function to process the form
// Handle errors here
console.log('ERRORS: ' + data.error);
error: function(jqXHR, textStatus, errorThrown)
// Handle errors here
console.log('ERRORS: ' + textStatus);
// STOP LOADING SPINNER
And a clarification of the parameters:
2 attributes need to be set to false:
processData – Because jQuery will convert the files arrays into strings and the server can’t pick it up.
contentType – Set this to false because jQuery defaults toapplication/x-www-form-urlencoded and doesn’t send the files. Also setting it to multipart/form-data doesn’t seem to work either.