I'm of the view that in large bodies of code, a little comment giving a brief explanation of what the code does can be very helpful. If my colleague writes a massive package that does something, I don't want to have to spend hours breaking it down so I can understand it. You can nearly always half that time by adding a little comment like this:
-- Working Day 01: 1st Email/MessagebeginPKG_LOCK_CHASE.FIRE;end;/-- Working Day 02: 1st Email/Message + 1updateTBL_LOCK_CHASEsetCREATED_ON=CREATED_ON-1;deleteTBL_LOCK_SFTPwhereDEVICE_IMEIin(selectDEVICE_IMEIfromTBL_LOCK_SFTPwhererownum<=5);beginPKG_LOCK_CHASE.FIRE;end;/
I know exactly what those blocks are doing without having to go into each package and work it out.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm of the view that in large bodies of code, a little comment giving a brief explanation of what the code does can be very helpful. If my colleague writes a massive package that does something, I don't want to have to spend hours breaking it down so I can understand it. You can nearly always half that time by adding a little comment like this:
I know exactly what those blocks are doing without having to go into each package and work it out.