|
It's just a non-coding colleague an myself here, but she keeps on buying these dashboard/reporting tools...you know the ones...you just give it a database connection and you can produce pretty charts and graphs in 10 minutes. One of them was a total dead end as they decided to abandon the promise of export to html5, instead only supporting flash. After a few dead ends now, I think I'm finally getting respect for what can be done with jQuery or even native .Net charting components.
"Go forth into the source" - Neal Morse
|
|
|
|
|
As often as Stackoverflow armies of moderators veto to close threads!
So that's freq or not freq?
dev
modified 25-Nov-18 10:26am.
|
|
|
|
|
Our owners's are too cheap to buy any software
Director of Transmogrification Services
Shinobi of Query Language
Master of Yoda Conditional
|
|
|
|
|
If the technical team needs a tool, we ask our manager about it. If he approves it, we buy it. He's never proposed a tool to us.
The only tool we have 'passed down from the top' is our bug tracker, a hoary old home-grown data base app.
Software Zen: delete this;
|
|
|
|
|
Isn't that part of Never - I/we choose our own tools and products
Director of Transmogrification Services
Shinobi of Query Language
Master of Yoda Conditional
|
|
|
|
|
The original question "How often do you shoot down product to tool choices your manager / team lead presents to your team?" presupposes that your manager suggests tools. In my case, that doesn't happen.
Software Zen: delete this;
|
|
|
|
|
Got it.... Null Management Suggestions error.
Director of Transmogrification Services
Shinobi of Query Language
Master of Yoda Conditional
|
|
|
|
|
I can not be the last programmer out there working that is not part of a "Team".
I don't know anymore, I just don't. I keep getting older, and they (pretty girls, programmers, etc.) just stay the same age ....
|
|
|
|
|
Nope, I am all so. Very lonely being the only programmer in a small city government.
|
|
|
|
|
I feel the opposite. Less distractions, fewer breaks in my concentration. Also I have "control issues" and I am not very good at compromise....
The older I get the less I understand...
|
|
|
|
|
Sometimes I miss being the programming department. When you are the designer/architect, implementer and QA, the odds of bug getting through drop considerably. If, heaven forbid, one does show up, you probably know were it is before they finish explaining it. The reason I left the job was because I wrote most of the code they used and was literally going nuts due to boredom.
INTP
"Program testing can be used to show the presence of bugs, but never to show their absence." - Edsger Dijkstra
"I have never been lost, but I will admit to being confused for several weeks. " - Daniel Boone
|
|
|
|
|
I am with you. I own my company and have multiple clients through the Southeast. So, there is never enough time to get bored, between new Modification requests, new Bug reports and many clients with a slightly different version.
Also, converting from VB6 to C#, only to discover that string handling is abysmal, and dates are truly ridiculous.
Any proponent of C# who argues that VB6 is "much more verbose" is someone that has never used VB6.
Take responsibility for your actions and failure to act when you should. that is what everybody else has to live with. It's OK to make a mistake. It's not OK to try to cover it up.
|
|
|
|
|
Our tech lead has informal discussions with team members before formally asking about tools, so there's no issue there. Management rarely suggests tools, leaving that to the tech lead and dev team.
|
|
|
|
|
We can choose, as long as it's already on the "approved software list".
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I was really expecting an answer from you that keyed off of "shooting down"...
|
|
|
|
|
Does management ever asked what tool / product might be helpful?
Not to mention upgrading your current tools/products to the latest version?
Or if you're using the tools you have correctly? "We" (only 1 week left of "we" ) don't even use source control branching because it's "too complicated."
Latest Article - A Concise Overview of Threads
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
I'm likely to leave my current place soon because there are idiots "up top" constantly telling us what's best and making us switch to it.
It's ridiculous, they have no clue what we actually need and that one tool does not fit all situations.
|
|
|
|
|
Marc Clifton wrote: "We" (only 1 week left of "we" [Dance] ) don't even use source control branching because it's "too complicated."
Been there, done that... 
|
|
|
|
|
...does the question and the smaller text below it make ANY sense?
What kind of grammar is this? Sorry, I do not understand what you want to ask here...
Especially this confuses me totally...
Quote: We you would ever buy a tool for a person using a tool without asking them about the tool is beyond me.
|
|
|
|
|
The spell-checker thinks "We" is a perfictlee gud wurd.
At least they didn't use cell-phone texting syntax (LOL).
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
I thought I had forgotten English after reading the question. It is something about picking a technology for a project, right?
|
|
|
|