Josh Smith JoshDevHub

I cloned your project and poked around. It's pretty good! I am going to write one thing that isn't fully in the curriculum (yet) but that you probably want to be aware of.

Some terms

First some terms:

Authentication: Figuring out who a user is.
Authorization: I know who the user is (using authentication), and now I need to consider what they're allowed to do.

Your app of course has authentication implemented through devise. Another thing you'll want to consider going forward though is that 2nd thing: what are the current user's permissions?

Param Manipulation

So let's walk through a quick scenario on your site. I'm signed in as the user "joshodin" and I have one upcoming event (one that I'm hosting). Now there's another user named "usern2" who has a private event set up. I shouldn't be able to see or interact with this event. So far, so good.

Now let me click on my event "Event Title". I'm taken to a page where I can take a variety of actions. I can invite people, edit the event, cancel the event, etc. Another thing I can do is declare that I'd like to attend this event. Let's examine this "Attend Event" button in devtools:

Basic LazyVim Setup with Ruby/Rails

A very basic setup for ruby/rails development using LazyVim

Prerequisites

First, you'll of course need neovim. I personally just use the stable release over nightly just because I dislike when things randomly break, and I have to stop working to deal with it. But do whatever you like.

Probably a good idea to start it and run :checkhealth to make sure everything works before proceeding.

Don't rely on form information for the current user

So here's the general setup I have. I am currently signed in as second_user. first_user has made a single post with the title "Hello" and the body "This is a post!"

Now I'm going to visit "New Post" and make a post. Keep in mind that anything you have in the page markup is observable and editable by the end user. Let me open up devtools on this new page.

List of Lessons touched by adding WSL2

Installations Overview: The language on the section regarding Windows support and OS options will have to be updated
Foundations Installations: Will need to include WSL2 specific installation instructions
Text Editors: Will have to show how to use VSCode with WSL2. Introduce WSL-remote extension
Command Line Basics: Using the terminal with WSL2. This could just be about using the default Ubuntu terminal that comes with WSL2 Ubuntu, or it could include instructions on using WSL2 via the Windows Terminal.

At some point, it'll need to be communicated how to deal with filesystem difference and in particular, how to move files from Windows to WSL2's filesystem. This could be introduce

Overview

So this will mostly be about the things I think can be improved, but I did want to point out that I think there are some cool ideas here, I just don't talk about them much in this review because it'd take way more writing. The Evaluation class is a really neat idea that I think fits with your code very well.

Also obviously a huge accomplishment in general to complete this, and no one's design is perfect (least of all my own). With that said, I'll jump right in

Functionality

Other than the bugs you mentioned, everything seems smooth save this one problem for castling to the queen side, where the participating rook isn't moved. I didn't immediately notice any other bugs going on, which is great!

	// solution to problem #6 in recursive exercises
	function contains(object, searchValue) {
	// because `null` has a typof "object", we have to explicitly check
	// to prevent trying to access `null`'s values (which don't exist)
	if (typeof object !== "object" \|\| object === null) {
	return object === searchValue;
	}

	for (const value of Object.values(object)) {
	// An important problem in the code quiz solution is that `return contains()` will only

	require "observer"

	class Board
	include Observable

	def initialize
	@grid = [" "] * 9
	end

	def to_s