|
I think Amazon already lowered the bar with their $60/year for unlimited storage. Quite useful if you have millions of photos and videos of your family vacations or the kids doing kid stuff.
The catch is, you can't automatically synchronize data without using a third-party tool.
|
|
|
|
|
is what i currently think. Arguing with the boss and insiting on my opinion is something i have never done before, now i can't get it out of my head.
Usually i tried to meet everyones needs but on this point i won't discuss. I know some of you have years/tons of experience, can you remember the first time you put a wooden board on your bosses forehead?
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Five minutes after met him...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
DId you meet him again XD
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
If you believe strongly that you're idea is the way to go, then present it, even strongly, but in the it's up to him/her to make the decision.
I used to be very foreceful when I thought I was right, and many times I WAS right... but that doesn't mean they're going to see it your way.
Then I learned a lesson... unless you work for you, then the software isn't yours... so make the recommendation, reinforce your position if you need to, then let it go. This is how you get it out of your head.. Let it go.
If it comes back later that you we're right, then great... but if later it's determined that your idea was totally wrong, then you would have looked like a fool for taking it to far.
In short, research your position, present it, then walk away.
If it's not broken, fix it until it is
|
|
|
|
|
Basically I like your Statement. But I think everybody has the right to fail, otherwise the option is: doing nothing to prevent from failures.
modified 19-Jan-21 21:04pm.
|
|
|
|
|
|
In real life - if you were right, it was the boss's idea. If you were wrong, it was your idea.
Alternative scenario - if your idea was turned down and later discovered to be a good one, it magically reappears as the boss's idea.
Yes, I'm cynical, how did you guess? 
|
|
|
|
|
I have been using a variation of this to get my own way for years. First convince the boss that it is a good idea and then wait for it to be presented to you. Doesn't give you credit for the idea but if later it is discovered as a bad idea then not your fault...
|
|
|
|
|
HobbyProggy wrote: Arguing with the boss and insiting on my opinion
You are not in that position due to age, but knowledge. It is why you are hired and what you are paid for 
If the boss/customer/whatever is a software-dev, then he/she might be able to see all consequences, but if they aren't, then they are paying someone who works with the subject-matter all they. Would be weird if the boss would pay you for something he doesn't wants.
As soon as they are informed, the decision is theirs to make. And yes, that might be a very wrong one, but that is their right.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
A lot.
Ultimately it was good for my bosses, the company, and me.
I now work at another company and I still give my boss my 2 cents when I deem it necessary.
Out of the four bosses I've had only one didn't take the "advice" I gave very well.
Then again, our customers had trouble with that guy as well
|
|
|
|
|
As others have said, it is your job to argue with the boss on the subject you are hired to know. Up to a point, then you do as required.
I learnt this when I was sacked for flatly refusing to write a console application to clean the registry in VB5.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I too did it with the CEO at the time. I had a lot of witness. The guy was only 4-5 years older.
He blatantly stole my idea that had been floated around. And when I called him on
it 'He told me to I didn't know what i was doing and
that he had been programming since I was in diapers.' He would have been 5 and still using punch cards.
It's amazes me that people can't look at both sides and make a correct decision.
That's why he gets paid the big bucks.
You have to decide are you happy where you are?
Can you find a another job?
The grass isn't always greener but its about being happy every day.
Today is my birthday and I am happy.
Not working but happy.
|
|
|
|
|
Happy Birthday then ![Beer | [beer]](https://codeproject.freetls.fastly.net/script/Forums/Images/beer.gif)
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
In my experience, do as the others have said. Present your side with as many facts as possible while being as diplomatic as possible without pushing too hard. But at the end of the day, do as your boss says and/or do both so that if the problem you're foreseeing shows up, you can have the fix ready to go. Be sure not do the 'I told you so' bit. If you cram your way down his throat, you will more than likely foster resentment. Do your best to make your boss look good and what you'll find is that in the future he'll trust you more and you'll have a better working relationship. That's if he's a good boss. (My definition of a good boss is someone who shares the credit of success and shoulders the blame by himself while addressing the shortcomings discretely) If he's a bad boss, well, that's up to you.
|
|
|
|
|
If you are discussing your area of expertise and you were hired for it, then you give your opinion with the pros and cons of doing it or not.
Remember, you do not get the final say. You just offer your expertise on the matters. It's your boss's neck on the line with the executives running the company.
Most techs have to learn how to talk to their managers. They don't respond to the same things we do. You have to spell things out in hours of downtime, productivity increases, costs, and resources. Otherwise, their eyes glaze over.. 
Wynter
|
|
|
|
|
|
|
An interesting task would be to list down all nebulas and celestial objects named after places on Earth, like this.
|
|
|
|
|
I'm having a couple of Merlots tonight. I did Cabernet Sauvignon yesterday.
|
|
|
|
|
I'm doing dry life. Does that count? 
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
I'm trying dry wit.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I've found that the responses to my dry wit often leave me feeling deserted.
|
|
|
|
|
Only if not combined with (read: due to) fervent beliefs and a full schedule each Sunday.
|
|
|
|
|
To ensure the success of the project I ordered 2 cases of dry Vermouth...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
