Wolf's Corner
About the Author
Karaoke enthusiast. Board game haver. Problem eraser. Cyclophile. Collaborative contributor. Certified Musk disliker. Certified New York City liker.
Trans rights are human rights.
Any opinions stated here represent the opinions of your cats. If you disagree, you can bring it up with your local felines.
Posts
- A better Phlex layout pattern
- How to drop 1Password for KeepassXC
- A better build order
- Symlink as an Organizational Tool
- Software Calcification
- Quality vs Speed
- Mental Sharecropping
- Cross modal join objects
- A Case for Rails Engines
- Wash Your Hands
- The world’s most accurate software analogy
- Kamal, Rails, and Ruby version
- Fixing a Bug in Rails Via Best Practices
- Just-In-Time Grooming
- ID as a form of primitive obsession
- LLM vs Dotcom Bubbles
- FactoryGirl associations without callbacks
Cool Code Collection
| Project | Details | Links | Art |
|---|---|---|---|
| Rails Engines as First Class Citizens Project | Rails Engines suck because Rails has so many hard-coded references to ActiveRecord::Base. With work we could remove the hard-coded references and allow Rails Engines to become fully isolated from everything else. This would mean they could own their configs, own their database connections, and own their migrations. This will provide missing waypoints between a monolith and distributed services, allowing much easier integration testing and iteration on design. | ||
| Pry-Rails | Utilized Docker to test Pry-Rails against a matrix of Ruby and Rails versions. | pry-rails/pull/135 | |
| dotenv implementation | A 9 line dotenv implementation I made. It does the standard dotenv things and also does parent directory walk. Useful for having multiple projects or apps for a single organization. My use case was to have a work directory containing .env files with common values and also work repositories. | de |