|
open plan is designed to give a positive FINANCIAL outcome to the company, it is not designed for the comfort of the employees. What pisses me off is that I get paid more than the bloody managers and they still get to squirrel themselves away in an office.
I have started calling the office "the kindergarten" it is slowly getting through to some people that having high volume discussion in mandarin over my head is not conducive to getting work done!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I have earplugs for when the person who sits one desk away shouts(their normal conversation level is shouting, they do not appear to have a quiet mode). 
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
Agreed. And I think it's hilarious to have an "open office" to improve communications, yet read the # of ear plugs / head phones suggestions.
Here's your sign....
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
Only thing worst, your the only programmer in an open office call center
and having the disgusting memory of watching a person using a collapsible back scratcher.
The only solution was to leave, best move ever to keep my sanity.
|
|
|
|
|
Snap! 
Even worse when they expect you to provide Technical Support.
(Well, you're IT, aren't you?)
All that is necessary for Evil to succeed is for Good Folks to keep voting for their Party. - Cornelius Thirp
|
|
|
|
|
If your application/library/class/function has developed out of scope and can no longer be considered having the right name, when is it ok to rename it?
|
|
|
|
|
Anytime you think the name is wrong or misleading you should change it to something more obscure. 
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Rename it, but leave a wrapper sitting there that calls the newly renamed function with the old name, in case someone is still using the old name. Remove the old name from documentation.
|
|
|
|
|
_Damian S_ wrote: documentation
+++ out of cheese error +++ MELON MELON MELON +++ redo from start +++
|
|
|
|
|
|
Hi Jorgen,
I think to attempt a meaningful response to that issue requires specific knowledge of the actual context, the nature of the application, the number of programmers working on the application, its users, etc.
For example: is the application extensible so that third-party developers writing plug-ins for it might somehow be affected by any changes you make ?
A fancy way of saying: "I can't generalize" ?
« There is only one difference between a madman and me. The madman thinks he is sane. I know I am mad. » Salvador Dali
|
|
|
|
|
I started writing a much more specific post, but then I thought that I've been in this position before, and will be there again, and so I wrote a more general question in the vain hope there was a general answer to it.
Mycroft describes my position very well.
|
|
|
|
|
I get this all the time, we get a spec (verbal discussion) I attempt to get a project name/description from the business, start building, name the database, create the projects. And management decides to change the name of the project.
It is a judgement call as to the cost of re-factoring (Bill's view) and the long term impact on support. It can be confusing for the support team when the UI naming and the supporting infrastructure does not match.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
You described my problem much better than I ever could have. 
|
|
|
|
|
When it is easy, or will end up causing too much confusion later on. Sorry, my answer is as vague as your question.
|
|
|
|
|
Jörgen Andersson wrote: when is it ok to rename it
a) Wednesday
b) The last day of your employment
c) Never
d) All of the above
PooperPig - Coming Soon
|
|
|
|
|
[Obsolete("This method is older than Yoda. We have new shiny one with lightsaber")]
public void OneThousnadYerOldMethod()
{
NewShinyOne();
}
public void NewShinyOne()
{
}
Zen and the art of software maintenance : rm -rf *
Maths is like love : a simple idea but it can get complicated.
|
|
|
|
|
Jörgen Andersson wrote: If your application/library/class/function has developed out of scope and can no longer be considered having the right name, when is it ok to rename it?
a. As soon as it's out of scope and can no longer be considered having the right name, and
b. You can find a poor slob to do the code renaming, refactoring, updating of tables, updating of docs, rerouting of any old URLs that point to that name, corrections and redistribution of written material, changes to DNS, server naming, jobs and schedules, Unit tests and test data, and all those coffee cups with the old name on them.
cheers
Chris Maunder
|
|
|
|
|
That poor slob would be me, and we don't get special coffee cups over here. Can I have a CodeProject one? I promise to not touch your code.
|
|
|
|
|
Jörgen Andersson wrote: I promise to not touch fix your code.
So close, but you blew it.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
If I promised that, I'd probably blow it anyway.
Wrong is evil and must be defeated. - Jeff Ello
Any organization is like a tree full of monkeys. The monkeys on top look down and see a tree full of smiling faces. The monkeys on the bottom look up and see nothing but assholes.
|
|
|
|
|
Chris Maunder wrote: You can find a poor slob to do the code renaming, refactoring, updating of tables, updating of docs, rerouting of any old URLs that point to that name, corrections and redistribution of written material, changes to DNS, server naming, jobs and schedules, Unit tests and test data, and all those coffee cups with the old name on them to blame when problems caused by the renaming appear
FTFY
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
I don't know about library, but if it's a class, never, you simply shouldn't if it used across several systems.
You can extend it by sub-classsing and giving the child class an appropriate name.
modified 20-Oct-19 21:02pm.
|
|
|
|
|
Kamen Nik wrote: I don't know about library, but if it's a class, never, you simply shouldn't if it used across several systems.
Hence the ghost of NextStep that lingers on in every Mac and iDevice...
|
|
|
|
|
Anytime, and if a name already in use that is suitable, just append a number to the end. e.g. SomeClass2, 3, 4
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
