|
Member 11917640 wrote: Just confirms what I am talking about.
"When you walk around with a hammer, everything looks like a nail." Abraham MaslowMember 11917640 wrote: Should I care about by brilliant member status?
If the brilliance is too blinding, put on the same glasses you wear on the glacier when you go after reindeer.
«... thank the gods that they have made you superior to those events which they have not placed within your own control, rendered you accountable for that only which is within you own control For what, then, have they made you responsible? For that which is alone in your own power—a right use of things as they appear.» Discourses of Epictetus Book I:12
|
|
|
|
|
BillWoodruff wrote: If the brilliance is too blinding
I like the way you are fighting with my brilliant brilliance.
|
|
|
|
|
Pet peeves (not in "Peevishness" order):
- Posting your homework question verbatim, and nothing else.
- Posting your whole application and expecting us to work out what bit is faulty.
- "It doesn't work" as the whole error description
- SQL Injection prone code.
- Code which is clearly copy'n'pasted from SO, hit with a hammer and still doesn't do exactly what is wanted.
- Posting all in uppercase so I'll REALLY NOTICE IT AND ANSWER IT MORE QUICKLY.
- Bumping your question because it hasn't been answered for a couple of hours. Or minutes in some cases.
- Reposting the same question over and over because you didn't like the answer.
- Spending half an hour answering a question, getting a response from the OP and being unable to respond because somebody voted the question closed because they didn't understand it.
- Messages saying "My answer is much better than yours, you should look at it"
- People who get rude because we won't do their homework.
- People who are used to Mummy doing everything for them if they order them to, scream, and shout, and expecting it to work on me.
- People who post an answer without actually trying it ...
Sent from my Amstrad PC 1640
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
The secret to answering homework questions is to provide an answer that uses advanced techniques that you're pretty sure the OP wouldn't have already been taught, and hope that if he uses your answer, the instructor will be able to determine that the student got his answer off the internet somewhere, and even better, mark the student down for not working it out on his own.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Having someone down-vote your answer after the OP makes changes to his question which renders your answer invalid.
Having someone down-vote your answer because you gave a solution to a homework question.
Having someone down-vote your answer because you vocalized a snarky response that everyone else wishes they had the balls to say themselves.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
modified 17-Jun-18 10:59am.
|
|
|
|
|
Watching John Simmons behave like someone whose prom date just jilted them because he got down-voted.
«... thank the gods that they have made you superior to those events which they have not placed within your own control, rendered you accountable for that only which is within you own control For what, then, have they made you responsible? For that which is alone in your own power—a right use of things as they appear.» Discourses of Epictetus Book I:12
|
|
|
|
|
John Simmons / outlaw programmer wrote: Having someone down-vote your answer because you vocalized a snarky response that everyone else wishes they had the balls to say themselves has the sensible reaction to keep to themselves.
This one is easily remedied.
Are you really surprised that a snarky answer would get downvoted? 
"Go forth into the source" - Neal Morse
|
|
|
|
|
After reading several dozen poorly worded, incomprehensible, code-only, or poorly described "questions", my inner snark escapes and I just gotta say something.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
|
Sadly proves nothing; need a larger sample size for a meaningful result.
This internet thing is amazing! Letting people use it: worst idea ever!
|
|
|
|
|
the foolishness of youth...i guess they never taught him never play with sharp objects period...
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
I guess I was taugth so.
But my brother in law, whose father was a lumberjack in his younger years, got a sharp lumberjack style key for his fifth birthday. "He better learn to handle it as soon as possible. And to keep it sharp." A dull knife is far more dangerous than a sharp one. And if a five year old cuts his finger, he doesn't have the force to seriously injure himself, and his body heals much faster than the body of a grown man. So let him cut himself while he is young, then he learns.
You got lots of things like that. I was out in bad snowstorm with my daughter when she was ten, and she proved that she could dress up for a snowstorm. I read enough books to her when she was little that she could handle adult themes very early (she read Umberto Eco: The name of the rose, at eleven). You can teach a six year old to swim in a cold river stream. You can early make kids familiar with visual and other information that some people think should wait until they turn eighteen; if they have encountered this sort of information is a safe and assuring framework, they will not be hurt by it.
Kids kan handle a lot more roughness than modern Western parents seem to believe today. Bringing them up to never experienced any hardship, any stress, any danger, any threat, is NOT protecting them. It is making them vulnurable.
As this is a computer based forum, I'll include a computer related story:
I am so old (and that partially explains why I am not over-protective!) that when I started my University Comp.Sci studies, we wrote our Fortran code on coding sheets, that the punching ladies wrote to card stacks, which we had to read into that huge, batch oriented mainframe. Depending on the load, turnaround was from 24 to 72 hours before we could read the compiler's error messages, so we could replace cards in the stack with corrected ones and submit for anoter 24 to 72 hours turnaround.
After Chistmas, we called for a class meeting to direct a complaint to the University, describing how bad we felt the learning environment. One of the very brightest girls in the class failed to see the problem: Why did it matter if we recieved the printoout from the run a little later? When you've solved the programming problem, the work is done, isn't it? ... After some discussion, it dawned upon us that this girl had never seen an error message, after half a year as a Comp.Sci. student - she had done everything perfectly correct on the very first try (and her handwriting on the coding form so clear that the punching ladies never made a single error transferring them to cards). Once she had left the room, one of the others made a sigh: Poor girl! and we all nodded confirmingly. If you have never been corrected by the compiler (or runtime system) in half a year, you have missed something very important!
It must be said that this girl got her share of error messages in later university courses, and she turned into a very successful and respected software designer. But hardships is a fundamental element of growing up.
Today I happen to wear a T-shirt stating: "Experience, the ability to recognize a mistake when you repeat it". I think it is relevant here.
|
|
|
|
|
Niven & Pournelle wrote:
--- Oath of Fealty "Think of it as evolution in action"
There are definitely times when the gene pool needs more chlorine. 
Sent from my Amstrad PC 1640
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Last time I wanted to test something like that, i put a piece of chainmail over a stack of hay and shot it with a crossbow.
The result: Chainmail does not help very much against bolts, arrows, spears or the pointy end of a sword. It's a bad idea to wear it while testing it.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
We've had a difficult time finding/keeping qualified applicants for a DoD contract SQL developer position. I'm astounded at our track record since November:
- We had a reasonably qualified developer for about six months, but she got fed up with the company's inability to manage her health care stuff correctly, so she quit. She had no certifications.
- Her replacement wasn't even into his third day of employment when he quit because the company he came from offered him a big pay raise to come back. I never got a chance to talk to the guy, so I don't know what his skill set was like.
- His replacement had no discernible SQL skills AT ALL, despite what he had on his resume. We let him go on Thursday, and he was only on the job for about a month.
WTF has happened to the talent pool that seems so crowded when I'm looking for a job change?
The DoD makes it very difficult to hire new IT people. They must already have a current Security+ cert (difficult to find people with this cert), and won't allow anyone access to the database server without some sort of provable training in SQL. The contract for the seat doesn't mention the SQL training part, but I suppose it will now after the last guy, in the form of a required MCSA cert for SQL developer and BIDS.
I'm the only developer supporting about 100 people, and the work is backing up, because not only do I have to service new requests, but I have to maintain years-old stuff (from as far back as SQL Server 2005) that has NO DOCUMENTATION. The last SQL dev they had wrote a bunch of SQL jobs that require annual changes every fiscal year, and created static tables that need to be updated MANUALLY "every once in a while" (determined when some app somewhere stops showing expected data).
Not only do I have to do WPF desktop apps, SQL, BIDS, and Qlikview, it's starting to look like I'll need to learn SSRS, and SharePoint, too, and I' have absolutely no interest in learning SharePoint.
On top of all of that, we expect to be updating our database server to SQL Server 2016 sometime in September (just before the new fiscal year), and we have over 300 SQL jobs to migrate. Further, there doesn't appear to be any consideration of updating tools to do the BIDS stuff. We're still on VS2013 and using VS2008 to do the ssis packages. I was hoping to have another SQL developer on staff to help out with that, but it's not looking promising.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
modified 16-Jun-18 10:13am.
|
|
|
|
|
Quote: You don't know how to ease my pain
You don't know what the sound is darlin'
It's the sound of my tears fallin'
Or is it the rain?
You don't know how to play the game
You cheat
You lie
You make me wanna cry
You make me wanna cry
Cry...
|
|
|
|
|
John knows he needs to find a better job, but he likes the misery. 
|
|
|
|
|
Yes, like artists and writers that produce their best work when they are in a state of misery 
|
|
|
|
|
Yes, I know this, but I'm over 60 and it's difficult to muster the energy (much less the desire) to go through the interview process which invariably includes pointless quizzes about esoteric constructs with fancy new names that don't really mean anything. I have become so reliant on google as a ready reference, that I have stopped trying to remember how I did something after I did it. There's just too much to know.
It seems that most jobs are only 6-months long, or they want "full stack" developers (another way of saying they don't want to hire enough people to do the job right) that can work on a technology mix that would make most real programmers wince in pain, and nine times out of ten, all they want is to hire someone long enough to clean up the last guy's mess, or to implement some tech agenda based on some idiot manager's wrong-headed view of how things should work.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Sorry, life doesn't work like that - it's all a trade off. You want a better job - you have to go through the pain. If you want to move to SoCal I have junior dev role going...  (Ducks as JSP takes aim).
Keep your friends close. Keep Kill your enemies closer.
The End
|
|
|
|
|
|
Which bit?
Keep your friends close. Keep Kill your enemies closer.
The End
|
|
|
|
|
The part where I might get to move back to SoCal.
|
|
|
|
|
Are you a junior dev? You know, where you get to "program" all the reporting?
Keep your friends close. Keep Kill your enemies closer.
The End
|
|
|
|
|
I prefer to stay in the back-end. (Can I say that in the Lounge?)
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
