pdougall1 / ar-models-refactoring

So I’m a big advocate of the perspective that I’m not that different from most people. And that if I’m encountering a thing than a lot of other people are probably have also encountered it, or maybe the will at some point.

This is not a talk about some important new technology, or a great new functional something. It’s about fundamentals, got to have good fundamentals.

I haven’t been programming for decades and haven’t …

I’m attracted to cool new flashy things, that are amazing in the what they fascilitate. Some of them I’ve learned (Rails, Ember, D3) Some of them I haven’t learned yet (Docker), some of the I’m electing not to learn (MongoDB). But I do find that the people that are best at what they do are so good because they have good fundamentals. I think it’s easy to loose track of that. I honestly don’t hear that much talk about it at meetups and work and, well everywhere. I know a lot of people have these things intrained down to their core, such that they don’t have to be think about them, they just are them. But there are many of us that havn’t been working with OO for decades, and it helps to have some fundamentals thrown about so we can know about their importance. This is an attempt at working some of that into the conversation.

### Describe assiciations

* Maybe mess with https://github.com/voormedia/rails-erd
* use enum for roles
  - would introduce some people probably
  - a chance to knock on AR a little :)

### Feature Requests ##### Admin tickets list

1. Admin needs to see all tickets being worked on
2. Filter to only show tickets that are active
3. Filter to only show tickets for projects they are on
4. Augment filter to show all tickets for projects under the company they work for
5. Can revoke access to project for within an operation for a worker

##### Worker tickets list

6. worker needs to see only their own tickets
7. only active tickets
8. only tickets for projects where they are a worker

Will likely need to have project specific roles here