|
|
It's not necessarily the same thing.
Just saying. 
|
|
|
|
|
we practice, but never practice at best else we'd be too tired for the actual practice and it wouldn't be the best.
Whoever phrased this survey comes directly from a Dilbert strip, please hunt it down and terminate top priority.
Geek code v 3.12
GCS 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
I use 1TBS
|
|
|
|
|
Best practices are always changing, like agreed upon diet and nutrition. One year the egg is in, next year, it causes heart disease.
Also, some engineers despise change. Best practices usually entails some effort toward change.
I think best practices should be very high-level in general, and more low-level and detailed per Company/software team.
|
|
|
|
|
Is this not a best practice?
|
|
|
|
|
Nobody cares if it works. What matters are:
is it under budget
did it ship
have we done root cause analysis
did we use patterns
is it n-tierd
did we use the latest catch-phrase practice
are we agile
Does it work? LOL - what are you, a user?
|
|
|
|
|
Urgency causes ignoring of Best Practises
|
|
|
|
|
Here is what "Best Practices" means:
I followed "best practices" so you can't blame me if they don't work.
I picked something from "best practices" so I didn't have to figure it out for myself.
As a consultant, I can sell "best practices" better than I can sell "my ideas", and I have to work less hard for my client.
So-called "best practices" are worth reviewing, but are nothing more than an idea worth looking at. If you do not have the knowledge, skills, abilities, and wisdom to look at the available knowledge base, gather information, and assemble a set of practices specific to your own situation, you are in the wrong job.
At best, "best practices" return mediocrity, at worst, disaster.
|
|
|
|
|
MSBassSinger wrote: At best, "best practices" return mediocrity, at worst, disaster.
Hear! Hear!
|
|
|
|
|
Then it turns into a fire drill.
|
|
|
|
|
In other words, the best practice should firstly check if the best practice is the right practice before spending a bunch of programming years and a $$$ AWOL...
The trouble with people,
is that they want to hear only what they want to hear.
|
|
|
|
|
I'd say that the "best practice" has to be organization (maybe app?)-dependent.
Smaller organizations or small, one-off apps don't need, and maybe can't afford, the same sorts of practices that would be appropriate to huge enterprises.
So, it's really "best practices which work for us."
|
|
|
|
|
|
My way is the best way so... I'm always following the best practices... 
Oh, and we put a lot of bacon inside the CListCtrls so you can imagine...
|
|
|
|
|
No matter how much better practice I apply to my application development cycle. There would be some part where I would be missing something, so no matter what happens there is something missing... Known as test team.
This is why, test teams are used to test the software in a way they are not meant to be used; crash them. But I always try to use the best-possible practices, in design, development, architecture etc.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
Only what I have found to be "Best" for what I do; I don't just blindly follow the crowd.
|
|
|
|
|
... are another man's "considered harmful".
But yes, we are following something that someone thinks are the best practices 
|
|
|
|
|
We are not following all SDLC life cycle stages...... 
|
|
|
|
|
|
After this much time, I don't need any more elephanting practice - I just go ahead and do it right.
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "As far as we know, our computer has never had an undetected error." - Weisert | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Care to define best practice?
There seems to be some conflict of opinion around the interwebs.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
Other times "best practices" have shown to be completely unsuitable
|
|
|
|
|
agree, and sometime close deadlines also don't let us follow.
|
|
|
|
|
It saves time in the long run - because even a trivial "one-off" app needs to work right, or you spend all day fixing it.
Do it properly, and it focuses you on what you are trying to achieve, and it works faster. And is a lot, lot easier to maintain later.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Although it's nice to aim for total compliance it's very difficult when maintaining system that have been built by many different developers over the years, each with his own version of 'best' practices.
My plan is to live forever ... so far so good
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
