Earlier quoted context omitted.
They're not though. They only exist as the relation between the edge and the start of content. How many levels of indentation are there on each line? https://i.imgur.com/s1WBHxU.png Spoiler: Line 3 has no indentation while Line 6 has one level. Line 4 has a mix of tabs and spaces that would confuse Python. The fact of the matter is that indentation is white space, and white space is implicit by definition. It only ex…
Stop using a legacy version of Python. You will get a "TabError: inconsistent use of tabs and spaces in indentation" exception if you use Python 3.
The Complexity Trap: Think Before You Leap
41–47 of 47 posts
Re: The Complexity Trap: Think Before You Leap
#42“Everyone knows that debugging is twice as hard as writing a program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it?” --Brian Kernighan How many times have I bitten myself this way? Dear past me: stop being so smart.
Re: The Complexity Trap: Think Before You Leap
#43This is a little-acknowledged industry-wide problem that extends beyond hot-shot overengineering to reems of banal code too, so I would rather it be written from a less expected perspective.
Re: The Complexity Trap: Think Before You Leap
#44Earlier quoted context omitted.
> functional fanatics that design solutions only top 20% of devs can understand Not a part of that group, but I think this is a false narrative. 20% might be accurate, or it might be a bit high even. But it has nothing to do with `top` or `bottom` performers. It's purely to do with exposure to functional styles. Learning Haskell first doesn't make you a top 20% developer, much as I'm sure HN in particular will want t…
>many who learn one first Everyone learns imperative first. "Wake up!" or "Eat your vegetables!" are imperative. No-one says to their kids, "map(vegetables, eat)"
If you want to use that example it'd be more like this snippet that no one on earth would tell their children:
> Starting from n = 0, take the nth vegetable from your plate, insert your fork into that vegetable, raise your fork to your mouth, bite that vegetable, remove your fork from your mouth, masticate, add one to n, and repeat.
Re: The Complexity Trap: Think Before You Leap
#45Has somewhat similar intro to the Rich Hickey's famous "Simple made easy" talk. A good read nevertheless.
Re: The Complexity Trap: Think Before You Leap
#46As one who frequently deals with Scala code, I have to say that this guy is right: the Scala community in particular seems to relish in complexity. Scala is a wonderful language and well-designed, especially in contrast to Java. The learning curve requires a good deal of effort, but with experience, it becomes incredibly fun to write Scala code. Once I got past the learning curve, Scala became my go-to language. That…
Also, it is not seldom that you hear them say "It took me n years to fully grok the _whatever FP concept_". Or Martin Odersky doesn't get the _whatever FP concept_.
So how do they expect the majority of sw engineers will use/adopt those principles if the guy who invented Scala "does not get it" and even themselves took so much time to "get it"...???