Member-only story
Outside-in approach — the community way
As a software engineer (or a consultant), we would be on a software development project, and we may switch from a project to another, or change from one company to another. That happens several times in our career. For legal and intellectual propriety purpose, we can’t re-use the codebase that does not belong to us. One thing however is left with each of us is the knowledge and skills we have built over time for ourselves.
Over years, the lucky ones would have been working on projects in which there is team spirits. How magnificent it is to work in a clean environment? With great teammates and careful managers! Still, one day we may want to lookup for new horizon, seeking for a place where we can make progress in our career, learn new things or experiment new things. Because we are passionate, right?
When we leave one place, we would leave only with our brain filled with more experience, knowledge and skills. But empty hand! Hm, what a shame. I suggest we explore a way to keep some assets for ourselves in such case. That’s is the outside-in approach.
Before jump to the heart of the topic, I suggest we do a little digression that will help understand later the outside-in approach.
