Need a new word mean "it worked first time and that's crazy because I just wrote the code in one hit and just compiled and ran it"
-
I'll never forget the business card I got one day from a Fluke Instrumentation salesman "If it works, it's a FLUKE" Loved it.
Psychosis at 10 Film at 11 Those who do not remember the past, are doomed to repeat it. Those who do not remember the past, cannot build upon it.
-
...but shorter, and more catchy. I've just completed about 8hrs of solid coding that involved tearing into the guts of my code, touching about 20 modules, ripping out a component and replacing it with a different (3rd party) component whose documentation is of the "documentation is Evil" variety, plus a bunch of refactoring and configuration changes and the first time I ran the code it...just...worked. Isn't that the best feeling in the world. It's like everything stops, and everything is perfect just in that moment. We need a word for it.
When that happens to me, my knee-jerk reaction is, this needs some more testing :)
-
...but shorter, and more catchy. I've just completed about 8hrs of solid coding that involved tearing into the guts of my code, touching about 20 modules, ripping out a component and replacing it with a different (3rd party) component whose documentation is of the "documentation is Evil" variety, plus a bunch of refactoring and configuration changes and the first time I ran the code it...just...worked. Isn't that the best feeling in the world. It's like everything stops, and everything is perfect just in that moment. We need a word for it.
-
...but shorter, and more catchy. I've just completed about 8hrs of solid coding that involved tearing into the guts of my code, touching about 20 modules, ripping out a component and replacing it with a different (3rd party) component whose documentation is of the "documentation is Evil" variety, plus a bunch of refactoring and configuration changes and the first time I ran the code it...just...worked. Isn't that the best feeling in the world. It's like everything stops, and everything is perfect just in that moment. We need a word for it.
The word you're looking for is in fact "holifuck"(tm)...
-
...but shorter, and more catchy. I've just completed about 8hrs of solid coding that involved tearing into the guts of my code, touching about 20 modules, ripping out a component and replacing it with a different (3rd party) component whose documentation is of the "documentation is Evil" variety, plus a bunch of refactoring and configuration changes and the first time I ran the code it...just...worked. Isn't that the best feeling in the world. It's like everything stops, and everything is perfect just in that moment. We need a word for it.
-
...but shorter, and more catchy. I've just completed about 8hrs of solid coding that involved tearing into the guts of my code, touching about 20 modules, ripping out a component and replacing it with a different (3rd party) component whose documentation is of the "documentation is Evil" variety, plus a bunch of refactoring and configuration changes and the first time I ran the code it...just...worked. Isn't that the best feeling in the world. It's like everything stops, and everything is perfect just in that moment. We need a word for it.
-
...but shorter, and more catchy. I've just completed about 8hrs of solid coding that involved tearing into the guts of my code, touching about 20 modules, ripping out a component and replacing it with a different (3rd party) component whose documentation is of the "documentation is Evil" variety, plus a bunch of refactoring and configuration changes and the first time I ran the code it...just...worked. Isn't that the best feeling in the world. It's like everything stops, and everything is perfect just in that moment. We need a word for it.
How about FIGJAM (Elephant I'm good, just ask me)?
-
...but shorter, and more catchy. I've just completed about 8hrs of solid coding that involved tearing into the guts of my code, touching about 20 modules, ripping out a component and replacing it with a different (3rd party) component whose documentation is of the "documentation is Evil" variety, plus a bunch of refactoring and configuration changes and the first time I ran the code it...just...worked. Isn't that the best feeling in the world. It's like everything stops, and everything is perfect just in that moment. We need a word for it.
Simple word: lie. More complex: It really didn't happen that way but I just want to piss all of you off.
-
...but shorter, and more catchy. I've just completed about 8hrs of solid coding that involved tearing into the guts of my code, touching about 20 modules, ripping out a component and replacing it with a different (3rd party) component whose documentation is of the "documentation is Evil" variety, plus a bunch of refactoring and configuration changes and the first time I ran the code it...just...worked. Isn't that the best feeling in the world. It's like everything stops, and everything is perfect just in that moment. We need a word for it.
First, congratulations on a job well done! Archimedes had the perfect word centuries ago. Eureka - the sudden, unexpected realization of the solution to a problem. You coded a solution to a problem - it ran the first time -- an unexpected realization. Eureka!!!!! :-D
-
...but shorter, and more catchy. I've just completed about 8hrs of solid coding that involved tearing into the guts of my code, touching about 20 modules, ripping out a component and replacing it with a different (3rd party) component whose documentation is of the "documentation is Evil" variety, plus a bunch of refactoring and configuration changes and the first time I ran the code it...just...worked. Isn't that the best feeling in the world. It's like everything stops, and everything is perfect just in that moment. We need a word for it.
-
...but shorter, and more catchy. I've just completed about 8hrs of solid coding that involved tearing into the guts of my code, touching about 20 modules, ripping out a component and replacing it with a different (3rd party) component whose documentation is of the "documentation is Evil" variety, plus a bunch of refactoring and configuration changes and the first time I ran the code it...just...worked. Isn't that the best feeling in the world. It's like everything stops, and everything is perfect just in that moment. We need a word for it.
Woaw, working 8 hours ... ... in a row without any intermediate point to see whether the code will work ... and ending the session with a run that you expect to crash and to debug that is really too much for me, now that I'm used to 5 mins cycles with refactoring and TDD I'm not amazed but sorry for you :-(
gzo
-
Woaw, working 8 hours ... ... in a row without any intermediate point to see whether the code will work ... and ending the session with a run that you expect to crash and to debug that is really too much for me, now that I'm used to 5 mins cycles with refactoring and TDD I'm not amazed but sorry for you :-(
gzo
That's kind of like being frustrated that when you take you car in for an engine change they can't take the car around the block every half hour to make sure it still works. Sometimes changes can be big.