|
Ah ok thanks
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
|
|
|
|
|
Don't you hate it when you have to explain a joke?
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I used to but now it gives me a great feeling of superiority, a warm fuzzy - as long as it's not my joke I'm explaining!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
...or when you get to nine you decide that's a neuf!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Quatre it out, you guys.
cheers
Chris Maunder
|
|
|
|
|
Well that’s it guys. Chris sinq the thread. We must six immediately!
If you can't laugh at yourself - ask me and I will do it for you.
|
|
|
|
|
Mona Lisa cut repaired with blemishes (11)
|
|
|
|
|
MACULATIONS
Anagram of "Mona Lisa cut": "a blemish in the form of a discrete spot, such as an acne scar"
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Yeah that's the one
|
|
|
|
|
May I inquire how you were lead to the solution Every list of synonyms I traveled did not provide it I am assuming it was as new to you as it is to me Do you have software which generates anagrams and checks their definitions - Cheerio
"I once put instant coffee into the microwave and went back in time." - Steven Wright
"Shut up and calculate" - apparently N. David Mermin possibly Richard Feynman
|
|
|
|
|
To be honest, I don't have a clue: my head is stuffed with useless sh*t that springs up when I need it. Mostly to annoy people in Trivial Pursuit games ...
Probably, it came up in a crossword, a book, a scramble game, or somewhere else equally random at some point and I looked it up to find out what the heck it meant.
Anagrams aren't that difficult - they generally leap out at me, or I write them down in a "cloud" and see if anything connects.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
|
The approach I take when I am fairly sure there's an anagram is just to examine the letters. Here the clue ("blemishes") is plural, so it's a fair starting point to assume the word may end in s. There's no e so, unlike blemishes, it's not es at the end so we've now simplified it to a 10-letter anagram. We've got all the letters t, i, o and n so there's a good chance it ends "tions". Great, now we just have a 6-letter anagram to solve. At this point I write down the 6 letters in a random pattern (not all on one line) and just gaze at the centre of the group. I'm not "reading" the letters, just looking at them as a group (or a cloud as Griff has better termed it). Sometimes this works and the word "pops out", sometimes not. If not, with 6 letters, it's not too hard to just start trying sequences that would be pronounceable. In this case, I can fairly readily spot the combination "macula" which I associate with macular degeneration, a particular type of sight loss. I don't know exactly what causes it, but a quick search on "macular" tells me it's (1) a small spot or (2) a small discoloured spot or blemish. Put the two together, MACULATIONS. Look that up to verify. (At this point the definition tells me maculations also refers to the pattern of spots or markings on an animal or plant, and at that point I remember it's a word I've come across before anyway, and now I understand its derivation!)
In short, look for likely patterns from the letters you have, then shake up the leftovers until they sound likely, then verify. I've been out today so haven't looked at the clue till this evening, but I suspect I'd have got there...
|
|
|
|
|
Well said Derek
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
|
|
|
|
|
Further to my earlier reply about anagrams, it's finally dawned on me (whilst in the shower) that the word immaculate simply means "without maculations"... so not as rare a word (root) as you might think!
As in 2nd level support: "No sir, that's not a bug; it's a maculation of the code".
|
|
|
|
|
ok, sometimes there are very good comments...
but every time the reviews are waaaaay too slow. and very often there are comments which are both useless, antagonistic and a big waste of time...
for example I don't see the point of long variable name nor do I like them, particularly for a short liner like
double Value
{
get
{
var x = Calculation();
return flag ? x : 2 * x;
}
}
And have to wait a few more hours because I was told 'not to use short variable name'.
Unsure I renamed 'x' to 'aNumber', but that irks me...
On top of that, that might be just me with my bad memory, but I find long variable name harder to read!
For example a simple expression like a = b + c
can confuse me if you write instead myobjectBlu = aCycleValueOrdinal + meteorStrikeOffsetTime .
Why they not care about making the code easier to understand?!
ok, ok, I need to get over it. just venting here!
Joke aside, you might like long variable name, but you won't convince me. save everyone's time and let's just agree to disagree. Or disagree to disagree, if you prefer...
EDIT
Upon reflection, I might be part of a minority of people with reading disability..
When reading long sentence I am skipping words and filling in by guess. Similarly long line of C# requires me multiple reading. And it kind of depends on the overall number of character, not words...
So I guess normal people comes with their usually suck it up, I am fine...
modified 7-Sep-21 2:40am.
|
|
|
|
|
double Value
{
get
{
var x = Calculation();
return flag ? x : 2 * x;
}
}
Uugh. Why not something easier to understand?
double IdiotSize
{
get
{
var size = CalcSize();
return notDoubledFlag? size : 2 * size;
}
} Or whatever the domain really is?
|
|
|
|
|
so we disagree to disagree then?
I find the later no easier.. In fact some interesting brain chemistry must be at work here...
I was reflecting how physicist (that's my background), prefer short name too, i.e. it'e E=mc^2 , not Energy = Mass * SpeedOfLight^2 , to vindicate me...
Anyway, regardless, it's more interesting to consider what psychological factor lead from one to another.
I know that for me, bad work memory favor short variable names. Long variable names are just too hard, I have to read the statement 2 or 3 times to get it.
1 or 2 time to get all the variables involved, and one more time to get the computation. I can get all that in one go/read with shorter text - i.e. short variable names and simple math.
Maybe I have some sort of dyslexia or something, I tend to not read big wall of text very accurately. Not just in code but also in plain English... Hence for me shorter variable name increasing my accuracy / understanding...
modified 7-Sep-21 1:48am.
|
|
|
|
|
Another angle: I do use single-letter Field names when:
1) they are used only in the scope of a Method/Function
and
2) they are, imho, easily recognized, in context, as representing logical attributes.
So, in a Method that takes a Rectangle as a parameter: I might, as the need arises, use 'w for 'Width, 'h for 'Height, etc. I only use 'i, 'j, 'k in for loops.
But, if an employer wanted longer names, no problem; the 'name issue is not a "religious" issue for me, but, I value consistency.
«The mind is not a vessel to be filled but a fire to be kindled» Plutarch
|
|
|
|
|
yea, exactly my case...
but from the strong reaction here, I think there some brain type at work...
|
|
|
|
|
Super Lloyd wrote: so we disagree to disagree then?
You agree to disagree. If you disagree to disagree, then you agree.
|
|
|
|
|
When I came up with that sentence, I suddenly get this meaning...
Disagree to disagree is when you keep arguing with the hope I'll eventually agree...
Agree to disagree is when we both realize we ain't gonna agree...
|
|
|
|
|
Super Lloyd wrote: so we disagree to disagree then? No. If I was the boss and an employee used Calculate as a function name I'd shitcan him or her, unless it was obviously a joke and they fixed it as soon as the laugh was had. I would not let a codebase I am responsible for be polluted by such meaningless names that all coders from there on out are going to have to spend precious time figuring out the intent of even something this simple. Among the oldest of business mantras is "Time is Money". And coding like this wastes everyone else's time. Making a lone coder happy, even if they are good, isn't worth it in cases like this.
|
|
|
|
|
We have a rule, if an acronym is well known, then we use it (eg url rather than universal resource locator), otherwise we spell out the full words.
A few years ago we where working on a system which had a limitation on some names, but we needed those names to be descriptive of the keys. We ended up with a jumble of 3 letter acronyms everywhere.
Sure enough, the parts we touched frequently where easy enough to deal with, but gee looking at some of the sections which remained fairly static was a nightmare to determine what was going on and what held what data.
|
|
|
|
|
you missed the part where I was talking about a variable.. inside a method...
|
|
|
|
|