the “snack game” by the window
When I go to the community hospital with colleage, he tells me a weird thing.
Well, someday he find that by the window there is a piece of candy outside the hospital window. Out of curiosity, he places another candy.
Then the next time he goes there, he find that the candy was added by one.
He tells me that there must be a child(boy). but I wonder - it may also be a girl, and adults also do weird things sometimes.
Also, there is something deep here - the “bet” and “social trust”. well, if both are childs, one can think another be betting - or show wealth/ affection? If there is good intentions between them.
But one can also take all candy. then he just doubles his candy. but another people might just takes them away. and both are suspecting each other taking them all.
well, I also think that in the urban area, the idea of the “secret place” is transforming. people always find them. But it requires a “heart”.
I also think back about a fantasy novel - that in the end world “God loses heart, monster loses blood, fairy loses spirit”. We need an watchful eye for the life.
the conflict with colleage
that might not be worthy to record.
basically, we are faking records on the system.
a particular types of them requires a record in the system, after 10 days of exam date.
In the agile development, I quickly make the program and delivered it. well, the onsite operator tells me that - “just a simple one is ok”, that she will fill the date, which was calculated from 10 days after exam.
But according to requirement, we need two records for people over 80. one after the exam, another is 6 months after the exam, type “SMS”. I make the automatic one and delivered it. Also, although they already have a “record deletion” program, I also included one myself.
I think I will need to explain some background here.
I’m currently in an RPA company - that is, automating record creation/delection/QC etc in the medical system. The company was boomed with the rise of AI, that enables them to write selenium(a browser driver) program that do the automation.
Selenium scripts are tricky and error-proven - because they are involved with element clicking, page load, and small change in the page or network delay will cause them to fail. So running it for a long time requires attention.
So as a business decision, we hire female “operators” to operate them. (Why female? because hospital doctors are usually female, and why doctors and nurses are female is a common society problem).
because of these are essentially “scripts” - that has no tech in there, just find element and click - they are easy to write, especially with the help of AI. So they made the “speed” of writing such scripts a evaluation of one’s performance, and one get boost for how many scripts he has written.
Also, because of the previous described problems with such scripts, it was clear that when something get wrong, it’s always the program’s fault.
But as logic complicates and contracted hospitals booms, things quickly goes out of control. And I was hired.
I added unit testing and created a framework, and transitioned many programs to requests based ones. But I also get a lot of misunderstanding, because they don’t undertand this, and always tell me to “seperate” them and “write easier code”.
Well, I might said too much, and now I’m a little excited/angry. I might continue sometime.