Assessing Data Management


Often, we settle for things that do not work well because we don't want to step back and look at the bigger picture. We don't want to stick our fingers in something that is so daunting to fix. 

Think about the last time you reorganized your attic or if you've let your laundry go too long. It's scary, there's so much to do. You try to ignore it as much as you can, procrastinate any way you can think, but at some time, you'll break down and take care of it. 

Why is this logic for data systems ignored? 

There's an incredible amount of technology and power right at our fingertips. Why are we settling for incredibly poor, archaic solutions? 

Simply, because it's something we can ignore. 

Poor data systems are something we've always had to deal with, so we just keep piling more and more data on top of that, organized the same way. This just creates a giant tangle of poor solutions that are integrated with each other and lean on each other. 

Think if you had to clean your neighbor's attic before you could clean your own. 

Now, couple this with the fear that everyone has of coding. Much of these problems could be solved by basic coding. We can circumvent a lot of these poor systems and create the exact solution we need with some basic automation. 

Introducing: Automation

Let's work on this together. 

We need to step back from our work to assess the situation. It needs some long term fixes, but we can remedy our problems with some minor changes to our own processes. 

Look at your situation; what's there that can be done better? 

If you do something more than one time a day and it's repetitive, there's most likely a way you can automate it. Dissect it, what exactly are you doing? Tackle the problem one piece at a time. 

One piece at a time. 

That's how we fix this. There isn't one giant fix for all the problems we have in data collection, interaction, and automation. We need to start with step one before we can reach step one thousand. 

One piece at a time. 

The way to understand writing code. Don't worry about your end product if you don't have a beginning product yet. There's no need to worry about what your end zone dance will be if you haven't started training for football tryouts yet. 

One line at a time. 

Take the initiative to understand what's driving what you interact with.

Is what you want to do possible or not? Yes, it's possible, but it begins with you learning <!DOCTYPE html>, def statement, $ (function () {, or any other language.

In engineering, we learn that there's about 1000 ways to get to the same solution.

What's yours?