jmmastey / level_up Goto Github PK

The factory_girl instances take too long.

If you don't complete any activities for maybe a day or two, provide some way to email the admin.

Right now I need to be involved with every deployment, including changes to corporate content. @bwthomas wants the ability to deploy without me.

Not sure how to structure this. Currently, nonpublic content is added as Rails engines and included to deployment separately via GemFury. Adding a way for them to deploy (while keeping content non-public) might involve:

1. Allowing corps access to the GemFury depot. I think this is problematic for potentially nonpublic information.
2. Deployment from Travis on successful master runs. I need to see if this would allow for the private configuration. Could we use ENV vars on Heroku for this? It would entail a less-open policy on who has commit bit.

To see who's falling behind, create a chart of people's completion progress over time.

Two-column card format for courses will be more attractive anyway.

In the capybara part of the testing course, it brings up trying out a different driver for a game_catalog exercise. Except we never did one. What is this referring to?

Per feedback: 'The article provided describes the benefits of TDD in making good code, but it doesn't really provide an example of how the opposite perspective could lead to worse code. I found myself trying to guess too much on that question, but a resource with examples on how "violating this rule would cause you to write worse code" would be very valuable.'

Yep.

So I don't spam anyone. Let users remove themselves from all mailings.

Since we have Github info and possibly integration, use that info to create issues directly.

site performance is laggy, add some basic caching and solve a few n+1 queries.

Move completion stats to multiply by course difficulty

Send an email if you haven't registered for a course after signing up after a few days.

No idea how to do deployment with proprietary content via Heroku, but find a way to do so and grab old spreadsheet content for Enova-specific content.

Need to:

1. Get gandi.net cert working properly.
2. Configure domain CNAME. Looks like no support for apex domain ALIAS, so redirect apex to www.
3. Install cert on Heroku.
4. Update all references.
5. Send email to users.
6. Update heroku config to reflect new URLs.
7. Redirect from old domain to new one?
8. Update github to reference new URLs.

We'd discussed this a long time ago. This is a natural specialization for some Rails engineers. Is there someone who wants this feature enough to develop it?

https://www.owasp.org/images/5/58/OWASP_ASVS_Version_2.pdf

@djkotowski wants more credit for finishing :D

At the top of a module, display a difficulty rating to help set people's expectations. Later, switch "completion" model to sum(exercises * difficulty) for completion percentage. Cache the fuck out of that one...

Almost feels like cheating: https://github.com/flyerhzm/bullet

Automatically detects N+1 problems. It's not perfect, and I've gotten a few false positives, but it really helped nip things in the bud.

It's also extremely annoying to add to an existing app so it might be interesting to have an entire exercise to shut it up.

Move dino catalog after arrowhead and robot name. That way, the user has already learned some of those idioms.

Bounce the feedback tab maybe the first time you reload a page per day

Even worse than sudo, according to dhall.

Make the little fucker move around a bit, evoke some emotion, change colors. Still not very noticeable.

If a course isn't published but you are enrolled in it (likely for proprietary courses), you can't do anything with it. maybe limit view of proprietary courses but publish them instead?

Context + Resources + Verification is important.
Help people believe this is a real website.

users can see each others' completion stats, which... y'know... is a bad idea.

probably the user page should be segmented by your current org. unless you're an admin.

Hey Joe,

What are your thoughts about the Github style guide: https://github.com/styleguide/ruby

I was thinking of submitting a pull request for Level 2. I think it is a great guide as it gives good examples. While I am not in complete agreement about everything, such as the Hash syntax, it does cover some key points:

• Exception handling
• The ||= operator
• Keyword arguments

I think it is pretty concise, contains very practical information and is pretty much on the money. I'll also toss this to @djkotowski for his thoughts.

If you like it, I'll submit a PR.

Paul

The link in line 160 of _linux.html.haml is the same as the link used in the previous section, found on line 149.

The link goes to an O'Riley reference site, but should be directing the user to a Zenoss demo video.

Per Donnie, the current one sucks as either an overview or an explanation of why it's dangerous.

When a user completes an assignment, offer them a link to give feedback. "Sweet! Leave feedback?"

My email links to courses/7, which returns an error page, instead of a redirect, or a page to indicate I am not logged in.

Send an email if you haven't completed any activities in a week.

Help people - especially apprentice-type people - to get started on LevelUp. Include how to use and how to study well.

I cannot figure out how to run tests for levelup. Can you add it to the README.md?
I have tried bundle exec rspec spec and bundle exec rake test
I am trying to remove a broken link but I don't want to break your tests.

Move to course completion over category completion. Fix orphans and widows for updates.

You can probably enumerate all the private content by "completing" it by a skill ID.

1. Probably move completion over to a skill handle rather than ID.
2. Probably use current_user.courses.skills, but I'm not sure that works.

We just had our first real Ruby training in Green Bay a month or so ago. I'm now looking for something to continue the learning, and I think LevelUp would be great.

/users is a great start (though it's unclear how to set a user's organization other than via the console) and there's likely a lot more data that would be useful to support the mentor/mentee relationship.

I think there's some gaps in my understanding of how the workflow should work for a group, so maybe some documentation on that would help as well.

@jmmastey mentioned he had some thoughts and this would be a good place to start, any features that will be beneficial to the global codebase I'd be potentially looking at submitting pull requests for.

For the benefit we get from it, interactor just includes too much extra stuff in the Gemfile. The basic functionality of interactors should be trivial to replace either with a locally developed class or using just PORO objects.

Investigating whether it also makes sense to remove any ActiveRecord specific code from those objects. Combined with #84 this would allow us not to load Rails at all for interactor specs.

Right now ENV is a bit opaque and annoying. Make keys default to some not-dumb status if not present.

It used to be easy to read. The current thing doesn't have enough visual differentiation between rows.

Help

1. Why is config/initializers/devise.rb not in git ignore? I can add it.
2. If it should not be in git ignore, why is the line, config.secret_key = 'f6a7f92d27a0a5a43bd2b10b1b4c1c56313acd913ed1ab2e35b' not automatically uncommented
   in config/initializers/devise.rb.

This change to the configuration in config/initializers/devise.rb is needed to install it on a new machine. Security reasons?

Level Up is very comprehensive for dev / server / backend work but somewhat lacking for frontend. Some things that would be nice to cover include:

• UI
  • HTML / CSS
  • DOM / jQuery
    • event bubbling
• Javascript
  • this
  • closures
  • prototypes - contrast with class-based and function-based (Crockford style)
  • Callbacks - ajax or node fs
  • Promises