4 ms·
The component will have a more extensive API and configuration. This requires more knowledge on the clients side, and makes debugging harder as more things can
by cubano 12y ago
The component will have a more extensive API and configuration. This requires more knowledge on the clients side, and makes debugging harder as more things can go wrong. Developing and debugging the component itself becomes harder as one needs to account for more and more edge cases.
Back "in the day", devs and managers used to call this job security, and was a preferred outcome for most of the people I worked with.
- pc86 12y agoIt's difficult to tell what your tone is, but it is horrible working with people who are concerned only or primarily with job security. It leads to people holding on to information, being hesitant or outright refusing to document procedures and processes, and absolutely denying that there may be a better way to do something than the way they happen to be an expert in.
- cubano 12y agoYes, I couldn't agree more. But, unfortunately, this was the mindset in corporate IT back 10-15 years ago, and in fact the last onsite contract job I worked a few months ago seemed to contain this attitude, so I was thinking in some ways, things are still the same. I couldn't really stand it back then, which is why I moved to contracting/consulting.
- pc86 12y agoI've only been in the job market for 6/7 years, and only half of that in a very corporate environment. Luckily it's (in my limited experience) an individual character trait and not any systemic cultural issue so far.
- cubano 12y agoI, too, have noticed a big change along those lines, which is why I was very careful to use the hated "back in the day" phrase. There is no doubt that due to the pace of technological change nowadays, the idea that devs and managers can hide behind a bloated solution and rake in profit! are pretty much long gone.