|
I had to google who Rhapsody of Fire are. I still don't know if you now understand their music better or if you think you were listening to bad music earlier.
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
dan!sh wrote: if you now understand their music better or if you think you were listening to bad music earlier.
Yes
It's good music but a bit cringey and full of tropes, overproduced and very cringey - yes I know I said it twice. It has its charm but honestly I'm not delving much more into Power Metal because the entire genre is like that. It gets boring fast.
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
In the name of Holy Thunderforce!
I think your current reaction was pretty much my initial reaction, although they have some enjoyable songs.
A friend of mine listened to it a lot, and he got it from me
|
|
|
|
|
The Duck Tales theme song is still fire though!
|
|
|
|
|
Indeed but I have always watched it in Hindi. I do not know how the Dutch or English version is like. I might end up comparing lyrics this Friday evening!
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
Maybe you should share that Lounge-Crawling-Program code as a short article or tip. Will be useful to others like me.
|
|
|
|
|
Fairly certain it wouldn't.
Do an HTTP request, parse the returned HTML using the HTML Agility Pack, then if (html.Contains(">Sound of the Week<")) select a specific node and then go .ParentNode.ParentNode.NextSibling because I've looked exactly at what I needed.
Counting how many parent, sibling or child nodes you have to skip is hardly worth an article
|
|
|
|
|
Ok.
It's also true that a lot of "programmers" will not know how to do it. Isn't it.
|
|
|
|
|
Soften staff speed (8)
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
I see what you did there!
Nice clue.
"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 liked it - bit too easy though
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
Says who?
“Real stupidity beats artificial intelligence every time.”
― Terry Pratchett, Hogfather
|
|
|
|
|
Well ... two of us found it simple - doesn't mean it is for everybody though!
"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 rarely get the CCC and I can only get half of this one.
|
|
|
|
|
Yeah, I see soften = moderate -- with rate being equivalent to speed -- not sure how mode equates with staff though...musically perhaps?
|
|
|
|
|
See below ...
"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!
|
|
|
|
|
OK, I'll take it and let them out of their misery ...
Soften
staff MACE
speed RATE
MACERATE
Did you get Mace Rates when writing it?
"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!
|
|
|
|
|
Yes and you are up tomorrow
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
on a code review someone commented I was enumerating twice a really big list, could I have only one loop instead, they said
initial code, where source is a large list
list.AddRange(source.OfType<A>());
DoThings(source.OfType<B>());
void DoThings(IEnumerable<B> items)
{
foreach (var b in item)
{
}
}
so to please the crowd I refactored
new code
foreach (var item in source)
{
if (item is A a)
list.Add(a);
if (item is B b)
DoThing(b);
}
void DoThings(IEnumerable<B> items)
{
foreach (var b in item)
DoThing(b);
}
void DoThing(B b)
{
}
now... without doing any measurement (hence the blind adjective) I am suspecting version 2 is in fact slower, since enumerating is cheap, but there a lot more method calls.
What says you?
modified 1-Jun-22 7:01am.
|
|
|
|
|
I could argue the performance either way, so unless this has been pinpointed as a bottleneck I would ignore performance.
With that in mind I would go with the first method, as it is a lot clearer and more maintainable.
If it does become a performance bottleneck I would consider refactoring the source so it does not store A and B together, as that will presumably be an issue in a lot of places.
|
|
|
|
|
I am glad you find first method clearer too!
Yeah, whatever... Arguing during code review is painful, so I'll go with version 2, it's pointlessly but minutely different... no biggie...
|
|
|
|
|
I would prefer option one. It seems cleaner to me. I find code that jumps through 15 methods to do a job confusing.
For performance, there is no way to comment. I would focus on how is this method going to get used. If it is once a day and saves me a nanosecond, I do not care as long as application does not need to be that fast. But if it is used million times a day and saved a millisecond each run, then I would focus.
I find these performance analysis of individual methods not really useful. We need to look at application usage in my opinion rather trying to make fastest ever code. In the end, this is a business and if I spend a day to refactor to gain a second in a day at say 1000 Euro cost, it does not look good.
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
I think this is a very valuable comment from the reviewer and it has potential to improve performance a lot.
It can take a lot of time figuring out who understands what to optimize and who doesn't have a clue. With this review comment you will no longer be in doubt: That guy has no idea and everything he says about performance can simply be ignored.
Think of all the time his comment can save you in the future - Your performance will definitely improve by not wasting time on him.
|
|
|
|
|
Wow, amazing tip!
|
|
|
|
|
I prefer #1. It might even be faster since AddRange() might do clever stuff under the hhod
"If we don't change direction, we'll end up where we're going"
|
|
|
|