What a year! A report of everything awesome that happened in 2016; in numbers, and data.
Monthly active users
The ones that sparked the most interesting conversations...
The ones that were most appreciated...
I use the format from this project and I find it incredibly useful when you are skimming through the commits.
Each commit message should include a type, a scope and a subject:
The whole community welcomes you! I'm really glad to see you as one of us - the awesome people of Hashnode. :)
Promise me one thing - please don't allow your condition to dictate your life. You are much, much stronger than you think. If you are passionate about programming and loves to do it, no matter your current status, you can get the job you want. It will be hard, it will be time consuming and exhausting, but it will totally worth it.
As a Full Stack Developer it is very important that you have deep knowledge of every part of the application. This means you have to know the languages, patterns, optimization opportunities and how 3rd party software works under the hood. The security, stability and performance of the whole architecture should be your highest priority.
The following paragraphs will look very ugly. Maybe I will clean them, but this will have to do for today (I am tired. sry). I just wrote down whatever came to my mind, so it will sound repetitive and boring. It will contain bugs.... I mean typos. Edits welcome!
Here are a few questions you might answer to guide yourself through building a Facebook-like feed:
Twitter used to call this the "Bieber problem": when he tweeted, a fan-out operation occurred, placing this new tweet into the feeds of every one of his followers which was a massive job that locked up whole machines. In Twitter's earlier years, a couple quick @justinbieber tweets in a row could "fail whale" the whole service.
Answering this question well requires looking at React from a couple of different perspectives. It also requires understanding a bit of the 35+ year history of presentation patterns as well as an understanding of web technology's purposes and intents.
First, it's important to understand that Separated Presentation patterns emerged mostly in the context of creating component models on various platforms. For example, MVC originated in Smalltalk, Supervising Controller and Passive View have their origins in things like Java Swing and Windows Forms, and Presentation Model and Model-View-ViewModel have their origins in binding-based technologies like Xaml, Flash/Flex and modern Web frameworks
The ones which attracted the most developers for their insights...
At Witworks we have been developing the Blink smartwatch, which runs on a customised version of Android called Marvin. We have also been building companion Android and iOS apps, for the smartwatch, in React Native (RN). If you're evaluating React Native for your next project, or just curious about it - here is my story. In this article, I will share our overall experience with RN, and the things we have learned so far.
At Hashnode we heavily use Node.js. I am a big fan of it and have learned a lot of things while running Hashnode. When I hang out with other developers, I notice that many people don't utilise Node to its full potential and do certain things the wrong way. So, this article is going to be about things which you shouldn't do while running Node in production. Let's get started!
So you've decided to try out Redux as your application state manager. Or perhaps you're investigating better options. Good for you. With Redux the good news is your application will enjoy a productivity boost from the simplicity of knowing precisely where data logic lives. However, Redux alone cannot protect you from a fashionable, spiced-up spaghetti mess. How does it fit into a multi-tiered application composed of several orders of widgets and components that each rely on asynchronous data? In order to save yourself from this ugly monster you'll need a higher order architectural convention.
I’ve always been a huge fan of Java. I started my career as a PHP developer and soon after that I was forced to work in perl in another project. With PHP’s consistent brokenness throughout the language and perl’s (alphabet-soup-puke)-like-syntax, getting into Python two years later was a huge improvement. However, certain things still irked me (which at that time I just couldn’t put into words), but it was there, like a splinter in my hand that would not go away.
Hate it or love it, you simply cannot ignore it. When it comes to Front-end frameworks, many people disproved their existence. I think it's about individual choices and when used properly, they do make your life easy.
In this article, I will be listing out some of the best front-end frameworks that you can try this year. And yes, I am going to ignore Bootstrap and Foundation for the time being. Relax. 👍
We're proud to have hosted some fantastic AMAs this year
Author of Vue.js. Previously at Google and Meteor. Parsons Alumnus.
Creator of CodePen, CSS-Tricks and Podcaster at ShopTalk
Creator of Laravel, Lumen, Forge, and Envoyer.
React core team at Facebook, previously at Khan Academy
Owner of Laracasts.com
In last two quarters of 2016, more than half a million people visited Hashnode.