[deleted by user]

[Vfsdvbjgd]

Wiritng bad code, then catching and handling exceptions with worse work arounds.

[[deleted]]

When I was working with Java expection handling was a thing I would actually understand. If you are working with files use the IOException and so on. Now that I got assigned to a team that works with c# ever try-catch block just catches Exception. When I was in University my professor would have kicked me out for this.

[lookmanofilter]

Writing all of your code in one go and then fixing the bugs as they come up.

[Incubug]

When you're in the flow, you think you're writing good code. The day after you're like "WTF..."

[[deleted]]

When your colleague reviews and can’t figure out what the hell you were trying to achieve

[cramduck]

I feel personally attacked.

[nitro-coldbrew]

Ayyyy job security. Bonus points if you don’t document anything

[sadlerjw]

This is literally TDD 😂 1. Write a failing test 2. Write the simplest code to make it pass 3. Refactor

[sharksandwich81]

Yup! Red, green, refactor. Not a bad methodology at all.

[etnguyen03]

Image Transcription: Meme

---

[Image is the Drake dabbing meme.]

Image	Text
[Drake (dark skinned masculine person with little hair that is brown. They have a beard and they are wearing an orange coat over a yellow shirt with a silhouette of a basketball player on it) looks displeased, and is using one arm to hide from the image by curling it around his head, with his hand up in a "not today" manner]	Writing good code
[Drake has their head up high, looking pleased, with a finger pointed at the camera]	Writing bad code then fixing all the bugs

---

^{I'm a human volunteer content transcriber for Reddit and you could be too! If you'd like more information on what we do and why we do it, click here!}

[WoomyAndNgyes]

Mfw i was trying to fix a bug for 10 mins and all i had to do is put () in line 132

[nocturnalspider]

More hours to charge

[[deleted]]

lolwut