Thing is, some of the blueprints we will use for the final production as well. And I personally know well what I can and cannot tamper with.
But lets say a college taps into my public variable (assuming it cant be private due to child class access) and sets it manually and the entire blueprint goes into a broken state because of it.
Its not really great.
Also, we have just recently started learning the engine. And we all have a fair understanding of c++.
It just is much quicker to check if the data flow etc works in blueprints.
And sometimes the budget just tells us that we simply cannot take the time to make it into c++ after all.