this post was submitted on 03 Sep 2024
859 points (99.5% liked)

Programmer Humor

32396 readers
1646 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 48 points 2 months ago (2 children)

Just run your prod env in debug mode! Problem solved.

[–] [email protected] 28 points 2 months ago (2 children)

Lol my workplace ships Angular in debug mode. Don't worry though, the whole page kills itself if a dubious third-party library detects the console is open. Very secure and not brittle at all! ~~Please send help~~

[–] [email protected] 12 points 2 months ago (1 children)

Blink-blink-blink. Blink. Blink. Blink. Blink-blink-blink.

No, I don't have something in my eyes, I swear I'm fine looks nervously at boss.

[–] [email protected] 2 points 2 months ago

Hang tight help is on the way.

[–] [email protected] 2 points 2 months ago (1 children)

Now I'm curious how this detection would work.

[–] [email protected] 5 points 2 months ago

I've seen some that activate an insane number of breakpoints, so that the page freezes when the dev tools open. Although Firefox let's you disable breaking on breakpoints all together, so it only really stops those that don't know what they're doing.

[–] [email protected] 25 points 2 months ago* (last edited 2 months ago) (2 children)

You can imagine how many node projects there are running in production with npm run. I have encountered js/ts/node devs that don't even know that you should like, build your project, with npm build and then ship and serve the bundle.

[–] [email protected] 14 points 2 months ago

I just died a little inside. Thank you.

[–] [email protected] 11 points 2 months ago

i have absolutely seen multiple projects on github that specifically tell you to do "npm run" as part of deploying it.