jamessom

ORM

Development dependencies:

• Microtest - A xUnit family unit testing microframework for Ruby. (100 LOC)

Features:

1. ORM::Attributes
2. ORM::Model
3. ORM::Record

jamessom

µ-test (Microtest)

A xUnit family unit testing microframework for Ruby.

Prerequisites

Ruby >= 2.2.2

Installation

jamessom

Rails Deployment to AWS EC2

Stack : (Nginx + Phusion Passenger + Postgresql)

By Manoj Naidu

Here is the Video Tutorial

• Step -1

  To Launch an EC2 instance from aws console with all the credentials and configurations hooked.

• Step-2

jamessom

sudo apt-get update

echo 'installing curl' 
sudo apt install curl -y

echo 'installing git' 
sudo apt-get install git -y

echo "What name do you want to use in GIT user.name?"
read git_config_user_name

jamessom

With Docker Desktop becoming more restricted, I've decided to move on to just using minikube. In doing so, I've consolidated my notes as follows.

Installation

Use brew to install the docker cli and minikube.

$ brew install minikube docker kubectl hyperkit

Running Minikube

The first time you start minikube, you should specify any settings you desire.

jamessom

jamessom

Architecture Haiku

• March 03, 2015

The most effective way to transfer complex, abstract ideas from one person’s brain to another person’s brain is by writing the ideas down. This premise permeates our whole approach to software design. Entire books are dedicated to creating better documentation! Following traditional documentation advice inevitably leads to comprehensive, albeit verbose, documents filled with important details that, sadly, too few stakeholders read. There must be a better way.

Introducing the Architecture Haiku

George Fairbanks originally came up with the idea of the Architecture Haiku as "a one-page, quick-to-build, uber-terse design description." With only one page of paper (assumed standard, A4) to work with there is no space to be indecisive or indirect. There might not even be room for diagrams - which at first sounds crazy, but perhaps is crazy brilliant! We tr

jamessom

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.

jamessom

Aperfeiçoe seus commits!

Sempre que falamos sobre o uso de ferramentas open source, é interessante buscar padrões que atendam ao seu fluxo de trabalho, pois na maioria das vezes essas ferramentas disponibilizam não só uma maneira de resolver um problema, mas sim uma gama de possibilidades. No caso específico do git, isso não é diferente.

Abaixo, veja algumas dicas para tornar o uso do git ainda melhor e garantir um padrão para o seu fluxo de trabalho.

Padronização e automação de ações no repositório

Antes de tudo, é importante ressaltar que as ferramentas descritas aqui são baseadas no padrão Conventional Commits. Essa ferramenta visa criar um padrão para que seja mais fácil e intuitivo ler os logs, entre outras vantagens.

jamessom

The Unofficial 37signals/DHH Rails Style Guide

About This Document

This style guide was generated by Claude Code through deep analysis of the Fizzy codebase - 37signals' open-source project management tool.

Why Fizzy matters: While 37signals has long advocated for "vanilla Rails" and opinionated software design, their production codebases (Basecamp, HEY, etc.) have historically been closed source. Fizzy changes that. For the first time, developers can study a real 37signals/DHH-style Rails application - not just blog posts and conference talks, but actual production code with all its patterns, trade-offs, and deliberate omissions.

How this was created: Claude Code analyzed the entire codebase - routes, controllers, models, concerns, views, JavaScript, CSS, tests, and configuration. The goal was to extract not just what patterns are used, but why - inferring philosophy from implementation choices.