DEV Community

Discussion on: What skills do career indie developers not learn (vs those employed mostly on teams)

Collapse
 
karandpr profile image
Karan Gandhi

I am just speaking from personal POV. >_> .

1.) Documentation: Indie developers don't document. If you do , you are either a maverick or a liar.
2.) Depending on Team: As an indie developer I had habit of soloing on everything. After a certain time it was bit infuriating being told to not do work ¯_(ツ)_/¯ .
3.) Libraries & Licensing : Indie developers tend to use everything available at their disposal regardless of the license involved.. In a company environment libraries have to be pre approved for usage. Plus developers are asked to not use GPL licenses or strict copyleft.
4.) Career Path/ Hierarchy : Indie developers don't think about career paths. While they get to Senior Developers roles faster. Indie developers are out of depth or experience for the Architect or other techno management roles.
5.)Vision: This is debatable. Indie developers don't get big projects or projects which connect to multiple systems. People in teams tend to get to work on bigger projects. But Indie developers can think of an project end-to-end. People in teams usually have work on a small part in a large vision without having access to see how everything wires up. So basically someone who has worked on teams exclusively cannot work on end to end projects.

Collapse
 
steelwolf180 profile image
Max Ong Zong Bao

+1 for point 1 and 2. I found the importance for it when I'm taking over legacy code or doing API integration work.