My perspective in this post is mostly tech interview — accumulation, retention of knowledge, prevention of loss due to churn. As I age, I’m more selective what new technology to invest into.
In contrast to the interview perspective, the GTD perspective is dominated by localSys ! So churn doesn’t matter.
Many of these technologies are past their peak, though none is losing relevance. However, I tend to perceive these tech skills as robust and resilient, time-honored. Among them, I see a partial pattern — Many of them exhibit a stable base; some of them show a fluid superstructure of skillset.
- essential algorithms/data_structures and bigO — stable, possibly growing base + fluid superstructure
- java skillset — has a stable base i.e. coreJava + fluid ecosystem including jGC, jxee
- C/C++ — has a stable base skillset including TMP, STL… The superstructure is fluid mainly due to c++0x
- SQL and socket — each has a stable base
- pthread, unix internals ..– ditto
- unix (no QQ topics, but many GTD skills) — stable superstructure skillset including instrumentation, utils and scripting. Base? tiny.
- http stack — stable but tiny base including session/cookies + fluid superstructure