3 ms·

This mentality is far worse then the article describes. The short sighted lack of institutional knowledge is, for technology companies, a serious issue. We are

This mentality is far worse then the article describes. The short sighted lack of institutional knowledge is, for technology companies, a serious issue. We are knowledge workers, and we know too clearly how technology management tries to treat salaried developers as inter-changeable. Add in contract technology developers and you have a recipe for success-causes-failure situations as there are black holes in the institutional knowledge of the flagship revenue generating product the company offers. I see time and time again, technology management not grasping it is the comprehensive solution, the product that allows customers to solve their problems without other software that make the difference. Any key technology is great, but without all the "document / project" wrapper, multiple import/export options, and API interfaces that contract developers are often tasked to create that enable the "key technology" to have the accessibility to be successful. Without all the "interface and GUI stuff" you do not have a product. That "interface and GUI stuff" is a core competency, yet technology management rarely recognizes this.

emidln 9y ago
> This mentality is far worse then the article describes. The short sighted lack of institutional knowledge is, for technology companies, a serious issue. We are knowledge workers, and we know too clearly how technology management tries to treat salaried developers as inter-changeable. Add in contract technology developers and you have a recipe for success-causes-failure situations as there are black holes in the institutional knowledge of the flagship revenue generating product the company offers. Quoting a bit of comedy: As long as there are ill-defined goals, bizarre bugs, and unrealistic schedules, there will be Real Programmers willing to jump in and Solve The Problem, saving the documentation for later. -- "Real Programmers Don't Use PASCAL"[0] There are a lot of consultants who stand to make a ton of money due to lack of institutional knowledge. [0] http://web.mit.edu/humor/Computers/real.programmers http://web.mit.edu/humor/Computers/real.programmers

emidln 9y ago

> This mentality is far worse then the article describes. The short sighted lack of institutional knowledge is, for technology companies, a serious issue. We are knowledge workers, and we know too clearly how technology management tries to treat salaried developers as inter-changeable. Add in contract technology developers and you have a recipe for success-causes-failure situations as there are black holes in the institutional knowledge of the flagship revenue generating product the company offers. Quoting a bit of comedy: As long as there are ill-defined goals, bizarre bugs, and unrealistic schedules, there will be Real Programmers willing to jump in and Solve The Problem, saving the documentation for later. -- "Real Programmers Don't Use PASCAL"[0] There are a lot of consultants who stand to make a ton of money due to lack of institutional knowledge. [0] http://web.mit.edu/humor/Computers/real.programmers http://web.mit.edu/humor/Computers/real.programmers