WTF??
-
You just have to sit back and say WTF:confused: Had meeting with my manager in which he said I don't care if my developers don't document their code or if one can't pick up where the other left off. I just want them to write code faster to keep the client happy. That was followed up by a conversation with the lead developer saying documentation is necessary in other places but we just write software here; we don't need it. :doh::confused::doh:
only two letters away from being an asset
-
You just have to sit back and say WTF:confused: Had meeting with my manager in which he said I don't care if my developers don't document their code or if one can't pick up where the other left off. I just want them to write code faster to keep the client happy. That was followed up by a conversation with the lead developer saying documentation is necessary in other places but we just write software here; we don't need it. :doh::confused::doh:
only two letters away from being an asset
Mark Nischalke wrote:
Had meeting with my manager in which he said I don't care if my developers don't document their code or if one can't pick up where the other left off. I just want them to write code faster to keep the client happy.
Yikes! Sorry to hear that. Tell him that "documentation is a value-add which frees up cycles, thus allowing us to enable our core competencies to touch base with client-facing base-touching ball-parking circle-backing ballparks who touch base with client facing core competencies, enabling us to free up cycles which add value." (phew!) :-D
:josh: My WPF Blog[^]
-
You just have to sit back and say WTF:confused: Had meeting with my manager in which he said I don't care if my developers don't document their code or if one can't pick up where the other left off. I just want them to write code faster to keep the client happy. That was followed up by a conversation with the lead developer saying documentation is necessary in other places but we just write software here; we don't need it. :doh::confused::doh:
only two letters away from being an asset
it's always one extreme or the other: no process or too much process. no rules, or too many rules.
Let's execute on the customer-facing market-driven swim-lane paradigm!
-
You just have to sit back and say WTF:confused: Had meeting with my manager in which he said I don't care if my developers don't document their code or if one can't pick up where the other left off. I just want them to write code faster to keep the client happy. That was followed up by a conversation with the lead developer saying documentation is necessary in other places but we just write software here; we don't need it. :doh::confused::doh:
only two letters away from being an asset
Mark Nischalke wrote:
You just have to sit back and say WTF
Uh huh, sure did :)
Mark Nischalke wrote:
I don't care if my developers don't document their code or if one can't pick up where the other left off. I just want them to write code faster to keep the client happy
Okay, a developer doesn't document his or her code, gets totalled in a car wreck on the way home from work, new person gets hired, how do they understand what the developer was doing and keep the client happy at the same time? Gotta document the code :)
Mark Nischalke wrote:
manager
He's probably been so BUZZWORDed (any of the buzzword dealing with the business aspect and not development) that the poor guy probably can't think straight.
-
Mark Nischalke wrote:
Had meeting with my manager in which he said I don't care if my developers don't document their code or if one can't pick up where the other left off. I just want them to write code faster to keep the client happy.
Yikes! Sorry to hear that. Tell him that "documentation is a value-add which frees up cycles, thus allowing us to enable our core competencies to touch base with client-facing base-touching ball-parking circle-backing ballparks who touch base with client facing core competencies, enabling us to free up cycles which add value." (phew!) :-D
:josh: My WPF Blog[^]
Josh Smith wrote:
documentation is a value-add which frees up cycles, thus allowing us to enable our core competencies to touch base with client-facing base-touching ball-parking circle-backing ballparks who touch base with client facing core competencies, enabling us to free up cycles which add value
X|
Josh Smith wrote:
(phew!)
:laugh::laugh::laugh:
-
Mark Nischalke wrote:
Had meeting with my manager in which he said I don't care if my developers don't document their code or if one can't pick up where the other left off. I just want them to write code faster to keep the client happy.
Yikes! Sorry to hear that. Tell him that "documentation is a value-add which frees up cycles, thus allowing us to enable our core competencies to touch base with client-facing base-touching ball-parking circle-backing ballparks who touch base with client facing core competencies, enabling us to free up cycles which add value." (phew!) :-D
:josh: My WPF Blog[^]
Wow, I'm impressed and confused ;P
only two letters away from being an asset
-
Wow, I'm impressed and confused ;P
only two letters away from being an asset
Mark Nischalke wrote:
Wow, I'm impressed and confused
Exactly. That might help you get what you want out of him. ;)
:josh: My WPF Blog[^]
-
Wow, I'm impressed and confused ;P
only two letters away from being an asset
Mark Nischalke wrote:
confused
Never mind, didn't realize it was about Josh's post. I am impressed with it as well, and a little confused by it. I am sure it would put a manager into a loop that never breaks :)
-
You just have to sit back and say WTF:confused: Had meeting with my manager in which he said I don't care if my developers don't document their code or if one can't pick up where the other left off. I just want them to write code faster to keep the client happy. That was followed up by a conversation with the lead developer saying documentation is necessary in other places but we just write software here; we don't need it. :doh::confused::doh:
only two letters away from being an asset
Mark Nischalke wrote:
only two letters away from being an asset
Love it!
cheers, Chris Maunder
CodeProject.com : C++ MVP
-
Mark Nischalke wrote:
confused
Never mind, didn't realize it was about Josh's post. I am impressed with it as well, and a little confused by it. I am sure it would put a manager into a loop that never breaks :)
Sorry, I meant it to be for Josh's post
only two letters away from being an asset
-
Sorry, I meant it to be for Josh's post
only two letters away from being an asset
You wrote: Sorry, I meant it to be for Josh's post No problem. After the dust settled from Josh's post, I figure it out :laugh:
-
Mark Nischalke wrote:
only two letters away from being an asset
Love it!
cheers, Chris Maunder
CodeProject.com : C++ MVP
Actually had someone use that on me. Always remembered it. He didn't like my reply though. Kiss my asset ;P
only two letters away from being an asset
-
Mark Nischalke wrote:
Wow, I'm impressed and confused
Exactly. That might help you get what you want out of him. ;)
:josh: My WPF Blog[^]
I got what I wanted out of him. Signing my time sheet as I walked out the door ;P
only two letters away from being an asset
-
You just have to sit back and say WTF:confused: Had meeting with my manager in which he said I don't care if my developers don't document their code or if one can't pick up where the other left off. I just want them to write code faster to keep the client happy. That was followed up by a conversation with the lead developer saying documentation is necessary in other places but we just write software here; we don't need it. :doh::confused::doh:
only two letters away from being an asset
Leave. Now.
Jon Sagara When I grow up, I'm changing my name to Joe Kickass! My Site | My Blog | My Articles
-
Leave. Now.
Jon Sagara When I grow up, I'm changing my name to Joe Kickass! My Site | My Blog | My Articles
I did
only two letters away from being an asset
-
Actually had someone use that on me. Always remembered it. He didn't like my reply though. Kiss my asset ;P
only two letters away from being an asset
Mark Nischalke wrote:
He didn't like my reply though.
And what happened? Could he not handle the truth?
-
You just have to sit back and say WTF:confused: Had meeting with my manager in which he said I don't care if my developers don't document their code or if one can't pick up where the other left off. I just want them to write code faster to keep the client happy. That was followed up by a conversation with the lead developer saying documentation is necessary in other places but we just write software here; we don't need it. :doh::confused::doh:
only two letters away from being an asset
Mark Nischalke wrote:
Had meeting with my manager in which he said I don't care if my developers don't document their code or if one can't pick up where the other left off. I just want them to write code faster to keep the client happy.
Sounds like my office. When I first started working I asked for the documentation and they said the code was the documentation!
-
Mark Nischalke wrote:
Had meeting with my manager in which he said I don't care if my developers don't document their code or if one can't pick up where the other left off. I just want them to write code faster to keep the client happy.
Sounds like my office. When I first started working I asked for the documentation and they said the code was the documentation!
That disappoints me. One of the arguements here against documentation was, no one else does it. To which my reply was, yes they do. You've proven me wrong.:(( There is nothing left to do but give up on life :^):sigh: I'd use VB and code myself a knife, but it wouldn't do the job; it won't be very # you C ;P
only two letters away from being an asset
-
That disappoints me. One of the arguements here against documentation was, no one else does it. To which my reply was, yes they do. You've proven me wrong.:(( There is nothing left to do but give up on life :^):sigh: I'd use VB and code myself a knife, but it wouldn't do the job; it won't be very # you C ;P
only two letters away from being an asset
Mark Nischalke wrote:
To which my reply was, yes they do. You've proven me wrong.
Hmmm, if it makes you feel better, I document all of my code and would not be caught with undocumented code. There is the idea of self-documenting code, but I am not sure about it. Does it really hurt to document the code. Come on, a comment every 3-5 lines or so can't really kill anyone.
-
Mark Nischalke wrote:
To which my reply was, yes they do. You've proven me wrong.
Hmmm, if it makes you feel better, I document all of my code and would not be caught with undocumented code. There is the idea of self-documenting code, but I am not sure about it. Does it really hurt to document the code. Come on, a comment every 3-5 lines or so can't really kill anyone.
PaulC1972 wrote:
Come on, a comment every 3-5 lines or so can't really kill anyone.
I agree. The arguement here was, "We don't have time for that". Again, WTF???:confused:
only two letters away from being an asset