|
Quote: wait till the battery runs out
Remove the battery and re-install it?
|
|
|
|
|
It's non-removeable of course... 
Anything that is unrelated to elephants is irrelephant
Anonymous
-
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-
Never argue with a fool. Onlookers may not be able to tell the difference.
Mark Twain
|
|
|
|
|
The only problem I have with Win 10, is every time there is an update Windows changes my default printer. We have 3 printers on our home network. Invariably, after an update, I try to print something in color to the inkjet printer, it ends up in black & white on the laserjet. I blush to disclose: Then the color in my language makes up for the lack of color in the printed piece. 
|
|
|
|
|
You're lucky this happens only after updates.
Lately after setting up my wireless printer, it'll process exactly one print job just fine...then I have to remove/re-add/reconfigure the printer. I have to do this on every computer I try to print with, so it's gotta be the printer, not the (or any particular) computer.
Heck, I print, and then the printer's web admin page becomes unreachable. Rather frustrating.
|
|
|
|
|
glennPattonWork wrote: booted on Monday and was treating monitor 2 as 1 and 1 as 2.
Welcome to the Terran Empire! 
|
|
|
|
|
They largely code worse than I do in terms of readability, not to mention maintainability. Single line ifs, using postfix-inc in array indexer like _array[index++], and being rather fast and loose with their encapsulation, putting internal methods all over the place - I don't do that last bit at least. 
I've done fine at code reviews at MS in the past. At other shops I adopt different practices. On my own I tend to gravitate towards a combination of styles I like.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
I have low esteem for people criticising other people for their style...
(I.e. I don't value those who thought it's a noble endeavour to micromanage and waste everyone's time and good will)
It's sadly way more common that I'd like and tend to prove, in my not so humble opinion, that there are more less than average developers than I thought... Which makes sense though! There should be, like 50% of them!
|
|
|
|
|
My big thing is consistency, at least within a particular domain, and sometimes i struggle with that consistency myself.
I don't really care how your code looks as long as I can always tell you wrote it. I can get to know your coding habits. What I can't know is random cut and paste gibberish or even things written by the same developer but down the road with completely different habits.
That just makes it harder for me. Still, that's more my problem than anyone else's
The exception is when I'm a lead or something and it's my job to enforce coding standards and to run code reviews. Then I like to have a shop standard more or less developed, and we stick with that for each other's sake.
Code here? To be honest I don't "like" the style of about 90% of the code I see. But I don't care. It's really not my business how you keep house unless I'm living in it with you. That's how I see it.
And if i need to use your code, I'll stare at it until my eyes adjust. They always do.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
I think consistency is a bad overrated thing...
I don't subscribe to the idea it helps you write performant bug free code and I do believe it prevents you from learning and experimenting....
|
|
|
|
|
I agree with that to an extent, but by most accounts - assuming they're honest, I'm considered pretty creative.
But I've learned some discipline in certain areas, because it helps keep me from getting bogged down in messes instead of creating.
So I think properly applied discipline in the right areas is actually an aid to creative expression, not simply an impediment.
Consider some of the master painters. They perfected the rules of the art so they could break them *well*.
There's a difference between badly drawn perspective and cubism.
There's a difference between undisciplined coding and creative programming.
Just my $0.02
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
also.. consistency is a little bit of a vague fuzzy concept... mostly people will argue over pointless stuff like bracket and line return...
The argument for consistency is writing code is easy, reading code is harder.
Yet there is a better argument than consistency, it's write simple code. Minimize nested block, minimise recursivity, minimise everything!
Consistency is not really helping in this endless minimisation quests!
And this is the real quest to follow. NOT consistency!
ANd I much rather like creatively short code to consistently bloated one!
|
|
|
|
|
I mean, make the code as simple as it can be and no simpler.
These days I tend to code things that are by nature complicated. I'm into the compiler front end (parser) and middle stuff (type/scope resolution) these days. The code can't be that simple and still be functional.
So there's that. KISS is a good engineering principle, but it doesn't mean that all programs can be simple.
Consistency in style just means that month to month i can tell the same person wrote the code.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
Automated message Review wrote: 'ANd' - wtf001: illegal use of capital 'N' following capital 'A' and preceding lowercase 'd'
|
|
|
|
|
#pragma disable warning wtf001
|
|
|
|
|
Well, think of every reading of any of your articles as a code review.
Out of the probably thousands of readers, I'll bet some of them have some level of OCD. (Hi Sander  )
|
|
|
|
|
haha @ calling out sander.
he's young and has fire in his belly. When he gets old and jaded he'll care less about stuff like that, and more about contemplating his own mortality like the rest of us.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
While I do kind of agree with lloyd on this I must also admit that I have trouble reading what I consider to be badly formatted code.
But there is little point in complaining.
If it's my own project I reformat and rename variables. But if it's owned by someone else I'll have to adjust. That's just common courtesy.
Oh, btw, Sander has humour. He can take it.
|
|
|
|
|
sigh, I hate this discussion, meetings, forums, wasting time on style:
I say your style sucks, and you [would I'm sure] say mine sucks. so.... that makes us equal? right or not?
next item on the agenda is....
|
|
|
|
|
honey the codewitch wrote: On my own I tend to gravitate towards a combination of styles ABSOLUTE CHAOS HAIL SANTA I like.
FTFY (keeping in season spirits) 
|
|
|
|
|
I could have sworn I turned you into a newt.
Maybe i was daydreaming.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
honey the codewitch wrote: using postfix-inc in array indexer like _array[index++],
Well, array[++index] does something different than array[index++], so what's the issue with postfix when you want the index to increment after accessing the value at that index?
int[] foo = { 1, 2, 3, 4, 5 };
int i = 0;
int j = 0;
Console.WriteLine(foo[++i]);
Console.WriteLine(foo[j++]);
2
1
|
|
|
|
|
THat's rather my point, innit?
Readability and maintainability are contrary to pulling stunts like that
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
At least you don't have to fight against MISRA rules and automatic enforcers.
GCS 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
|
|
|
|
|
My three rules.
- The code must be readable to a junior dev
- The code must be correct (ie safe, efficient and actually do its job)
- The code must be consistent
I'll put up with some really, really bad coding practices if they at least follow the 3 rules. I find it intensely painful switching between modules, files or even methods to find totally different styles and assumptions. It slows down reviews and is like a pot-holed road: you get thrown around and things break.
cheers
Chris Maunder
|
|
|
|
|
On point 1 you and I are going to disagree.
I can't even read LALR(1) generation code. I can't even read the algorithm it's based off of. That's how messy the problem is.
No junior developer will be able to dissect LALR(1) table generation code. Someone with a masters in CS might recognize what it is, and be able to point out the various steps of the algorithm in the routine, but it's the algorithm itself that is the problem, not the code that implements it.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
