Tag Info

New answers tagged

7

At some point, every project becomes too large and complicated to keep it all in your head. For some this point comes sooner or later than for others and you seem to have hit that point in your project now. The first step now is to start writing that dreaded documentation. Write down what each class is supposed to be doing, which classes work together ...


1

How do you overcome it? I see (intentionally seeking) other people making mistakes and being fine with that. That tones down my fear of mistakes. If you absolutely cannot work on a solo project then how do you explain it to your boss so that it doesn't seem like you're incompetent? I don't know how it looks from the eyes of my boss. I can't read ...


0

It is not clear from the question if the projects were actually released at some point or were they abandoned before the first release. In the latter case it's clear that a change in mindset is needed. We engineers would always like to perfect our product and feel uneasy when we need to release something that still has lots to improve. But this is exactly ...


10

As Churchill famously remarked, "the maxim 'nothing avails but perfection' may be spelt shorter: p-a-r-a-l-y-s-i-s". You need to internalize the notion that this approach is unprofessional. Or, as Jamie Zawinski put it (in "Coders at Work", recommended by Joel Spolsky once), "At the end of the day, ship the fucking thing! It’s great to rewrite your code ...


6

One thing I could suggest from my own experience is to have a clear "definition of done" for every task you are working on. Although this term comes mainly from the scrum environment (see a description here) it could also be helpful to adopt it when working alone on a project. The main idea is that you define clear, measurable criteria that describe when ...



Top 50 recent answers are included