🌊 Pretty, common and useful algorithms with modern JS and beautiful tests - jiayihu/pretty-algorithms
Investors will not be interested in your product until you can show them that a big market is getting interested.
Linked is yet another nice explanation of what REST-ful and REST APIs really mean. What is the test? Is this a restful API or not?
There’s never been a better time to act on your “big idea”. And this manifesto will show you how.
Concurrency is a boon, so make sure you know how multi-threading works. Let's examine the important components of threads and how to use them together.
Linked is a guide to concurrency in Java.
An introduction to real-time WebSocket apps with Rails
A deep dive into achieving concurrency using multi-process.
If your Rails app is getting slower, here are some tips on how you can make your Active Record queries faster.
The rise of the web and mobile applications has led to an increased need for back-end API services. Ruby on Rails' philosophy seemingly makes it the ideal framework for creating back-end APIs. However, using Rails only for the API is overkill. In this article, Freelance Software Engineer Boško Ivanišević explore...
Comprehensive data proxy to knowledge about real world - molybdenum-99/reality
Almost every web app requires a sign in form.In Ruby, the popular choice is the Devise gem for Rails.
We're happy to announce Clearbit's free Logo API. While services like Gravatar make it straightforward to pull in a user's default avatar, we haven't found anything that caters well to company logos. And yet there's a lot of clear use-cases ranging from setting an organization's default image on signup to
cancelled_at).to be_a(Time) end end end SINGLE RESPONSIBILITY If your method doesn't fall into one of the three categories above - meaning that its purpose isn't defined by a result, a method call, or a side effect - perhaps it's doing too much.
How and why should you use JSON API in your Rails API? Crafting a well-behaving API is a virtue. It is not easy to come up with good standards of serializing resources, handling errors and providing HATEOAS utilities to your design. There are a lot application-level concerns you need to make - whether you want to send back responses in mutation requests (like PUT/PATCH/POST requests) or just use HTTP headers. And it is hard - and by hard I mean you need to spend some time to get it right. There are other things you need to be focused on which are far more important than your API. Good under...
Part one of a four-part series which will show you how to optimize a memory-heavy Rails API action.