MHB Data Science and Systems Integration Blog Post

AI Thread Summary
The discussion emphasizes the importance of data handling and the challenges faced by experts in maintaining a fresh perspective when analyzing data. It highlights the difficulty of empathizing with those less knowledgeable due to the internal assumptions formed through experience. The conversation advocates for a bottom-up approach in system design, arguing that while some guidance is beneficial, excessive direction can lead to user frustration. There is a debate about the merits of top-down versus bottom-up design, with one participant questioning whether a top-down approach can be valid if it involves using the same data for both hypothesis generation and testing. The need for a balance in documentation that is both concise and adequate is also raised, underscoring the complexities of effective communication in data-driven environments.
Ackbach
Gold Member
MHB
Messages
4,148
Reaction score
93
Really excited about this blog post by yours truly. Wineman Technology is going places!
 
Technology news on Phys.org
Interesting article!

I work with large amounts of data every day and would consider myself an expert in the field when considering the whole continuum of "Can't use a computer" to "Coding at Google". I grab data, clean it, join it, model it, and present it.

That is important to your point, because what I lose in my years of training is the ability to see data and a problem with new eyes. Once you know something, you can try to empathize with the mind of someone who doesn't know it but it is quite difficult. Even worse, you can be very unaware of the facts that you internally assume everyone must know yet they don't.

So I fully agree with you that systems benefit from building bottom-up, not top-down. Some guidance is helpful but too much will leave the end user clueless and frustrated.
 
Jameson said:
Interesting article!

I work with large amounts of data every day and would consider myself an expert in the field when considering the whole continuum of "Can't use a computer" to "Coding at Google". I grab data, clean it, join it, model it, and present it.

That is important to your point, because what I lose in my years of training is the ability to see data and a problem with new eyes. Once you know something, you can try to empathize with the mind of someone who doesn't know it but it is quite difficult.

Yeah, yeah. Total nerd. I get it. ;)

Jameson said:
Even worse, you can be very unaware of the facts that you internally assume everyone must know yet they don't.

So I fully agree with you that systems benefit from building bottom-up, not top-down.

I'm a hair puzzled. I thought I was advocating for a top-down design approach, which is simply what a typical statistics textbook will tell you. If you have an hypothesis at hand (big question, in the parlance of my blog post), then you can design the system that generates the data that, once analyzed, answers the hypothesis or question. Isn't that a top-down design approach? It is considered "cheating", is it not, to use the same data to generate an hypothesis as well as to test it?

Jameson said:
Some guidance is helpful but too much will leave the end user clueless and frustrated.

I'm very curious what you mean here. Are you talking about achieving that difficult-to-achieve balance in documentation between conciseness and adequacy?

Cheers!

By the way, I LOVE THE QUOTE-BREAKER!
 
Dear Peeps I have posted a few questions about programing on this sectio of the PF forum. I want to ask you veterans how you folks learn program in assembly and about computer architecture for the x86 family. In addition to finish learning C, I am also reading the book From bits to Gates to C and Beyond. In the book, it uses the mini LC3 assembly language. I also have books on assembly programming and computer architecture. The few famous ones i have are Computer Organization and...
I have a quick questions. I am going through a book on C programming on my own. Afterwards, I plan to go through something call data structures and algorithms on my own also in C. I also need to learn C++, Matlab and for personal interest Haskell. For the two topic of data structures and algorithms, I understand there are standard ones across all programming languages. After learning it through C, what would be the biggest issue when trying to implement the same data...
Back
Top