I'm currently delivering a data migration for a corporate acquisition. Got a few devs on my team, and I'm quite lucky with the ones I do have.
What I'm not so lucky is with the quality of the data in the source system. Or rather, the way the data is structured in the source system.
I have to convert the pile of poo records into workflow records to go into a very complex workflow system. It is a fools mission to even attempt to map it as the source system doesn't have any discernible workflow, and the flags that are stored against a record vary over time as and when the company "tried stuff out". It is a cluster**** of gargantuan proportions.
So, Suity 2.0 now takes time out to chill, focus and think about stuff rather than beating myself up until I burn out and fade away. So during one of my personal focus groups I had the idea of using a fuzzy logic approach. Don't get me wrong, not in terms of pattern matching per se, or Soundex queries, but in terms of trying to generally work out the status of a case.
That is to say I can use certain markers such as "this letter template was used to send a letter to the client", or "The supplier called to chase payment". Using these "soft markers" and applying fuzzy logic confidence and biases I can get the computer to "think" me an outcome to tell me where to pop it in the workflow.
So we just had the big meet up with the PM to show off my approach. I was expecting spellbound attention, lavishing praise upon my giant and oh so clever noggin. In fact one of my devs wrote a case file viewer (about half a days work) which the PM was thrilled with.
The fuzzy logic stuff was met with stifled yawns and a few shrugs, even though I have cracked the one insurmountable problem we had.
Just a gentle reminder from the contacting God that you're just a day rate. Worth remembering the next time a contract is stressing you out. "Meet success and failure and treat those two imposters just the same"....
What I'm not so lucky is with the quality of the data in the source system. Or rather, the way the data is structured in the source system.
I have to convert the pile of poo records into workflow records to go into a very complex workflow system. It is a fools mission to even attempt to map it as the source system doesn't have any discernible workflow, and the flags that are stored against a record vary over time as and when the company "tried stuff out". It is a cluster**** of gargantuan proportions.
So, Suity 2.0 now takes time out to chill, focus and think about stuff rather than beating myself up until I burn out and fade away. So during one of my personal focus groups I had the idea of using a fuzzy logic approach. Don't get me wrong, not in terms of pattern matching per se, or Soundex queries, but in terms of trying to generally work out the status of a case.
That is to say I can use certain markers such as "this letter template was used to send a letter to the client", or "The supplier called to chase payment". Using these "soft markers" and applying fuzzy logic confidence and biases I can get the computer to "think" me an outcome to tell me where to pop it in the workflow.
So we just had the big meet up with the PM to show off my approach. I was expecting spellbound attention, lavishing praise upon my giant and oh so clever noggin. In fact one of my devs wrote a case file viewer (about half a days work) which the PM was thrilled with.
The fuzzy logic stuff was met with stifled yawns and a few shrugs, even though I have cracked the one insurmountable problem we had.
Just a gentle reminder from the contacting God that you're just a day rate. Worth remembering the next time a contract is stressing you out. "Meet success and failure and treat those two imposters just the same"....
Comment