I am constantly trying to improve myself and enhance my capabilities, but sometimes you just have to stop and know your own limitations. Limitations aren’t a bad thing, because if you know of them, then you can try to work around them at the same time as focusing on what you are very good at.

I think I’ve hit on one of those limitations in myself. I have problems with big projects which I can only do on my own. I just seem to not be able to manage them correctly. In fact, in some cases they’ve put me off of programming altogether.

So sole-developing big projects is my downfall. The only way forward if I have to deal with the project in its entirety then I’ll just have to get somebody else to help. Preferably if they have prior knowledge of the platform/technologies used. That obviously frees up some of my time to regain my sanity on some other small projects.

One other thing that I could do, and probably should do in the future is only say “yes” to team-based projects (if they are big projects) and small/mini projects such as building small plugins/modules/components to existing well-documented and well-designed systems.

I’ve been learning quite recently that I should say “no” to things more often, particularly if there is any chance that I can’t do something (skill-limitation), don’t have the time to do something (time-limitation) or don’t have enough time to learn how to do something (time-skill-limitation).

This does of course sound a bit of a negative post, but it is a crucial aspect of self-employment, and as you know I try to be open about my career. However, I don’t think that it is entirely negative. I was always taught “Know Thyself”. By knowing myself I can actively and continually work on (and at) smoothing those knobbly bits that can get in the way.

I am open to comments, suggestions and ideas. For now I shall be proud to say that I am a “divide and conquer” style pluging/module/component programmer.

Many thanks and blessings,

Daniel