> grug has never used erlang, hear good things, but language look wierd to grug sorry
maybe grug try drink elixir?
The Grug Brained Developer
71–80 of 394 posts
Re: The Grug Brained Developer
#72complexity isn't bad, redundant complexity is
Re: The Grug Brained Developer
#73Earlier quoted context omitted.
Not who you're replying to, but Tcl was that language for me. Dead-simple syntax, documentation, and behavior. I loved it. But also dead-simple tools. And if you wanted to do anything that wasn't a "solved problem" already, you had to write your own library. When I switched my focus to Python, everything was more effort but I could also do _much_ more with it.
> And if you wanted to do anything that wasn't a "solved problem" already, you had to write your own library. For which language is that statement not true ?
Their point is that the language they’re discussing requires you to write that library far more often than other languages, as a second order effect of few using it. But you know that already, you just want to make a semi-snarky reply instead, I guess.
Re: The Grug Brained Developer
#74Kevin, is that you?
Re: The Grug Brained Developer
#75> unfortunately also many test shamans exist. some test shaman make test idol, demand things like "first test" before grug even write code or have any idea what grug doing domain!
I am keeping that.
Re: The Grug Brained Developer
#76Ah, the ample club of wishful thinking. There are two general ways of approaching software design (and I'm paraphrasing Tony Hoare here): 1. You can write software so simple there are obviously no errors 2. You can write software so complex there are no obvious errors One thing that escapes "grug" is that achieving 1. often requires more sophistication than their magical club allows. Most well-intentioned "grug" deve…
>There are two general ways of approaching software design (and I'm paraphrasing Tony Hoare here): 1. You can write software so simple there are obviously no errors 2. You can write software so complex there are no obvious errors
And both are neither here, nor there, regarding what the article talks about, which is basic advice that always holds: avoid complexity, say no whenever possible, opt for 80/20 solutions.
>One thing that escapes "grug" is that achieving 1. often requires more sophistication than their magical club allows.
Which is irrelevant to grug's point, as he doesn't pretend to advocate achieving 1.
Re: The Grug Brained Developer
#77> grug very like type systems make programming easier. for grug, type systems most value when grug hit dot on keyboard and list of things grug can do pop up magic. this 90% of value of type system or more to grug
This resonates with me
Re: The Grug Brained Developer
#78Australians of a certain age might have a different (yet not that different) take on the Grug brain: https://www.simonandschuster.ca/books/Grug/Ted-Prior/9780731...
Re: The Grug Brained Developer
#79Now this is a good post. Especially the part about the frontend Complexity Demon having a grip on the entire industry, and the Fear Of Looking Dumb. It goes hand in hand.
> frontend Complexity Demon having a grip on the entire industry Is frontend web development more complex than it needs to be? If so, how?
Hehe, good one!
Oh, you're serious? :D
Re: The Grug Brained Developer
#80This reads a lot like like commit comments, status reports, e-mails and tickets in a company in which everyone is from a different country from around the globe. If you can't read grug English, you will find it hard to navigate in the global workforce.
I have accidentally introduced “dope” as a thankful affirmative into our international developers lexicon at work. There’s another even more amusing one too but I can’t remember what it is. Working with global teams is fun!