What's your preference? One (quite) long review publication, or a shorter one along with some discussions here?

Hi  obones ,

Well, much like what you and others have written, I also prefer a series of shorter, interconnected blog posts.

I think it also depends on the complexity of the project.
For instance, whether you're dealing with a measuring instrument, a computer, or "smaller" devices—the description and explanation will vary accordingly.
Another thing I do is read the reviews by other participants - after all, we’re a team; that’s exactly how I view it - and that helps me decide where to focus my own review.
Because you don't have to copy everything exactly; you can supplement or expand on others with your own contribution.

For example, I'm now allowed to participate in the road test of the Arduino Ventuno Q. Thank you very much Owain and Christopher for that opportunity!

Well, I usually write everything in German first, then translate it into English.
On top of that, as an electronics specialist, I face the challenge of mastering the software as quickly as possible.
I’m learning and doing everything through self-study, building things up in my own lab.
So, in a way, it’s like learning a third language.
-> I’m very familiar with standard Arduinos (and the Raspberry Pi) - the smaller controllers - but the Ventuno Q is a whole different ball game for me.
That naturally shapes the way I write my review.
So, how much should I actually write?!?!?! 

In the past, I used to write entire user manuals and technical descriptions—documents the size of brochures.
...Oops... as you can see from all the words above... "once I get started, where does it end...?" 

So, I prefer keeping it shorter—highlighting the key aspects of my project—and that works well.

I wish you, and all the other road testers, all the best for your review.

Best Regards
Gerald

---

Hi  obones ,

Well, much like what you and others have written, I also prefer a series of shorter, interconnected blog posts.

I think it also depends on the complexity of the project.
For instance, whether you're dealing with a measuring instrument, a computer, or "smaller" devices—the description and explanation will vary accordingly.
Another thing I do is read the reviews by other participants - after all, we’re a team; that’s exactly how I view it - and that helps me decide where to focus my own review.
Because you don't have to copy everything exactly; you can supplement or expand on others with your own contribution.

For example, I'm now allowed to participate in the road test of the Arduino Ventuno Q. Thank you very much Owain and Christopher for that opportunity!

Well, I usually write everything in German first, then translate it into English.
On top of that, as an electronics specialist, I face the challenge of mastering the software as quickly as possible.
I’m learning and doing everything through self-study, building things up in my own lab.
So, in a way, it’s like learning a third language.
-> I’m very familiar with standard Arduinos (and the Raspberry Pi) - the smaller controllers - but the Ventuno Q is a whole different ball game for me.
That naturally shapes the way I write my review.
So, how much should I actually write?!?!?! 

In the past, I used to write entire user manuals and technical descriptions—documents the size of brochures.
...Oops... as you can see from all the words above... "once I get started, where does it end...?" 

So, I prefer keeping it shorter—highlighting the key aspects of my project—and that works well.

I wish you, and all the other road testers, all the best for your review.

Best Regards
Gerald

---