A frequent interaction with research software clients:
Client: Why are we building this study software this more convoluted way?
Me: You asked me to solve problem X. This solves problem X in the most complete and robust way I can manage.
Client: But we only need part of X for our pilot.
Me: And you'll need ALL of X when your study goes from pilot to full deployment. And you won't have the patience for me to pause the project to rebuild the system between those phases.
@aleen @donmelton J is just preparing you … so buckle up.
You’re going to go to IKEA and then he is STILL going to mock it up with cardboard at home to see if he likes how it looks, feels in the space, etc.
#NotMyFirstRodeo
My spidey senses told me the dog was up to no good. She was on the other side of the yard so I couldn't see her very well but when I looked over at her she nonchalantly laid down. Having had a kid who was often up to no good, I walked over to her and she sat up, wouldn't make eye contact and tried to pretend she was observing birds. She was also trying to lick the dirt off her nose like I was born yesterday.
I've got a stack of good software engineering books, along with 30+ years experience, that could invalidate this campaign.
I've seen this idiocy many times before. It's standard corporate playbook stuff for trying to manage knowledge workers with manufacturing lessons learned.
#NotMyFirstRodeo
#DumbAllOver