veganism.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Veganism Social is a welcoming space on the internet for vegans to connect and engage with the broader decentralized social media community.

Administered by:

Server stats:

297
active users

#cleancode

3 posts3 participants0 posts today

Dear Gradle, Why So Stubborn?
Do I do something wrong?

Watching juniors try to set up a project and being greeted by cryptic stack traces like it's some kind of initiation ritual.

`Unsupported class file major version 61`
`invalid CEN header zip64 no access package`, ...

Java can compile code for older versions just fine.
It's literally designed for that.
Oh why, must Gradle behave like a bitter librarian who refuses to hand over a book unless I whisper the exact Dewey Decimal Code?
Every other Language will laugh again at java, seeing this.

💡 Why is Gradle bound to a java version? And if Gradle knows it needs Java 11… why doesn't it just do this for me?
Like using `/usr/libexec/java_home -v 11` in background?

🤖 Is there a clean way to force Gradle into submission without adding another tool like SDKMAN or jabba or YunaBraska/gradle-java-fix or whatever the trendy painkiller of the week is?

🔍✨ Behold the revolutionary revelation: less is more in the land of software design! 🚀 Apparently, if your code doesn't look like a Jackson Pollock painting 🎨, it's clearly an underwhelming masterpiece. Remember, folks, if it ain't broke and doesn't dazzle, it must be boring! 🙄👾
seangoedecke.com/great-softwar #softwaredesign #minimalism #codingtips #cleancode #techhumor #HackerNews #ngated

www.seangoedecke.comGreat software design looks underwhelming--

> "If your code needs a comment to be understood, it would be better to rewrite it so it's easier to understand."
- doc.cat-v.org/bell_labs/pikest

Pondering this over tea this afternoon. I would tend to agree. If code is well-written, with well named structs, variables, etc it should be _almost_ self-explanatory.

Now...well-named to one dev might come off as poorly named to another, but I think there's a kernel of truth here. Less comments, placed strategically, are best. Avoids scenario where comments end up being misleading when they are not changed while the code they refer to is changed. :neofox_dizzy:

What do you think? All the comments? No comments?
#programming #cleanCode

doc.cat-v.orgRob Pike: Notes on Programming in C