That first reply is so funny to me because it hits too close to home https://twitter.com/nice_byte/status/1466940940229046273 The more I do this, the more I gravitate towards the simple things.
Funny, I posted this on another HN thread [0] recently, but it's perfectly relevant again: We shall not cease from exploration And the end of all our exploring Will be to arrive where we started And know the place for the first time. T. S. Eliot - Little Gidding [0] https://news.ycombinator.com/item?id=29043941
“Coding is basically just ifs and for loops.”
121–130 of 418 posts
Re: “Coding is basically just ifs and for loops.”
#122also "coding is basically over glorified plumbing". ~ my cynical coworkers
Re: “Coding is basically just ifs and for loops.”
#123Re: “Coding is basically just ifs and for loops.”
#124I also like "all web development is basically fancy string concatenation", and as a web dev I feel seen.
Re: “Coding is basically just ifs and for loops.”
#125you guys have for loops?
Re: “Coding is basically just ifs and for loops.”
#126A Turing machine is basically just ifs in a loop.
Re: “Coding is basically just ifs and for loops.”
#127If you want to go even lower than that, coding is basically just saying yes or no in response to a yes or a no . Sure, that's oversimplifying it, but that's the smallest unit of information being changed during computation. But yes, once you learn the basics that are shared between most programming languages and don't get distracted by the nuances, it doesn't take that long to pick up a different language. Being prof…
yes, at the lowest level its binary code, 0 and 1
Re: “Coding is basically just ifs and for loops.”
#128Earlier quoted context omitted.
It’s just so sad that the lowest common denominator has become the standard now. When I first learnt Clojure it entirely changed the way I think and solve problems. The code really was elegant. Obviously, it can only be read by someone who can also understand programming beyond ifs and fors. That’s a non-starter in most environments - enterprise or otherwise. Funny enough, I see most innovations coming from consultan…
Ifs and fors are the easiest concepts to explain to non-developers, so it makes sense to start there. I wouldn't say that they are the standard now, but using and mastering all features in a language is hard. Add to that design patterns, classes and code layout it becomes a full-time job to keep up. I have been in contact with code most of my professional life, but still isn't comfortable writing large amounts of cod…
However, most of those features are relatively standard and are more conceptual than syntactical in nature. Bashing people because they don't know stuff is stupid and counterproductive, but I shouldn't be forced to code in the programming equivalent of roman numerals just because someone else can't be properly fucked to understand lambdas or interfaces or generics, all stuff that's literally covered in your run-of-the-mill CS 101 course.
It all boils down to having enough humility and empathy to understand that other people are not, in fact, the same as us.
Re: “Coding is basically just ifs and for loops.”
#129Re: “Coding is basically just ifs and for loops.”
#130Earlier quoted context omitted.
> you eventually "give up", and clock your 9–5 writing if+for making a fine living, but erroneously pass that off as a mature This comment sure indicates to me where you most likely are on the curve. In all seriousness, I think this is considerably off the mark. After enough experience you realize that expressivity and convenience are antipatterns and don't actually simplify things but are harbingers of complexity, b…
Personally I disagree. We should be using state machines and pure functions. If+for loops are just what's easiest to express in the major languages of today. they are no more or less computationally expensive but due to lack of tooling they are often cheaper to write. In languages and libraries that allow FSM and pure functional kernel based designs you can get just as clear logic that is expressible not just to the…
I’m yet to see a secretary who could “return a new table state such that as if documents became a right fold as binding together a map of composition of signing and copy routines over documents” instead of “get these documents from the table, copy, sign and put them back in a binder”. This is a nonsense some of us want to believe in, but it is not true.