Many of you may have heard the story of Aaron Swartz, a genius who helped shape the internet into what it is today. Someone who fought for an open access to the collective human knowledge, and the inherent right of internet access to all people. He was “made an example of” for a trivial lawsuit which ended in the US justice system driving him to suicide with their overreach in a case they didn’t truly understand.
In the first post of this series we learned how to create a user resource with Sails.js that allowed us to create and authenticate user accounts in our API. In this post we will be creating a resource that our user owns and learn how to create access control around that resource. Sails makes it pretty easy to accomplish.
I’m really enjoying the Sails.js framework. I see a lot of potential here for use on ‘real’ work, plus it’s just a really cool idea. I’m going to start building an example application using Sails and the first step is user authentication. I’m going to be building this as an API, so all of the example will simply use GET and POST requests to the REST API that Sails makes so easy for us. Let’s dive in.
Recently I’ve been looking around at different Node.js projects that aim to be to Node what Rails is to Ruby. There’s a handful out there: Tower.js, Derby.js, Compound.js. But most recently I came across one called Sails.js. This one has really caught my eye, and I want to write up a quick post about why it’s awesome.
I’ve hit a recurring dilemma several times throughout my journey as a developer. This dilemma involves the choice of tools and technologies I use to create things with. There are choices out there that make the job easier, are more helpful, and they are this way because they hide some of the complexity of what is actually happening from you. I always ask “can I really feel proud of building this if the tool I used did so much of the work for me?”.
For the longest time I have grown as a developer knowing about all these amazing conferences and community events for developers happening all over the world, and to this day I still have no attended a single one. It seemed to me that developers in my area did not organize many community events. That is until recently. Now, the efforts of a few have brought a couple new things to Wichita to contribute to the developer community.
I don’t have to tell you every reason why commenting code is important. Most of us know already. However, if you’re anything like me, it can be easy to forget about these benefits when you’re in the middle of writing your code. You want to keep the flow moving and stopping to think about how you can explain the logic in plain english can be a roadblock. This post serves as a reminder to myself, and hopefully to others, of the major benefits of commenting.
This blog certainly isn’t updated as often as I would like. Even when it is, the posts are minimal, I don’t use a lot of other functionality outside of categories and pagination. Previously this website was running on WordPress but I’ve decided to move away from that for a few reasons. Though primarily I was just tired of WordPress.
I use the word ‘awesome’ pretty excessively, so this project appealed to me right off the bat. Beyond word-choice, though, Font Awesome is an open source icon-font available for use in your websites, and it’s some seriously high quality stuff. I’m using it here on my recent redesign, and with a recent addition of 70 new icons in the latest version, there’s bound to be some awesome icons that are a perfect fit for your project.