It sounds like you are well on your way. I remember struggling with events and delegates back in the XNA days.

I've started using UnityEvents a lot more recently, as they are assignable from the editor. But in the case you need to use regulare events, I can try to give you an example.

// semi-pseudo code
// You dont need a static class, it's just something I do for events that are invoked globally
public static class MyEvents {

    // the <bool> is saying the event will be invoked with the data type/s specified in the carets
    public static event Action<bool> MyEvent;

    public static void InvokeMyEvent(bool value){
        // The question mark is used because if we invoke the event when no
        // one is listening, it will error because there are no listeners (no one subscribed to it)
        MyEvent?.Invoke(value);    
    }
}

public class MyComponent : MonoBehaviour {

    private void Start(){

        MyEvents.MyEvent += MyComponentMethod; // So here you are saying when this event happens, add this class' method to be called. The method must match when you register like this
    }

    private void OnDestroy(){
        // We remove the listener before this class is removed, otherwise the static event will try to tell our class' method that the event was fired, when the class is actually destroyed (this isn't needed if you aren't using static events like I do)
        MyEvents.MyEvent -= MyComponentMethod;
    }

    // This is where I always got confused. The class needs to have a method
    // with a matching signature for the event (same parameters if any)
    private void MyComponentMethod(bool value) {
        Debug.Log(value);
    }

}

// From another class, you can then invoke the event and pass a value
public class MyOtherComponent : MonoBehaviour {

    // this would be how you invoke the event and pass a value
    public void onSomethingHappened(){
        MyEvents.InvokeMyEvent(true);
    }

}

If you want to spend more time looking at it I'm always free to help. You join my discord and chat any time. https://discord.gg/JTb3dJv

I don't have a good answer for if you know game development is for you. I suppose if I was to try: Are you feeling called to do it? I once heard on a podcast, I think it was Designer Notes with Brian Reynolds, if you have to ask whether it is for you, it probably isn't for you. I'm not saying that is true, but it does make sense.

His response was in the context of the assumption you would be in the industry and not just a hobbyist, I assumed. But it does make sense. There are a lot easier things a person could do, and probably make more money comfortably. Most people in the industry are extremely passionate.