Write code. Not too much. Mostly functions.
brandons.me
Write code. Not too much. Mostly functions.
1–10 of 362 posts
Re: Write code. Not too much. Mostly functions.
#2And functions should be no bigger than your head.
Re: Write code. Not too much. Mostly functions.
#3The quotes on nutrition remind me of arguments about the health implications of MSG, in that the argument tends to devolve to "is MSG good or bad" rather than "how much MSG is good or bad."
Re: Write code. Not too much. Mostly functions.
#4And functions should be no bigger than your head.
Well this explains why the most difficult people to work with always write the most disgustingly large god functions
Re: Write code. Not too much. Mostly functions.
#5And functions should be no bigger than your head.
This is my least favorite programming advice. Splitting functions for no reason other than "it's too long" is a bad practice. https://news.ycombinator.com/item?id=25263488
Re: Write code. Not too much. Mostly functions.
#6Re: Write code. Not too much. Mostly functions.
#7And functions should be no bigger than your head.
What if my cranium is extra large? Do I get to write bigger functions?
Re: Write code. Not too much. Mostly functions.
#8What is the point of this article? There is nothing new or interesting in it.
Re: Write code. Not too much. Mostly functions.
#9And functions should be no bigger than your head.
This is my least favorite programming advice. Splitting functions for no reason other than "it's too long" is a bad practice. https://news.ycombinator.com/item?id=25263488
Most of the illegible code I've ever written was because I kept splitting functions up, thinking I was following good practice, but was really just making emotional/aesthetic decisions.
When you go back to edit your code, it's like calling a 1-800 number and getting re-routed to 15 different departments to finally find the person you need to talk to.
Re: Write code. Not too much. Mostly functions.
#10And functions should be no bigger than your head.
This is my least favorite programming advice. Splitting functions for no reason other than "it's too long" is a bad practice. https://news.ycombinator.com/item?id=25263488
I think the trick is to split it the eight way. If you do it the wrong way, you end up with functions becoming layer upon layer of indirection that feels like a rabbit hole you need to dive further and further into to understand what is actually going on. But if instead you keep the core control flow in the original function, but move sensibly named chunks of into into helper functions - that way the original function ends up reading like pseudo-code, and you don't really need to actually look at any of the helper functions to understand what is going on.