As mentioned in my previous post, here is the roadmap I have planned out for Finesse this year.
Broadly I want to focus on 4 different categories of features, each with its own merits.
For the past couple of months, I’ve been hard at work in completely revamping the user experience on Finesse.
This includes changing the whole frontend framework (bootstrap to semantic-ui), redesigning all the pages and completely rewriting all the front-end code involved.
As you probably know, git is a popular version control software used in projects across the globe. One of the major features and one that distinguishes it from other tools is it’s branching mechanism. The code is usually tracked via commits and grouped by branches in git.
As the branches are lightweight and disposable it’s very easy to get cluttered when many people are working on a project or if there are many branches. And so, as anything with software, naming a git branch will itself need a standard convention to be followed in a project to keep it organized and sane. There are many naming formats out there and several project-specific ones I’ve worked with.
This is a follow-up post to my previous article on how to implement passwordless authentication in rails in sitepoint. It basically talks about how to implement login with just rails model, controller and a login token.
Recently I received an requirement to build a Password-less authentication system for a client project and while I wanted to do the way I have written in the article, I was looking out for if any viable options are out there since it’s been 3 years. And there is one. I stumbled across passwordless by mikker. It’s basically a gem that you can add it to your Rails project and get the password-less authentication system enabled.
Barring couple of hiccups I faced (project specific requirements, the PRs were promptly addressed), the gem works neatly as advertised. I’ve used it for the project and it’s running smoothly in production now.
That’s why this entry. I wanted to share the gem because it’s a nice solution for something I advertise a lot(get rid of those passwords!).
Recently I was debugging a code on Intelllex API and thought I’d share.
We have a product called Stacks, where users can save links, searches and files to it, which helps them with organizing their legal research. Our stack is Rails on the API side and Angular on the client side.
We use counter culture gem to cache the counts of things that are saved to stacks by users and we also have the ability where users can save and move stuff from one stack to multiple stacks.