But then we have a management that loves shiny. Part of our mandate is to piss about with the latest tech so lots of it is recommended by various sources and the team get to play with the new toys. The majority get rejected as for most of the reasons in the survey.
Never underestimate the power of human stupidity -
I'm old. I know stuff - JSOP
I accepted a job offer, where I was to implment a GUI to a fancy debugger with a command line interface. It was decided before I entered that the implementation language would be Tcl/TK, which was completely new to me. My only inteface to the debugger would be the command line language, and it was out of the question to make modifications/extensions to the CLI. Yet they expected a dynamic GUI of the same quality and responsiveness as GUI-born applications.
Tcl/TK is not the tool for that kind of implementation! I struggled with it for about a year. Then the code base had grown to between 30 and 40 KLOC, and stability was like a house of cards. I spent my summer vacation replacing the great majority of the program logic, and the data structures holding a shadow copy of inforation that could be obtained through the CLI, with a plain C implmenetation, leaving only the GUI widget handling (the TK part) to Tcl, i.e. about 10% of the old Tcl code. After my summer vacation, I silenly replaced the Tcl code with my C stuff, increasing performance significantly, and stability went from a nightmare to acceptable.
There had always been a small core of C interfacing functions, so I could slowly leak out that I had extended that core a little, and a little more, and a little more... I don't think the management ever realized that it was done in one big sweep. They just saw the code getting gaster and more stable. Maybe they even discovered that my swearing and bitching at the keyboard was significantly reduced as well.
According to the description (in Englihs) of this open source code library, it was just what we were after - but the nature of our project required us to make extensions/modifications to it. So we got hold of it, only to realize that it was well commented all over the code, and the naming of variables, functions and such seemed to be reasonably descriptive, guessing from the lenght of the names.
Or so we guessed. None of the project members could read French, and everything but the reserved keywords were in French. When you wnat to modify something, you want to know what you've got. We didn't have a clue, not at the code level. So we had to find another library, probably not as good as the French one, but in a form that we could make use of.
".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