31–40 of 41 posts
This great talk is a pet peeve inducer, because after watching it you will start noticing how often the word "simple" is still used as a platitude in programming circles.
At least "simple" tries to say something - even if it's completely subjective. Far worse is "pragmatic".
This great talk is a pet peeve inducer, because after watching it you will start noticing how often the word "simple" is still used as a platitude in programming circles.
I.e., my code is simple--and that might make your usage complex.
Of course, things can evolve from the original implementation--especially if the code is maintained by a team. What was once 'simple' (from any perspective) can become terribly appendaged yet never renamed.
Related: Simple Made Easy (2011) - https://news.ycombinator.com/item?id=23905051 - July 2020 (30 comments) Simple Made Easy (2011) - https://news.ycombinator.com/item?id=13660797 - Feb 2017 (36 comments) Simple Made Easy (2011) - https://news.ycombinator.com/item?id=13313398 - Jan 2017 (2 comments) Rich Hickey: Simple Made Easy - https://news.ycombinator.com/item?id=4173854 - June 2012 (42 comments) Rich Hickey: "Sim…
Dumb and honest answer: do you have an automated tool to generate such a list of "we discussed that already" ? Would it belong "somewhere" in the base UI for HN (if it's ever allowed to change ?) Or do you just keep a list at hand for the usual suspects ?
Ooh, this time of year when engineers finely get some time to dig into longer tech talks. I remember watching the original "clojure" talks during Christmas break too. At least it's a found memory that I keep, as opposed to all the troubles getting a somehow functioning clojure dev environment set up back in the day... For all my whining, it has actually got better nowadays, although I still don't know if it's accepta…
They are going to create an error that you can see and fix immediately, in the vast majority of cases. Certainly in compiled languages (like clojure), but less so in interpreted languages like python, where a misspelled variable in a hidden part of the code may not cause an exception until that part of the code is run.
At least, that's my understanding of what he means by typos being less important than other types of mistakes.
By the way, when I saw his comment originally I was surprised too. But when comparing to the other kind of mistakes he talks about I realized that, yes, I'd rather have a typo than any of the other problems! Though of course, I'd prefer to have none :)
Rich Hickey's Sermons On The Mount changed my life as a programmer. 'Trouble is I can't look at OOP anymore without wanting to throw-up.
what has been seen cannot be unseen
Each to their own. There's room for everyone.
https://gbracha.blogspot.com/2022/06/the-prospect-of-executi...
Polymorphism is complex.
Earlier quoted context omitted.
I've never use clojure directly in any production work, but every one of his talks have influenced a ton of my programming in other languages. I'm a bit sad he hasn't had any recent talks. Feels like they've exhausted the journey, like there's not much else to extract from the clojure mindset even though it feels like there's a lot more there.
he just did a talk where he shows ppl how to use excel, rich hickey the manager
Related: Simple Made Easy (2011) - https://news.ycombinator.com/item?id=23905051 - July 2020 (30 comments) Simple Made Easy (2011) - https://news.ycombinator.com/item?id=13660797 - Feb 2017 (36 comments) Simple Made Easy (2011) - https://news.ycombinator.com/item?id=13313398 - Jan 2017 (2 comments) Rich Hickey: Simple Made Easy - https://news.ycombinator.com/item?id=4173854 - June 2012 (42 comments) Rich Hickey: "Sim…
Dumb and honest answer: do you have an automated tool to generate such a list of "we discussed that already" ? Would it belong "somewhere" in the base UI for HN (if it's ever allowed to change ?) Or do you just keep a list at hand for the usual suspects ?
Ooh, this time of year when engineers finely get some time to dig into longer tech talks. I remember watching the original "clojure" talks during Christmas break too. At least it's a found memory that I keep, as opposed to all the troubles getting a somehow functioning clojure dev environment set up back in the day... For all my whining, it has actually got better nowadays, although I still don't know if it's accepta…
> (I just wish I understood what in meant in "Effective Programs" by "typos are not important". They are, aren't they ? A typo is a runtime error begging to occur during the demo, how is that "not important" ? Never mind.) They are going to create an error that you can see and fix immediately, in the vast majority of cases. Certainly in compiled languages (like clojure), but less so in interpreted languages like pyth…
(Now, maybe it's PTSD from that time a typo in a script botched a demo in front of important people, and, well, let's say I avoided a bunch of scaling / domain complexity / temporal cohérence / etc... issues by not having to work on the thing any more ?)