Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore: remove broken link | rails | advanced topics #29080

Merged
merged 1 commit into from
Nov 13, 2024
Merged

chore: remove broken link | rails | advanced topics #29080

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions ruby_on_rails/mailers_advanced_topics/advanced_topics.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -325,8 +325,6 @@

Luckily, Rails has done a pretty good job of following these, so you should have absorbed some good habits just through using it. But you'll want to take a minute and read up on each of them (including the odd-sounding ones) because they're fairly central to all software engineering (and a ripe interview question).

If you're particularly interested in pursuing design patterns, check out the ["Gang of Four" (GoF) Patterns](http://www.blackwasp.co.uk/GofPatterns.aspx).

There's a useful book written on anti-patterns, which can help you clean up your code by identifying bad smells, called [Rails Antipatterns](http://www.amazon.com/Rails-AntiPatterns-Refactoring-Addison-Wesley-Professional/dp/0321604814/) by Tammer Saleh and Chad Pytel.

### I18n: Internationalization
Expand All @@ -347,7 +345,7 @@

</div>

### Conclusion

Check failure on line 348 in ruby_on_rails/mailers_advanced_topics/advanced_topics.md

View workflow job for this annotation

GitHub Actions / Lint lesson files

Required heading structure 

ruby_on_rails/mailers_advanced_topics/advanced_topics.md:348 TOP004/lesson-headings Required heading structure [Expected: h4 heading; Actual: h3 heading] https://github.com/TheOdinProject/curriculum/blob/main/markdownlint/docs/TOP004.md

In this lesson we covered some fairly random and intricate concepts but useful stuff to at least get familiar with, even if you're not going to use it every day. Experience is the real key here -- in the course of building awesome stuff you'll run into the need for all of the things you just learned and it might just save you a lot of time and complexity in your code.

Expand Down
Loading