taylorcooney
OpenUnit provides management and payments software for the +$50B self-storage industry. I’m looking for people who (still!) want to work with Ruby, and who are at least a little skeptical of JavaScript SPAs. There have been some great updates lately to the Ruby on Rails ecosystem with the introduction of Hotwire.
Remote only, but US/Canada based is easiest for me to work with.
We’ve raised a small seed round, with notable investors from the self-storage industry. You’ll get full transparency of the company’s cap table and balance sheet, and you'll work alongside a small engineering team that consists of three people.
You’ll spend basically all of your time building and very little of it in synchronous meetings.
Contact via email in profile, or check out our job posting[1]
Jump to the 7d view
OpenUnit (YC W20) Is Hiring a Senior Ruby on Rails Engineer
OpenUnit provides management and payments software for the +$50B self-storage industry.
I’m looking for people who (still!) want to work with Ruby, and who are at least a little skeptical of JavaScript SPAs. There have been some great updates lately to the Rails ecosystem with the introduction of Hotwire.
Remote only, but US/Canada based is easiest for me to work with.
We’ve raised a small seed round, with notable investors from the self-storage industry. You’ll get full transparency of the company’s cap table and balance sheet, and you'll work alongside a small engineering team that consists of two people.
You’ll spend basically all of your time building and very little of it in synchronous meetings.
Contact via email in profile, or check out our job posting[1]
OpenUnit (YC W20) Is Hiring a Ruby on Rails Engineer
The latter is where real difficulty and liability lies; an event, such as a rental payment, triggers a series of transactions that must be financially sound and sufficient for meeting the expectations of an audit. There were a few other considerations but that really is the core framework. Where the real work begins is implementing the triggers, or events (like I mentioned above), that sets off a set of entries and making those financially sound. I've been able to achieve some basic rules exclusively for the self-storage space whose types of business transactions are very similar, but the truth of this can only be revealed by third party auditors. It leads me to believe that it's very difficult, if not impossible, to come up with a universal system for all businesses and industries since the events that trigger entries are specific to each system.
Happy to riff on this a little more if you're interested!
[1]: https://www.mathstat.dal.ca/~selinger/accounting/tutorial.ht...
[2]: http://www.austintek.com/gnucash/ncsa-gnucash-talk.html
[3]: https://docs.google.com/document/d/100tGcA4blh6KSXPRGCZpUlyx...
[4]: https://medium.com/@RobertKhou/double-entry-accounting-in-a-...
Launch HN: OpenUnit (YC W20) – Software for managing self-storage facilities
Hi HN,I’m Taylor Cooney. My co-founder Lucas Playford and I are launching (https://www.openunit.com) - software for managing self-storage facilities.Lucas and I met 5 years ago at a startup in Toronto. Since leaving the startup, we’ve been looking for ways to “get the band back together” ever since. I would hack on side projects, such as an order-ahead food app and applicant tracking system for...
The acts_as_tenant gem might be what you’re looking for:
> This gem was born out of our own need for a fail-safe and out-of-the-way manner to add multi-tenancy to our Rails app through a shared database strategy, that integrates (near) seamless with Rails.
My recommended configuration to achieve this is to simply add a `tenant_id` column (or `customer_id` column, etc) on every object that belongs to a tenant, and backfilling your existing data to have this column set correctly. When a new account signs up, not a lot happens under-the-hood; you can create a row in the main table with the new account, do some initial provisioning for billing and such, and not much else. Being a multi-tenant platform you want to keep the cost really low of signing up new accounts. The easiest way to run a typical SQL query in a distributed system without restrictions is to always access data scoped by the tenant. You can specify both the tenant_id and an object’s own ID for queries in your controller, so the coordinator can locate your data quickly. The tenant_id should always be included, even when you can locate an object using its own object_id.
Creating an account is to access more free content in "the community". Thoughts?