It’s been a month since I entered this work - Python RPA.
The company is still growing. There is a common pattern for communication - do you finished that task? I finished that task! then they just go playing.
But, actually, the work done by them is just half-made. whenever a requirement arrives, or some bug happens, the same process repeats.
As a new employee, I also get some tasks for fixing bug. It’s exactly in this process I know the problem. The code is just copy and paste code; the logic was inconsistant and, no proper error checking. No data model. Whenever some new need arrives, they just create a new project, or copy existing code and start a new project based on that.
Also, the RPA for many clients is similar. However, because the code is copy-pasted, every project has it’s own copy of the same logic, and the reason is “I can change it". But this is just an excuse for inability to make a common logic. Take my group leader for example, he is bad at config reading. And almost all one is bad at environment management and, making a library.
Another co-worker entered the job before me around two or three months. He is doing a project for checking the intergrity of the data. Followed by the copy-and-paste pattern (of course), he is sinking in everyday jobs for fixing bugs, and doing work overtime is a common sight.
Well, back to the topic for fixing bugs. As a new employee, I am naturally not familar with the code. However, I invested on my skill, and I have the help of the top AI tools. I quickly find some fatal bugs in the project. Some feature change or bug fix would require rewrite some part of the project. As I realized this is not sustainable, I start writing a framework.
But this takes time. I starts to slow down or the bug-fix process, and the group leader immediately gets unhappy: “what are you doing in XXX day?” Because I didn’t discuss with him about my work.
Well, I have already realized that he is not good at code.
It’s that event. As a new employee I feel my position is not secured - so I volunteered to take on some new tasks - three minor features bundled together for a project. But then an accident happened - the client requires a complete UI rewrite.
The group leader accepted it immediately - because it’s not him to do the work anymore. And I forget to mention that these tasks are mainly his. And he even promised it will be completed in one week!
Well, it’s also part of my fault - a minor thing happens when I first entered office - the group leader asked some CSS problem on the UI, and I, think myself know some CSS, volunteered for a fix. however, a nearby senior employee quickly helps him find the problem. I feel discouraged; and the take on these tasks can be seen as my reverange for that.
TBD - problem and how I realize GL’s weakness