Words of Advice for Young People about roro HOT 27 CLOSED

👍 Brilliant

from roro.

Nice one, Day-V

from roro.

Nice one. I often get asked by junior devs on how to do this and that. So come to think of it, why don't you talk about how to ask a right question / how to google for solution / how to read API?

from roro.

Good point, Trung! That is a skill that has to be learnt by practice, isn't it?

from roro.

Reflecting on some systems I've seen implemented by juniors, I'd like to see (or deliver) "Why I like to use reference tables". I can think of at least five good reasons to create a table for an enumeration, even though it might never get changed.

from roro.

Excellent idea, Clifford. Please do enumerate your reasons... :-)

Off the top of my head:

• Able to add/remove enumerations without changing code/redeploying
• Can change spelling without breaking relationships
• Simple to localize

from roro.

Another idea: Why juniors should give presentations, even if they think it's trivial.

• It's good practice for public speaking, which is a skill that improves only with practice.
• What may seem trivial to you, may well save someone else hours/days/weeks of banging their head against a wall.
• No-one knows everything. There is so much to learn, there is great value in having something useful pointed out to you.

from roro.

In addition to ease of extension and change, my main reasons are:

• Can use foreign key enforcement
• Can use either surrogates (numeric ids) or strings for the value (if suitable)
• Can add explanatory text to populate pick lists or help bubbles

I tend to have all three of the stored id value, the short pick-list string, and the extended text.

Actually "simple to localize" isn't that simple, if you want multiple languages in the same deployment; but at least it gives you a place to hang the language tables from, or a stable lookup key for Rails-style translations.

Typically a quarter to a third of the tables in my database designs are reference tables.

from roro.

👍

from roro.

This suggestion might not have much to do with coding skills or best practices, perhaps a talk on how budding web developers could land themselves a junior role and how companies could embrace a junior with little or no prior web development knowledge but have gone through courses/railsgirls/rails girls summer of code/ to increase employability.

from roro.

Sounds like a talk that @mattallen gave a year or so ago. Is it time for a reprise?

On Thu, Nov 13, 2014 at 8:58 AM, yiingshan [email protected]
wrote:

This suggestion might not have much to do with coding skills or best practices, perhaps a talk on how budding web developers could land themselves a junior role and how companies could embrace a junior with little or no prior web development knowledge but have gone through courses/railsgirls/rails girls summer of code/ to increase employability.

Reply to this email directly or view it on GitHub:
#15 (comment)

from roro.

How to structure (Rails) relationships to avoid too deep nesting ;)

from roro.

Great suggestion, Liam.

from roro.

deployment onto VM servers with Rails is really painful. I've been using Passenger and Apache, I've been seeing bugs everywhere. Are there good tips on how to do that?

from roro.

Please, no need to CC me, I’m on the roro list already.

On 4 Dec 2014, at 7:22 pm, Peter He [email protected] wrote:

deployment onto VM servers with Rails is really painful. I've been using Passenger and Apache, I've been seeing bugs everywhere. Are there good tips on how to do that?

—
Reply to this email directly or view it on GitHub.

from roro.

Thanks everyone, these are all great. For everyone who has put in a suggestion can you create a new issue (https://github.com/rails-oceania/roro/issues/new), then we can start to work out who can present or talk to each of the these.

from roro.

@hexinpeter That sounds like an entire talk suggestion, not something I can cover quickly.

But, my initial answer to that would be "Don't use Passenger and Apache". Seriously, that's 5+ year old technology that nobody uses any more. Most people use nginx + unicorn/puma/thin.

But, if you're a beginner, why not just deploy to Heroku?

from roro.

How to read Heroku logs is another suggestion.

from roro.

Another: using ActiveRecord association queries for more readable code. e.g:

# bad
comments = Comment.where(:post_id => @post.id).all

# good
comments = @post.comments.all

from roro.

Why you should be using Github-Flavored Markdown.

from roro.

How to fork a repo on GitHub, fix an issue, and send a Pull-Request.

from roro.

Why you should adopt good code style practices. (consistent indenting, naming conventions, meaningful comments)

from roro.

Why beginners need to do more talks at RORO. (if only for getting feedback from Seniors).

from roro.

Why use helper methods in views.

from roro.

Why have thin controller methods?

from roro.

Wow, would really love to go for the meetup now. Sadly that I am in Melbourne. Very interested in hearing about "How to read Heroku logs" and "How to fork a repo on GitHub, fix an issue, and send a Pull-Request."

from roro.

Great talk @suranyami with a lot of info. Looking forward to the next ;) Shipped.

from roro.