ruby-science VS missing-semester

So, bigger is worse, but how big is bad? At what number should you take action? Thoughtbot's Ruby Science book suggests a method is long or complex with a flog score above 10. It also posits that a class is long or complex with a flog score above 50.

Ruby Science - it's a free book by thoughtbot. It might be the most short term beneficial thing honestly. It just points out all of these various practical patterns you can immediate use to increase code quality.

I think you would appreciate Ruby Science. I love this book, it's extremely practical.

Well, if you're programming in Ruby, a great place to start is the Ruby Science book by ThoughtBot. It's a bottom-up approach to improving your code by identifying code smells and applying OO principles to fix them. Identifying smells in your own code will lead you to the OO principles that you need to learn to build your OO skills.

Read Ruby science to learn about code smells and good architecture.

It's a bit more advanced, but I like Ruby Science by thoughtbot.

Check out Ruby Science by Thoughtbot which I found useful at your stage.

Code smells. Ruby science is a good one for Ruby.

Currnetly reading ruby science. 200+ page guide on code smells and solutions.

This book is old but it's still very relevant https://github.com/thoughtbot/ruby-science. Also check out thoughtbot's blog and www.gorails.com

The missing semester of your cs education

https://missing.csail.mit.edu/

You mentioned having issues with accessory concepts so perhaps this might help: https://missing.csail.mit.edu/. There's also a chapter on git

https://missing.csail.mit.edu/ is a good way to pass the Dec-Jan break if you want to prep for CS2030S + some more general stuff.

Reflecting a little bit more I don't think it was replit's fault, per-say. But that change should have been made together with a larger adjustment to the program. Like adding a class/unit in the style of [the missing semester](https://missing.csail.mit.edu/) to make sure people came away with a good range of intuitions.

From MJD's post: I think CS curricula should have a class that focuses specifically on these issues, on the matter of how do you actually write software?

But they never do.

FWIW, MIT's "The Missing Semester of Your CS Education" attempts to deal with this lack, though, even there, it's an unofficial course taught between terms, during MIT's IAP -- Independent Activities Period[1] -- and not an actual CS course.

[0] https://missing.csail.mit.edu/

[1] https://en.wikipedia.org/wiki/Traditions_and_student_activit...

Link to the "missing semester of your CS degree" course by MIT.

Rightly called The Missing Semester (of Your CS Education), this class from MIT will teach you how to use some of the tools that are fundamental to the software engineering ecosystem. From shell scripting to the fundamentals of information security—spanning around 12 lectures—you can add a bunch of practical skills to your toolbox.