he/him
I just inherited my first codebase a few months ago. It’s like this everywhere and original developer was fired, so what should sometimes be a simple fix turns into a full day of finding what needs to change. Any recommendations on fixing/maintaining code like this or should I just make it the next person’s problem?
When I was a kid I put a yellow cherry pit up my nose while my family and I were on a bus. I remember trying to dig it out, but pushing it deeper every time I did until I started sneezing uncontrollably. By this point I was crying, but it was so far up that nobody could see it and thought I was lying. The bus driver stopped doing his route and took us to the nearest hospital. They were able to find it and 3 nurses held me down while the doctor stuck some medical pliers up my nose to pull it out. After wards the doctor said that had it been 1 centimeter deeper I would have asphyxiated to death and yelled at my parents for letting me have small object.
Don’t know if this helps since dokuwiki lets me link pages, but I have a main page where I just do a one paragraph description of every big thing in use.
each page has:
I’ll also add any notes in the misc section in case I need to reference them later. If a service is mentioned, I’ll create a page for it and link to it every time I mention it. That way nothing is more than a few clicks away and the documentation grows naturally as long as you don’t have any monolithic application. Example: (main -> Docker -> Project_Ozone_2 -> custom configurations Or main -> Joomla -> wysiwyg ->JCE Editor)
I also had a professor tell me to just write everything down first and then focus on formatting to find what kind of structure suits your needs best.