Learn More
Resend Email
35
Worst dev advice you've been given?
Week 66 Group Rant
v-kip
7y

"First remove the break points, and then commit the code".

He described it as if the breakpoints could stop time!! 😂

undefined

wk66
Favorite
Ranter
Comments
  • 0
    7y
    That's really quite scary...
  • 9
    7y
    they r called break-points after all ...

    hey the build is broken, who checked in a break point
  • 2
    7y
    Some IDEs used to keep the breakpoints on a project file. I remember having that issue on NetBeans, not sure if by itself or with a plugin. Perhaps they got used to remove the breakpoints before adding all the files.
  • 2
    7y
    @Eariel Aah. That explains why the senior Dev started that practice. Unfortunately junior devs followed, without asking why. They reasoned the app will stop in prod and no one will be there to hit resume. 😛
  • 1
    7y
    Old versions of ABAP (programming language for SAP ERP) had brakepoints in the code! You literally had to explicitly write them. So depending on the environment this may be a good advice
Related Rants
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment