docs: added note on snoop to dev cycle docs

Author: arctic-hen7

docs/next/en-US/first-app/dev-cycle.md

@@ -15,6 +15,8 @@ Importantly, any time you don't need to be actually seeing the views your app is
 
 Then, when you need to see what your app looks like in a browser, for example when you're styling it, or testing a particular feature, you can use `perseus serve -w`. If you're updating static content (like a `.css` file), rebuilds will be pretty much instant, but updating the Rust code of your app will be a fair bit slower. This is unfortunately a downside of working with Rust web development, but, in return, you get an *extremely* performant site that eliminates whole classes of bugs that run rampant in JS code.
 
+Importantly **if you're doing any kind of logging, you'll need `perseus snoop`**! This series of commands (i.e. `perseus snoop build`, `perseus snoop wasm-build`, and `perseus snoop serve`) will run each of the stages of your app manually, returning all output, whereas the default commands will only show logs if there's an error (meaning those `dbg!` calls will vanish into the ether).
+
 *Note: there is currently ongoing development on the Sycamore side for a system to remove the need for recompilation when you change things in the `view! { .. }` macro, which will dramatically improve performance.*
 
 ## Custom watches