Luis Carlos Hernandez Macias luiskhernandez

Growing Rails Applications in Practice

How to use discipline, consistency and code organization to make your code grow more gently.
As you cycle through patterns, your application is becoming a patchwork of different coding techniques.

All those new techniques actually help, or if you are just adding layers of inderection.
Large applications are large so what we can do is organize a codebase in a way that "scales logarithmically".

Commit Message Format

This specification is inspired by and supersedes the [AngularJS commit message format][commit-message-format].

We have very precise rules over how our Git commit messages must be formatted. This format leads to easier to read commit history.

Each commit message consists of a header, a body, and a footer.

Update: I no longer work for the company and this challenge is no longer used, but I'll leave the gist here in case people want to practice.

Alphasights Technical Challenge

Using Ruby on Rails we would like you to create a simple expert search tool. The application should fulfill the requirements below. The source code must be placed in a public repo on GitHub. The application should be deployable on Heroku.

I enter a name and a personal website address and a member is created.
When a member is created, all the heading (h1-h3) values are pulled in from the website to that members profile.
The website url is shortened (e.g. using http://goo.gl)
After the member has been added, I can define their friendships with other existing members. Friendships are bi-directional i.e. If Sasha is a friend of Ash, Ash is always a friend of Sasha as well.

	ruby '2.2.0'
	source 'https://rubygems.org'

	...

	gem 'font-awesome-rails'

	###############################################################################
	# Helpful Docker commands and code snippets
	###############################################################################

	### CONTAINERS ###
	docker stop $(docker ps -a -q) #stop ALL containers
	docker rm -f $(docker ps -a -q) # remove ALL containers
	docker rm -f $(sudo docker ps --before="container_id_here" -q) # can also filter

	# exec into container

	function OnBlurComponent({ onBlur }) {
	const handleBlur = (e) => {
	const currentTarget = e.currentTarget;

	// Check the newly focused element in the next tick of the event loop
	setTimeout(() => {
	// Check if the new activeElement is a child of the original container
	if (!currentTarget.contains(document.activeElement)) {
	// You can invoke a callback or add custom logic here
	onBlur();

	require 'rails_helper'

	RSpec.describe TodosController, :type => :controller do

	describe "GET #index" do
	#describe "POST #create" do
	#describe "GET #show" do
	#describe "PATCH #update" do (or PUT #update)
	#describe "DELETE #destroy" do
	#describe "GET #new" do

	// layout file

	<body>
	<div class="container">

	<%= flash_messages %>

	<%= yield %>
	</div><!-- /container -->
	</body>

	# This is a skeleton for testing models including examples of validations, callbacks,
	# scopes, instance & class methods, associations, and more.
	# Pick and choose what you want, as all models don't NEED to be tested at this depth.
	#
	# I'm always eager to hear new tips & suggestions as I'm still new to testing,
	# so if you have any, please share!
	#
	# @kyletcarlson
	#
	# This skeleton also assumes you're using the following gems:

	app.directive('ngFocus', ['$parse', function($parse) {
	return function(scope, element, attr) {
	var fn = $parse(attr['ngFocus']);
	element.bind('focus', function(event) {
	scope.$apply(function() {
	fn(scope, {$event:event});
	});
	});
	}
	}]);