|
|
|
|
|
Mr Musk's satelliets, may be.
|
|
|
|
|
Sloppy orchestra for the hard worker (9)
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
modified 5-Nov-20 4:16am.
|
|
|
|
|
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
|
|
|
|