Ah, "Explaining". There's your problem.
Lets have a checklist with supporting documentation, please~
Situations like this remind me of devs that talk at people, but not with them.
Leaving 3 weeks worth of senior work to a junior is your own damn fault.
The meme doesn't say that happened
Came back to learn you created job security
FIFY
Tomato tomayto
Worst is redo it all
Can't help but think of a "senior dev" "explaining" (hing: brain-dumping) some bizarre reasoning why his unusable untested undocumented untyped API uses floats for item counts or something, and expecting the "junior dev" to just nod and keep that in their mind and adapt to it.
(Instead of making every possible excuse not to work with that API and instead doing something else where they can make some progress without going insane.)
They probably got stuff done, just not the things you left half implemented code for...
Just started a new job last week. Ive been in the industry for 3 years so not completely junior but getting in to a new codebase is always rough. Especially when only 1 huge library file is documented, every component is cluttered af and most variables and parameter names are 1 character long.
Doesnt help that functions are 100 lines either when each the parameter names makes the logic incomprehensible.
