loading words...

Apr 11, 2019 21:42:19

Copy vs. create

by @Arcticloon PATRON | 206 words | 310🔥 | 310💌

Janne Koponen

Current day streak: 310🔥
Total posts: 310💌
Total words: 67476 (269 pages 📄)

It's a good thing that nowadays there is a ready solution to almost everything. For example, in software development, there is a library or API implementing what you need and in personal development, there are all those methods. It's not about lack of solution, its about the difficulty of choosing the best one from all the available options.

But is copying and using those already existing solutions always the most suitable choice. Or are they actually the best possible. Maybe there is a way to do even better, more suitable solution. At least for your particular use case.

It's tempting to think you could improve something so many others have already tried and iterated through. But they didn't necessarily have your specific problem or situation. Even if it would be best solution in general, maybe something else would suit this special case.

It would be so easy to just copy and use those ready-made solutions. Somebody else has gone through the trouble of refining them.

But if we never try new things, never aim to improve existing well eventually end up in stagnated situation where nothing new ever comes up. Sometimes it's worth to try something new. Even if it's just for the sake of it.

Originally published at arcticloon.fi

contact: email - twitter / Terms / Privacy