Are the posted questions getting worse?

Question

Are the posted questions getting worse?

Viewing 15 posts - 46,696 through 46,710 (of 66,712 total)

You must be logged in to reply to this topic. Login to reply

Sioban Krzywicki One Orange Chip Points: 27770 More actions · Answer 1

Steve Thompson-454462 (12/22/2014)
Brandie Tarvin (12/16/2014)
But still... To my mind, since I'm already fixing one part of the package, why shouldn't I proactively fix the rest of it to make sure the other 6 procs and ETL paths do NOT become a problem down the road?
Or am I just being too efficient?
I'm in your corner, Brandie. In my experience opportunities to pay down technical debt through refactoring can be so difficult to come by (getting approval for them, finding time for them, etc.) that when the window is open you should try to cram as much through as possible. I suppose one consideration might be the scope of the testing required before the changes can be released into production, but if the code is passing all tests why not release it?

When did we all start calling rewriting/reworking code "refactoring"?

--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams

Steve Thompson-454462 SSCrazy Points: 2624 More actions · Answer 2

Stefan Krzywicki (12/22/2014)
Steve Thompson-454462 (12/22/2014)
Brandie Tarvin (12/16/2014)
But still... To my mind, since I'm already fixing one part of the package, why shouldn't I proactively fix the rest of it to make sure the other 6 procs and ETL paths do NOT become a problem down the road?
Or am I just being too efficient?
I'm in your corner, Brandie. In my experience opportunities to pay down technical debt through refactoring can be so difficult to come by (getting approval for them, finding time for them, etc.) that when the window is open you should try to cram as much through as possible. I suppose one consideration might be the scope of the testing required before the changes can be released into production, but if the code is passing all tests why not release it?
When did we all start calling rewriting/reworking code "refactoring"?

I'm using that term here to describe changes to a code base that affect/improve the implementation but do not change the result/output. Per Martin Fowler (http://martinfowler.com/books/refactoring.html) it usually consists of a series of small changes so maybe applying it to large overhaul of a system is bit of a misnomer.

Sioban Krzywicki One Orange Chip Points: 27770 More actions · Answer 3

Steve Thompson-454462 (12/22/2014)
Stefan Krzywicki (12/22/2014)
Steve Thompson-454462 (12/22/2014)
Brandie Tarvin (12/16/2014)
But still... To my mind, since I'm already fixing one part of the package, why shouldn't I proactively fix the rest of it to make sure the other 6 procs and ETL paths do NOT become a problem down the road?
Or am I just being too efficient?
I'm in your corner, Brandie. In my experience opportunities to pay down technical debt through refactoring can be so difficult to come by (getting approval for them, finding time for them, etc.) that when the window is open you should try to cram as much through as possible. I suppose one consideration might be the scope of the testing required before the changes can be released into production, but if the code is passing all tests why not release it?
When did we all start calling rewriting/reworking code "refactoring"?
I'm using that term here to describe changes to a code base that affect/improve the implementation but do not change the result/output. Per Martin Fowler (http://martinfowler.com/books/refactoring.html) it usually consists of a series of small changes so maybe applying it to large overhaul of a system is bit of a misnomer.

I'm just hearing it all the time now about any code rewrite or mod & I don't remember hearing it before this year.

--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams

jasona.work SSC Guru Points: 50117 More actions · Answer 4

Stefan Krzywicki (12/22/2014)
Steve Thompson-454462 (12/22/2014)
Stefan Krzywicki (12/22/2014)
Steve Thompson-454462 (12/22/2014)
Brandie Tarvin (12/16/2014)
But still... To my mind, since I'm already fixing one part of the package, why shouldn't I proactively fix the rest of it to make sure the other 6 procs and ETL paths do NOT become a problem down the road?
Or am I just being too efficient?
I'm in your corner, Brandie. In my experience opportunities to pay down technical debt through refactoring can be so difficult to come by (getting approval for them, finding time for them, etc.) that when the window is open you should try to cram as much through as possible. I suppose one consideration might be the scope of the testing required before the changes can be released into production, but if the code is passing all tests why not release it?
When did we all start calling rewriting/reworking code "refactoring"?
I'm using that term here to describe changes to a code base that affect/improve the implementation but do not change the result/output. Per Martin Fowler (http://martinfowler.com/books/refactoring.html) it usually consists of a series of small changes so maybe applying it to large overhaul of a system is bit of a misnomer.
I'm just hearing it all the time now about any code rewrite or mod & I don't remember hearing it before this year.

Perhaps you need to refactor your process of learning new buzzwords?

:hehe:

Sioban Krzywicki One Orange Chip Points: 27770 More actions · Answer 5

jasona.work (12/22/2014)
Stefan Krzywicki (12/22/2014)
Steve Thompson-454462 (12/22/2014)
Stefan Krzywicki (12/22/2014)
Steve Thompson-454462 (12/22/2014)
Brandie Tarvin (12/16/2014)
But still... To my mind, since I'm already fixing one part of the package, why shouldn't I proactively fix the rest of it to make sure the other 6 procs and ETL paths do NOT become a problem down the road?
Or am I just being too efficient?
I'm in your corner, Brandie. In my experience opportunities to pay down technical debt through refactoring can be so difficult to come by (getting approval for them, finding time for them, etc.) that when the window is open you should try to cram as much through as possible. I suppose one consideration might be the scope of the testing required before the changes can be released into production, but if the code is passing all tests why not release it?
When did we all start calling rewriting/reworking code "refactoring"?
I'm using that term here to describe changes to a code base that affect/improve the implementation but do not change the result/output. Per Martin Fowler (http://martinfowler.com/books/refactoring.html) it usually consists of a series of small changes so maybe applying it to large overhaul of a system is bit of a misnomer.
I'm just hearing it all the time now about any code rewrite or mod & I don't remember hearing it before this year.
Perhaps you need to refactor your process of learning new buzzwords?
:hehe:

Oh how I hate buzzwords. "Proactive" still bugs me.

--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams

Jeff Moden SSC Guru Points: 1004329 More actions · Answer 6

Stefan Krzywicki (12/22/2014)
jasona.work (12/22/2014)
Stefan Krzywicki (12/22/2014)
Steve Thompson-454462 (12/22/2014)
Stefan Krzywicki (12/22/2014)
Steve Thompson-454462 (12/22/2014)
Brandie Tarvin (12/16/2014)
But still... To my mind, since I'm already fixing one part of the package, why shouldn't I proactively fix the rest of it to make sure the other 6 procs and ETL paths do NOT become a problem down the road?
Or am I just being too efficient?
I'm in your corner, Brandie. In my experience opportunities to pay down technical debt through refactoring can be so difficult to come by (getting approval for them, finding time for them, etc.) that when the window is open you should try to cram as much through as possible. I suppose one consideration might be the scope of the testing required before the changes can be released into production, but if the code is passing all tests why not release it?
When did we all start calling rewriting/reworking code "refactoring"?
I'm using that term here to describe changes to a code base that affect/improve the implementation but do not change the result/output. Per Martin Fowler (http://martinfowler.com/books/refactoring.html) it usually consists of a series of small changes so maybe applying it to large overhaul of a system is bit of a misnomer.
I'm just hearing it all the time now about any code rewrite or mod & I don't remember hearing it before this year.
Perhaps you need to refactor your process of learning new buzzwords?
:hehe:
Oh how I hate buzzwords. "Proactive" still bugs me.

So be proactively efficient in producing a holistic and robust environment by fully redacting the code in a highly manageable and agile-like manner. 😀

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Jeff Moden SSC Guru Points: 1004329 More actions · Answer 7

... OR... you just fix the crap code you found and celebrate with a beer and a chew. 😀

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Jeff Moden SSC Guru Points: 1004329 More actions · Answer 8

GilaMonster (12/22/2014)
Someone, please, help! http://www.sqlservercentral.com/Forums/Topic1645843-1549-1.aspx

Heh... WHAT? Nah... he doesn't need any help. He only lost 1 day of business. :-):-D:-P

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 9

... Mark one off, 67 days on the calendar to go. 67 days on the calendar to go, 67 days to go, ...

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 10

Jeff Moden (12/22/2014)
GilaMonster (12/22/2014)
Someone, please, help! http://www.sqlservercentral.com/Forums/Topic1645843-1549-1.aspx
Heh... WHAT? Nah... he doesn't need any help. He only lost 1 day of business. :-):-D:-P

Wrong target. I need the help after that thread 😀

That's about the 5th person at the moment posting threads about AGs, mirroring or other HA/DR without a clue as to what they're doing or why they'd use it. Whatever happened to 'right tool for the job'?

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Eirikur Eiriksson SSC Guru Points: 182911 More actions · Answer 11

Jeff Moden (12/22/2014)
Stefan Krzywicki (12/22/2014)
jasona.work (12/22/2014)
Stefan Krzywicki (12/22/2014)
Steve Thompson-454462 (12/22/2014)
Stefan Krzywicki (12/22/2014)
Steve Thompson-454462 (12/22/2014)
Brandie Tarvin (12/16/2014)
But still... To my mind, since I'm already fixing one part of the package, why shouldn't I proactively fix the rest of it to make sure the other 6 procs and ETL paths do NOT become a problem down the road?
Or am I just being too efficient?
I'm in your corner, Brandie. In my experience opportunities to pay down technical debt through refactoring can be so difficult to come by (getting approval for them, finding time for them, etc.) that when the window is open you should try to cram as much through as possible. I suppose one consideration might be the scope of the testing required before the changes can be released into production, but if the code is passing all tests why not release it?
When did we all start calling rewriting/reworking code "refactoring"?
I'm using that term here to describe changes to a code base that affect/improve the implementation but do not change the result/output. Per Martin Fowler (http://martinfowler.com/books/refactoring.html) it usually consists of a series of small changes so maybe applying it to large overhaul of a system is bit of a misnomer.
I'm just hearing it all the time now about any code rewrite or mod & I don't remember hearing it before this year.
Perhaps you need to refactor your process of learning new buzzwords?
:hehe:
Oh how I hate buzzwords. "Proactive" still bugs me.
So be proactively efficient in producing a holistic and robust environment by fully redacting the code in a highly manageable and agile-like manner. 😀

Cannot help it, this to me sounds like an oxymoron

😎

jasona.work SSC Guru Points: 50117 More actions · Answer 12

Aanndd here comes the spam again...

Including some with titles that look like they might be "real" posts, until you hover and get the first couple lines...

Ed Wagner SSC Guru Points: 287026 More actions · Answer 13

Eirikur Eiriksson (12/23/2014)
Jeff Moden (12/22/2014)
Stefan Krzywicki (12/22/2014)
jasona.work (12/22/2014)
Stefan Krzywicki (12/22/2014)
Steve Thompson-454462 (12/22/2014)
Stefan Krzywicki (12/22/2014)
Steve Thompson-454462 (12/22/2014)
Brandie Tarvin (12/16/2014)
But still... To my mind, since I'm already fixing one part of the package, why shouldn't I proactively fix the rest of it to make sure the other 6 procs and ETL paths do NOT become a problem down the road?
Or am I just being too efficient?
I'm in your corner, Brandie. In my experience opportunities to pay down technical debt through refactoring can be so difficult to come by (getting approval for them, finding time for them, etc.) that when the window is open you should try to cram as much through as possible. I suppose one consideration might be the scope of the testing required before the changes can be released into production, but if the code is passing all tests why not release it?
When did we all start calling rewriting/reworking code "refactoring"?
I'm using that term here to describe changes to a code base that affect/improve the implementation but do not change the result/output. Per Martin Fowler (http://martinfowler.com/books/refactoring.html) it usually consists of a series of small changes so maybe applying it to large overhaul of a system is bit of a misnomer.
I'm just hearing it all the time now about any code rewrite or mod & I don't remember hearing it before this year.
Perhaps you need to refactor your process of learning new buzzwords?
:hehe:
Oh how I hate buzzwords. "Proactive" still bugs me.
So be proactively efficient in producing a holistic and robust environment by fully redacting the code in a highly manageable and agile-like manner. 😀
Cannot help it, this to me sounds like an oxymoron
😎

Don't forget to achieve synergy between teams when implementing your holistic efficiencies. Or, like Jeff said, just fix the crap.

Tally Tables - Performance Personified
String Splitting with True Performance
Best practices on how to ask questions

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 14

http://www.sqlservercentral.com/Forums/Topic1646163-391-1.aspx

I'll just be in the corner sobbing softly...

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Luis Cazares SSC Guru Points: 183706 More actions · Answer 15

GilaMonster (12/23/2014)
http://www.sqlservercentral.com/Forums/Topic1646163-391-1.aspx
I'll just be in the corner sobbing softly...

Smile, you're on Candid Camera. 😀

Luis C.
General Disclaimer:
Are you seriously taking the advice and code from someone from the internet without testing it? Do you at least understand it? Or can it easily kill your server?

How to post data/code on a forum to get the best help: Option 1 / Option 2