The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Did it happen to you that a coworker refactored some (large amount?) of your code
Thankfully, I'm the only coder here for most of the last 20 years so I don't have that to worry about.
My task of the week has been putting lipstick on a pig...new interface/graphics/theme/icons for 94 forms in a legacy project. My designer made it difficult and chose a diagonal gradient and not all controls have transparency. When I get this one done, I have around 70 'add-on modules/utilities' that need rebranding. What I really need is an intern!
Not exactly, but I've once talked to a co-worker about his mess of code both convoluted and hard to debug. According to him, it's simpler this way. Turned out he learned to code in the 60s and pretty much stuck with what he learned for half a century now.
* Yes, There are multiple points of view a developer can look at a task (or a job)
* If you gives the **beeeep*** about loosing your position (job) your point of view
is the correct to take (personal risk).
* If this job is probably the only developer job you will get for the next 6 months, you have to use your Emotional Intelligence forging a way threw the difficult organizational culture (politics) and accept the risk you will get the blame for accepting/following the work some other person forced you using.
sometimes a task you get assignd to you just in order to protect someone else with better score
in the organization political structure and you have no chance surviving it....
Not so much code, but documentation I wrote. They did a lot of pointless wordsmithing - changed fonts, removed page headers, linked sentences into compound sentences using semicolons, introduced spelling errors, and removed paragraphs in places. A section they added didn't adhere to the formatting in the rest of the document at all.
Fortunately this document lives in source control. When I needed to update the document recently, I could go back to my original. I added their new section, reformatting it so that it looked like the rest. I did adopt a couple of their wording changes.
A good friend of mine, after 7 years of medical school and training has been fired for one minor indiscretion. He slept with a patient and can no longer work in the profession.
What a waste of time, effort, training and money. He's still paying on his student loans. This just goes to show that one minor mistake can ruin your life. Thoughts for him and his family. He really is a great guy and a brilliant Veterinarian.
Give me coffee to change the things I can and wine to accept the things I cannot! JaxCoder.com
Do you have people in your organization that only respond to the first question in an email?
This bugs the *shart* out of me. I took the time to compose the email. I carefully thought through the specific questions I wanted answered before communicating them... and nothing, no response other than to the first question. So, if I stopped building the application at the login screen, they would be good with that. I think not!
Maybe I should just adopt their approach? I would be able to get through more emails in a more timely manner by only answering the first question. Please note that this is the second question in my post, so feel free not to answer.
“The palest ink is better than the best memory.” - Chinese Proverb
Last Visit: 21-Jul-19 3:35 Last Update: 21-Jul-19 3:35