Where to Start?
Okay, so recently, my company i work for stopped letting us use the best tool we had and give us one of the crappiest tool EVER. Ever tool that we ever get to use they take away or try to give a better one that doesn't work. I work for a cable company and we have tools that pull the .bin files and other information off of the modem by the mac address. However the took away are good one. I was woundering if anyone had an idea on how to start off making one in c++. I know C++ i just dont know were to start.
Dunno if Wireshark is in the ballpark, but perhaps follow-ups to this may help narrow your query.
So why not argue your case for the tools you prefer and back it up with some hard data, like how long it took you to perform certain tasks (in other words, how much money it cost the company).
I agree with Salem, decisions like this often come from people who are no longer working in the field. The only thing they see related to this tool is a license cost. And probably some advisor (who is also nolonger working in the field) of this person said we could do without.
In my opinion from what I've seen in medium size to big companies, the people at the bottom of the ladder do not communicate well enough with the people that are ranked higher. Most of the times they really are afraid to go into dicussion/conversation with the higher ranked persons... which is ridiculous as long as you can back up everything with hard data like Salem said and do it in an appropriate way.
In the end a company will only really work and stay alive if everyone contributes (hell even if its the guy that cleans the toilets).
Well, the tool we used to use was never payed full software. It was made by a person in the company that does what I do. He did it in his spare time. Now they are trying to use a software that they pay for that doesn't work wroth a damn.
So their train of thought is, "You get what you pay for", despite the fact they were paying the employee who made it. Sad situation. I'd say just ask the higher-ups for training from the company they bought it from.
Where the hell did the requirement for the bought in software come from?
You have a tool, which didn't cost the company any money (apparently), did exactly what everyone wanted, and could be changed on a moments notice to do something else.
No doubt some PHB is getting a kick-back for introducing this bought in package, because there seems to be no sane reason for choosing it. Investigate how the cost of this s/w was justified, then set about rebuking the arguments put forward.
Were you (or anyone else) asked if you needed any additional tools?
Were you (or anyone else) asked for an opinion about the proposed tool?
If the answers are 'no', then the PHB just pulled the decision out of their ass IMO.