We are AI-enabled software consultants
Every detail—from architecture to deployment—is handled with rigor, ensuring clarity, performance, and long-term maintainability.
We design and deliver systems that are technically rigorous and commercially impactful.
We embed AI into core workflows, decision-making, and product architecture to create durable advantage.
We translate complex opportunities into elegant, production-ready solutions.
We build with precision, scalability, and a clear understanding of business context.
Built for impact
We combine deep engineering expertise with AI to deliver solutions that are practical, scalable, and grounded in real business outcomes.
AI that actually ships
We don’t just prototype—we design and deploy production-ready AI systems that integrate with your existing stack.
Measurable advantage
Our work is defined by outcomes: faster operations, smarter decisions, and capabilities that compound over time.
Transforming Ideas into Intelligent Solutions
Software consultant specializing in AI/ML integration, custom model development, and intelligent automation for forward-thinking businesses.
"We are better than AI. We are human."
Real thinking.
Real people.
Crafted, not generated.
Invented, not imitated.
The future needs
more humanity.
Not less.
AI can replicate patterns.
Humans create meaning.
e9e
Latest Articles
All Articles
Configure Bundler for Access to Private Repositories
What worked for me is using ENV VARs:
gem 'iron_warbler', :git => "https://piousbox:#{ENV['GITHUB_TOKEN']}@github.com/wasyaco/iron_warbler.git", :branch => '0.1.0'
What didn't but should have worked is reproduced below: You can add authentication information to it like this:
Ruby on Rails: allow parameters to have “.” (dot)
By default, dot in rails router is used to separate the format from the rest of the url. To allow dot in a parameter, override the constraint. The below example allows any character except slash:
get "/:user/contributions" => 'users#contributions', :constraints => { :user => /[^\/]+/ }
Ruby on Rails naming conventions
Ruby on Rails, often referred to as Rails, follows a set of naming conventions to maintain consistency and readability in code. I generally like RoR conventions and follow them. Here's a summary of some key naming conventions in Ruby on Rails:
Class Names: Class names in Rails are typically in CamelCase (also known as PascalCase), starting with an uppercase letter. For example, User, ProductCategory, or OrderDetail.
Some notes on naming conventions
Singular or plural?
This can be a much larger conversation, really. In the Ruby on Rails (RoR) framework, what is plural and what is singular is very specific.
I'd like to additionally note, that since I apply Occam's Razor to everything, and simplify everything, then generally speaking my names are singular, because plularily can be removed. This helps me easier find names in the future.