No bounds check on `i`, so 257 characters into this and you're writing straight into whatever the hell lives past `line`. That's not reading a line, that's a buffer overflow with a getchar costume.

Read a line

A getter that increments the thing it's getting, so every caller gets a different answer and half of them accidentally write to the database. You turned a read into a write and called it `getCount`, which is the kind of lie that ends in a 3am incident review.

Getter with side effects

Session

Copy an array

Goroutine leak

You built an `interface{}` tunnel that shits out `int` when you put in a `string` and calls that "processing." That's not type switching, that's a pipe that turns everything into a mystery meat surprise and dares the caller to guess.

Empty interface everywhere

Swallowing a ZeroDivisionError and returning 0 means some poor bastard eventually divides by that result and gets zero again, forever. You didn't handle the exception, you fed it and taught it to reproduce.

Exception handling

Eight threads doing unsynchronised `count += 1` because Python's GIL is doing sweet fuck all to protect a read-modify-write, and that little `# 800000, probably` comment is you admitting the bug before the interpreter even gets to embarrass you. You didn't write a counter, you wrote a race condition with a prayer attached.

Counter

Cart total

Seven divs to make a button, and the only functional line is an inline `onclick` calling `submit()`, a global name so generic it'll collide with anything on the page. The browser already shipped a `<button>` tag, but sure, hand-build the whole thing.

Most EWW