Aspiring Web Developer

[...] is extremely developer-friendly on its own, so can be used in quite a custom manner in your Rails app. Unless you use a Stripe partner, you will be writing custom code to interface with Stripe.  [...]

[...] Sometimes we need to show tables of data in a Rails app, sort of like souped-up spreadsheets. The tables, or grids, should handle tons of records, [...]

[...] ActiveRecord with PostgreSQL, a thought-provoking slide deck. Detect N+1 issues in your Rails app with the Bullet gem. Full-text search is another area where you can harness cool database [...]

[...] about real-world results with React JS. Here is a concrete example of adding React to a Rails app, start to finish. React JS is a library from Facebook that powers user interfaces. It is [...]

[...] customer, by e-mail address. This is a search across two tables, orders and customers. Wice Grid, a fantastic data grid for Rails, makes this search easy. Check out our intro to Wice Grid if [...]

[...] , ordering, etc., every time. Why not use a pre-built solution and built off of it instead? Wice Grid is the quickest grid solution out there for Rails. It takes care of both the client and server. [...]

[...] This is part 3 of building a gem for targeted, one-time announcements to users in Rails. See part 2 and part 1. We’ll focus on targeting announcements to [...]

[...] building a Ruby gem to enable this. Tests I started by writing tests, describing what the one-time announcements gem should do. Test driven development (TDD) can be controversial, but I find that it [...]

[...] I’m developing a gem to deliver one-time announcements to users in Rails apps. See the previous parts of this series for some background. Now, [...]

[...] At Cook Smarts we need a way to provide one-time announcements to customers, right inside our Rails app. For instance, we may want to notify our paying [...]

[...] customer reads the announcement, he or she can close it and will never see it again. The closest Ruby gem I could find is thoughtbot’s paul_revere. It’s elegant and simple, providing one-off [...]

[...] , shown to each user only once, and targeted to particular types of users. We’re building a Ruby gem to enable this. Tests I started by writing tests, describing what the one-time announcements gem [...]

This is part 3 of building a gem for targeted, one-time announcements to users in Rails. See part 2 and part 1. We’ll focus on targeting announceme [...]

I’m developing a gem to deliver one-time announcements to users in Rails apps. See the previous parts of this series for some background. Now, i [...]

There are many React JS intros out there, but too few articles about bringing React into an existing Rails app. At Cook Smarts, we brought React J [...]

Say that in your Rails app’s admin interface you have a table of orders, each of which is associated with a customer. You need to find orders belo [...]

[...] I’m developing a gem to deliver one-time announcements to users in Rails apps. See the previous parts of this series for some background. Now, in part 4, we’ll test [...]

Developing an app is never a solo effort, even if you are the only developer in a company. We live an ecosystem of services and open source tools that [...]

[...] in your views Create the server-side API’s necessary to feed and interact with your React components (this is not React-specific, just something an app needs to do as it implements more client- [...]

[...]  works well in a Rails app. The global function creates the Fluxxor store and renders React components to the page. Here is its code, excluding the snippets we’ve already covered: The Rails view [...]

[...] -side data store. We still need to build our client-side UI, and that’s where React comes in. React apps are basically component trees. The ingredient suggestions editor contains multiple ingredient [...]