What I’ve noticed since leaving Svpply is that other industries treat their 1% differently. In the fashion or magazine industries for instance, they give the creative output of their star members their full attention. The 1% is the whole thing. There’s no open invitation to contribute content to Monocle.
With hindsight, I feel the reason Svpply never grew into anything substantial is because we misread the opportunity. Smallness was the steam that drove our engine and we opened the gasket.
The familiar social network pattern is to aspire to convert the whole world into a member.
We think there’s room for a different approach. A social network that’s both niche and healthy. A social network that’s more magazine than platform.
I don’t consider myself a Sass newbie by any means – I’ve been using it for over 2 years and feel that I can do everything I need to in order to build great websites – yet I took one look at that mixin and it scared the crap out of me. In fact, it still does and I’ve looked at it a dozen times now. If I took over maintaining a project and all the Sass looked as complex as that, I’d feel a little out of my depth maintaining the project.
We just gather all the stuff from top developers and put here. Since it come from exceptional folks, we could say that it is “the right way”, or the best way to do so.
Here, we address head on the tendency of JS developers to learn “just enough” to get by, without ever forcing themselves to learn exactly how and why the language behaves the way it does. Furthermore, we eschew the common advice to retreat when the road gets rough.
These books each take on specific core parts of the language which are most commonly misunderstood or under-understood, and dive very deep and exhaustively into them. You should come away from reading with a firm confidence in your understanding, not just of the theoretical, but the practical “what you need to know” bits.
Sometimes when you need to examine the results of a JSON response, using your browser’s developer tools console just won’t cut the mustard. In such a case, a good alternative would be to copy the JSON object from the console and to view it in your text editor. It’s not quite as easy as ‘CMD + C’, ‘CMD + V’ though, so here’s a quick primer. Specifically, these instructions are for copy the response from Chrome’s Developer Tools console to Sublime text 2.
First, we need to copy the JSON object from the console:
// where res.data is the JSON object copy(JSON.stringify(res.data))
Now, if you don’t already have it, you’ll need to install the Sublime Text 2 package, ‘Pretty JSON’. I got it via Package Control. Read more about Package control and installing new packages here.
Once you have the package installed:
That’s it! You could also use the shortcut code for reformatting with Pretty JSON, which is ‘^ + CMD + J’
Is a new feature requiring weeks of time and thousands of lines of code? That’s your code telling you there’s probably a better way. Is there a simple way to code something in one hour instead of a complicated way that will take ten hours? Again, that’s your code guiding you. Listen.