zirk.us is one of the many independent Mastodon servers you can use to participate in the fediverse.
Literature, philosophy, film, music, culture, politics, history, architecture: join the circus of the arts and humanities! For readers, writers, academics or anyone wanting to follow the conversation.

Administered by:

Server stats:

731
active users

#preference

0 posts0 participants0 posts today

Dear artists and photographers,
your works are often incredibly inspiring to me! Thank you!

...but to people who put digital watermarks on inspiring works, I try like the dickens to never boost watermarked stuff. It is very unfortunate! And the world shed a tear for the misrepresentation of your otherwise immaculate, yet intentionally marred expressions...

Apple Notes on iPad, writing with the pen, when it takes your handwriting and then re-inserts it every so slightly, but unnecessarily different. Definitely auto, but not refined. It can be switched off! In the tools palette, the … menu, look for the "Auto-refine Handwriting" switch. #iOS #handwriting #preference

A quotation from John Adams

Facts are stubborn things; and whatever may be our wishes, our inclinations, or the dictates of our passions, they cannot alter the state of facts and evidence.

John Adams (1735-1826) American lawyer, Founding Father, statesman, US President (1797-1801)
Speech (1770-12-04), “Argument in Defence of the Soldiers in the Boston Massacre Trials”

Sourcing, notes: wist.info/adams-john/1456/

Replied in thread

@graham_knapp

A lot of it is always going to come down to personal preferences. But I think the different cases are more or less appropriate depending on the problem being solved.

If you're calling a function or creating an object that you expect to almost-always work - it fails when low on memory, or when the network connection is broken, or some other exceptional (hint) condition, then I think exceptions are most appropriate. Throw one, and let it bubble up the caller's stack until they either handle it and possibly re-try, or the program exits with a diagnostic.

If you're calling something that can reasonably be expected to both succeed or fail under normal conditions - say a command given in an inappropriate state fails, but otherwise succeeds, maybe - then an explicit return object with success/failure (and possibly a result, and / or an error message) can be better, as the caller expects to handle failures immediately.

Both are easy in Python; I've implemented the latter with tuples, named tuples, custom classes, and dataclasses over the years for different projects.

</0.02>

A quotation from Bacon, Francis:

«
Man prefers to believe what he wants to be true. He rejects what is difficult because he is too impatient to make the investigation; he rejects sensible ideas, because they limit his hopes; he rejects the deeper truths of nature because of superstition; he rejects the light of experience, because he is arrogant and fastidious, believing that…
»

Full quote, sourcing, notes:
wist.info/bacon-francis/1260/

WIST · Instauratio Magna [The Great Instauration], Part 2 "Novum Organum [The New Organon]," Book 1, Aphorism # 49 (1620) [tr. Silverthorne (2000)] - Bacon, Francis | WIST QuotationsMan prefers to believe what he wants to be true. He rejects what is difficult because he is too impatient to make the investigation; he rejects sensible ideas, because they limit his hopes; he rejects the deeper truths of nature because of superstition; he rejects the light of experience, because…