|
Sloppy (anag)
orchestra ORCHESTRA
for the hard worker
CARTHORSE
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Wouldn't have wanted to come up against you at the O.K. Corral 
Was about about to post the same thing.
// TODO: Insert something here
|
|
|
|
|
Just as I felt when creating these clues...
Your turn tomorrow!
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
Is there a name for when your application / project gets to a stage where implementing a new feature is basically copying and pasting an existing part / components and renaming a few things. Where you basically have almost everything you need in the project in some form and can just copy / reuse?
|
|
|
|
|
DevCops?
// TODO: Insert something here
|
|
|
|
|
|
EOL
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
|
I wouldn't know; that has never happened to me.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Not even when doing CRUD interfaces? The first one may take a while, but the second goes quicker, the third even more as you reuse components, etc.
|
|
|
|
|
There might be some boilerplate code that can be re-used, but most of the implementation is custom.
We appear to work on different types of projects...
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
|
Amateurs copy and paste; pros refactor and write generic code.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
Or use reusable components 
|
|
|
|
|
Agreed, time to refactor,
|
|
|
|
|
I don't think there's a name for it, but I do this often. If I had to call it anything it would be 'templating'.
Sometimes, even the project itself may become a template for future projects.
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
ya thats called.. when you build a project that is a whole framework... when the support or customer need a new feature you just add a new control file modify the menu code .. add a new object to the class .... etc etc ... its called version 2.. don't forget the test cases
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
|
Not sure if it is exactly the same but I would normally call it good architecture.
I don't achieve this that often but reuse of existing classes and ease of modifications is often the result of good architecture.
It is like that the mods have been predicted.
It is nice when it happens.
Makes you feel like you know what you are doing.
Good code is always better to work with.
Sometimes we do it and some times we don't.
But when it is thought out properly the architecture is there to help us.
That's my 2 cents
"Rock journalism is people who can't write interviewing people who can't talk for people who can't read." Frank Zappa 1980
|
|
|
|
|
Yes. Trouble is, the requirements change every day, forcing this.
It's hard to hit a moving target.
|
|
|
|
|
I call it done, and move on.
Time is the differentiation of eternity devised by man to measure the passage of human events.
- Manly P. Hall
Mark
Just another cog in the wheel
|
|
|
|
|
The term I use is "Oh what a relief it is." or simply "Hallelujah!" or on rare occasion "I must have done something right this time." Cheerios
|
|
|
|
|
|
|
Actually this is a metric we use while developing a system.
When the majority of the "issues" are resolved with one line of code being changed.
[Now, do to formatting, a fix to a loop, that is logically a single change could count]...
But basically as code stabilizes, the amount of rework/adjustment to the existing code should decrease over time. Typically to end conditions, and such things. Resulting in fairly small changes.
It's the sign of a stable product, IMO. It is the goal. In fact, it is the goal to come out of Beta into production for us. When we are still rewriting blobs of logic, we are NOT there...
Now, the copying/pasting (refactoring) to leverage ideas from ONE area, to another area... Is conceptually similar. It usually arrives as people can EXPRESS themselves via the program itself. (Why can't we copy/paste from this grid to this grid? Why can't we get a preview button, or hover over this to see a preview like we can HERE and HERE?).
At that point, you are not debugging and fixing, you are actually improving the functionality in the direction the users want to go. THAT'S A GREAT THING. I've seen some of the most appreciated features show up in software this way. [I also believe it's why XP, and other Lightweight approaches can produce really good results quickly: They improve inter-team communication/understanding]
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
