xsevensinzx (10/12/2015)
Let me start of by saying that I am one of those accidental DBA-types who kind of jumped head first into the data. I'm still very much learning the ropes and currently have a pretty large project in my hands.That being said, I'm doing a bit of redesigning as of lately due to the growth of my data. Through this process, I've been doing a lot of detailed planning on architecture of a new solution that will include a much needed redesign of all areas of the existing data warehouse solution.
I feel very confident and proud of what I've accomplished thus far with my plans. However, I need feedback. I need to understand the strengths and weaknesses of what I'm about to roll out. Thus, I've been seeking feedback from other like-minded data gurus in the organization to get their weigh in.
Due to that, I've received some kind of googly eyes when I ask about feedback. As if I'm second guessing myself like it's a bad thing. Like I'm supposed to be this all-knowing data wizard who should know how to structure every chaotic byte into a magnificent symphony of data blissfulness. :hehe:
So, I wanted to prod the community. Is seeking architecture design feedback a bad thing or a sign of weakness in itself? I personally love feedback. I actually like people poking holes in my work so I can make it better.
It depends... Forums tend to be a great place to ask specific questions. So if you have a specific design challenge and you aren't 100% which direction you want to go or you want to have a discussions about the pros & cons of alternate design ideas, then yes, forums are the perfect place to seek advise and feedback.
If, on the other hand, you're want someone to validate your entire database schema... That's what paid consultants are for. Most people who answer questions on a forum either genuinely like helping other people and/or enjoy solving puzzles... but... very few, if any, want to do your job for you unless there is a pay check to go along with it.
Just my 2 cents.