How to Write Unmaintainable Code (2017)

Re:How to Write Unmaintainable Code (2017) by maerF0x0 on Friday August 17, 2018 @12:52PM (#17784156)

Disclaimer: This comment is mostly in jest.

For a second there I thought i was reading about golang[1].

* Single letter var names[2] / [3]

* Underscores [4] / [5]

* extended ascii code [6] / [7]

[1]https://golang.org/doc/effective_go.html

[2] https://github.com/Droogans/unmaintainable-code#single-lette... [3] https://github.com/golang/go/wiki/CodeReviewComments#variabl...

[4] https://github.com/Droogans/unmaintainable-code#underscore-a...

[5] https://golang.org/doc/effective_go.html#blank

[6] https://github.com/Droogans/unmaintainable-code#extended-asc...

[7] https://golang.org/ref/spec#Source_code_representation

[ Parent | on HN ]

Re:How to Write Unmaintainable Code (2017) by ppeetteerr on Friday August 17, 2018 @02:52PM (#17784948)

Oh man, any time I read example Go code it always reminds me of code from the 80s/90s. Probably written by the same crowd too.

[ Parent | on HN ]

Re:How to Write Unmaintainable Code (2017) by marcosdumay on Friday August 17, 2018 @02:13PM (#17784670)

> Single letter var names

They are also a Haskellers favorite.

There's a non-sarcastic paper running on the internet named something like "descriptive variable names considered harmful". Most of the community agrees with it, including me.

[ Parent | on HN ]

Re:How to Write Unmaintainable Code (2017) by therealdrag0 on Tuesday August 28, 2018 @09:20AM (#17858571)

Why are they harmful?

[ Parent | on HN ]

Re:How to Write Unmaintainable Code (2017) by Hirak on Friday August 17, 2018 @02:35PM (#17784840)

> Single letter var names

There are tons of those in Android framework code as well

[ Parent | on HN ]