|
Yeah sorry, my comment was pretty OT. I really don't like codereviews either but they do serve a purpose, when they're done properly. Fussing over the name of a variable is not doing it properly.
// E
|
|
|
|
|
Code should be easy to skim for the easy bits, so using descriptive variables is helpful, as is insertion of concise comments, but descriptive needn't be long.
Also, as long as you keep in mind the scope of each variable and are doing any trash collection that is needed by your language choice, then short names are fine, especially as iterators. Just don't be lazy and leave a variable living longer than it is needed.
|
|
|
|
|
see.. you obviously didn't read what I said.
I said it is much harder for me to read those long names.
I am cool though, however strange, I believe you when you said you find long names easier... I just beg, don't make me suffer for your personal convenience...
|
|
|
|
|
I did say that descriptive names need not be long, and that iterators need not even be descriptive. Clarity is the goal, so using a name like double_me for a flag might be all that's needed, leaving your input variable as x.
Did I say that long names are easier? I don't remember saying that.
|
|
|
|
|
One thing not mentioned in the other replies is the readability from the very first word.
In your example of
a = b + c
If a was named better then I wouldn't need to read the rest of the code to understand what I'm dealing with.
So in the long run I can gain general understanding at a glance. You should only need to dig deeper if you need to, and with each well described method and variable I can gain a better understanding.
Personally a = b + c is a bit lazy and I wouldn't want to have to maintain your code.
This talk on Clean code really hits the nail on the head for me when it comes to clean code - JeremyBytes Live! - Clean Code: Homicidal Maniacs Read Code, Too! - YouTube[^]
|
|
|
|
|
Super Lloyd wrote: 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...
A huge mistake many developers make is thinking of the code as "my code". It is not. It is your employer's code which you are paid to write. As with most other jobs, you are paid to do what your employer wants, not what you want.
If the coding standard is to not use 1 character variable names, then it's the programmer's job to do what they are paid to do.
That said, the feedback provided was useless. Making an assumption, the feedback should have been "use variable names descriptive of the situation".
I've suffered the good, the bad, and the ugly with code reviews. The truly bad was sitting in a room for 8 hours with 10 developers, literally reading and critiquing EVERY line of code. The lead developer had no understanding of what the goal was and he was not one to accept anything remotely resembling criticism.
The best? Reviewers were provided with the code and instructions to identify violations of the coding standard, places where the processing was not clear, and suggest corrections. Review of 1,000 lines of C took about 30 minutes with 3 reviewers, as the few problems identified were diagnosed before the meeting so in meeting it was a matter of reach agreement.
|
|
|
|
|
why?
Because I am a software mechanic (engineer), and my first reaction is: "Who the F... wrote this?"
You will learn over time that a good code review by your best colleagues will preserve your reputation, and people like me won't have that kind of reaction when we look at your code.
"That's enough for me, please pass the album cover..."
 ![Java | [Coffee]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/coffee.gif)
~d~
|
|
|
|
|
I would have thought the use of these names could be defended as "The scope of the name x was exactly two lines. It was used to make the code lines shorter and more readable."
|
|
|
|
|
I actually agree with you. The property name of "Value" makes sense as it's likely part of a larger class that has an outputted value. it's what I would look for browsing the class definition.
The 'x' variable is used in such a short space, that's it's fine by me, since Calculation should have the definition for it's return value. a longer name would take longer to read, and add more noise to something so simple.
A long time ago, I also subscribed to long variable names. like 'for' loops I used to us 'xloop', 'yloop', 'zloop'. but that was stupid, turned out it was way more 'noise' than worth while and started keeping the code cleaner like i, j, k..
for(int xloop =0;xloop<max; xloop++){total += data[xloop]}
or
for(int i=0;i<max; i++){total += data[i]}
I feel the second is way more easy to read. now if the variable was used over 10 or so lines, I would likely give it a much more meaningful name. but I look for clarity over hard rules.
Especially being a little dyslexic, the easier to read the better.
I once worked with a developer that would have written it like:
for(int intCounterForAccumulationLoop=0;i<maximumCountOfTheArrayBeingProcessed; intCounterForAccumulationLoop++){totalAmmountOfAccumulationFromTheDataArray += data[intCounterForAccumulationLoop]}
All three produce the same output, but the last one was by far the hardest to read and understand what was going on.
|
|
|
|
|
Put yourself in the imaginary position that you're someone who didn't write the code and has to understand what the author intended in order to be able to extend the functionality. It has to be understandable at the very first glance as if you were reading a book, because otherwise it's gonna take you hours because you get stuck every 1 1/2 lines and have to stop reading and try to guess: What does the author mean by "x"? The x axis? A cross? What does he mean by "cmp"? Component? Computer? Compare?
From that point of view, it should be obvious that it's kind of rude to treat other programmers like that. No?
|
|
|
|
|
Exactly, for me the change make it harder to understand.
Obviously people dont put themselves in my shoes.
|
|
|
|
|
|
Interesting critique of ITER. However, it misses one important point. Fusion power plants, assuming we ever manage to control the reaction, will have to be designed differently simply because they'll have a different output requirement from ITER. As the author points out multiple times, ITER is a research project and not designed to generate power. Fusion power will have to build on what's learned by ITER and other research facilities but they'll have a different goal - to produce power.
Where I think the author is right is in something he implied - fusion research so far has been nothing more than learning how to manage and control high temperature/high pressure plasmas.
|
|
|
|
|
The proud declaration “ITER will produce 500 megawatts of output power with an input power of 50 megawatts” as the author explains is a falsehood This suggests to me the project is corrupt and therefore doomed
A successful fusion power plant will of course have to be designed differently from ITER as according to the author ITER is doomed to failure due to its many "irremediable drawbacks"
Perhaps inertial confinement will succeed - 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
|
|
|
|
|
So because the first one that actually has a chance of working will be a messy, expsensive, oversized string and duct tape affair that probably won't live up to the hyperbole, we should not bother?
Imagine if the Wright brothers felt the same.
cheers
Chris Maunder
|
|
|
|
|
Well, the guy waiting for his bicycle to be repaired certainly felt that way. 
|
|
|
|
|
Perhaps instead of "irremediable drawbacks" I should have said "apparent irremediable drawbacks which perhaps will be overcome in one-hundred or two-hundred or three-hundred years"
I am all for research of course I would be kinder to ITER if instead of their bold false deliberately misleading claim of unlimited energy they instead proclaimed "Maybe in a few hundred years this will work" Hopefully by then we will be running on wind solar tidal and who know what else Perhaps ITER will be useful then so yes we should press on with it but some honesty of ITERs' part would be appreciated - 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
|
|
|
|
|
I currently have the Power Pavilion, but as it is on its last legs after 4 years of loyal service (including a self-done battery replacement that has left the video a bit shaky  ), it's time for me to get replacement. It seems that the Wikipedia article for the Envy says that it is the successor to the Pavilion, and I suppose that the Envy models that have a gaming video card are basically the Power Pavilion.
I should say that I am a dedicated HP user - not because I like the current company (which is not as bad since Carly Fiorina got fired), but because it seems to have the only touch pad (that I know of) that allows for physical depressment. I also like that it is a fully American company as I can complain about setting it up in English (I always buy mine abroad so as to get a combo-Cyrillic keyboard).
On a side note, I see that all notebooks seem to come with a SSD drive. Is this more reliable than the HDD? Is it recoverable if it goes down, so I need to do an emergency excision of the drive for a new system?
|
|
|
|
|
If the notebook does not come with a M.2 NVMe SSD: Stay away: It's old stock on the way out. NVMe SSDs are many - many times faster than old HDDs or even old SATA SSDs. They plug directly into the PCIe bus, so they are not limited by the slow speed of old serial SATA buses. PCIe buses transmit up to 16 bits in parallel. SATA transmits one bit at a time in a serial stream. You do the math! I have used several Samsung NVMes for several years without a single failure. Good luck!
PCIe lanes explained - how many do you need on a motherboard?[^]
Get me coffee and no one gets hurt!
modified 6-Sep-21 19:41pm.
|
|
|
|
|
If you're going to tell someone to do that math; at least do it vaguely right.
A. m.2 is a maximum of 4 PCIe lanes wide.
B. That's only half the equation though; you also have to factor in the bit rate (PCIe3 is about 1.5x as fast/lane as SATA, PCIe4 about 3x as fast; but AFAIK still uncommon on laptops due to diminishing returns and power consumption).
Telling someone to do the math also ignores the fact that:
- The main advantage of SSDs vs spinning rust is in random IO where the former doesn't have to do a 10ms seek before starting to read; or that within SSDs.
- The main advantage of PCIe vs SATA is that the NVME interface was designed around how SSDs function not how HDDs do and is much more efficient as a result.
- Low end PCIe SSDs are nowhere near as fast.
VI. But I wouldn't have bothered posting B-5 if it wasn't for the  level mistake of A.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
|
|
|
|
|
I have tested the relative speed for NVMes versus traditional SATA SSDs. NVMes are much much faster, especially when reading or writing large files. When dealing with a large number of smaller files, the difference becomes much less significant. By the way, I tested only Samsung products of both types.
That is what is important: The relative speed, not the number of PCIe lanes they occupy.
Get me coffee and no one gets hurt!
|
|
|
|
|
I have an HP Envy, but it's a printer!?!?
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated.
|
|
|
|
|
Everyone buys HPs today. Dell tripped and Hp overtook them.
All computers are now made as cheap as possible in china.
Backup all drives SSDs or otherwise with an imager like Acronis or others to a usb drive religiously unless you fancy reinstalling you dev environment brick by brick more than once.
|
|
|
|
|
I splashed out and replaced my 9 year old huge tower PC with an HP EliteDesk 800 G5 Mini with i7 at the beginning of the year.
While, at times, the fan can be audible I am very happy with it, it's nice to have the space back too.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
I don't know about successor. I've had an HP Envy m7 laptop for about 6 years. It had pretty good specs when I bought it for only $700 and I upgraded the OS and the HDD twice since then...once cloning to a 480GB SSD (huge improvement), then a clean install on a 1TB SSD. (another huge improvement)
After all these years, it's still a great laptop that is still snappy and actually compiles faster than my 3y/0 desktop system with better specs. I'd recommend it or a successor but would also advise for a clean install on the biggest SSD I could afford before actually loading it with dev components.
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
