WHY ARE SOME PROGRAMMERS 10,000 TIMES BETTER THAN THE REST? DOES IT MATTER? THEY

WHY ARE SOME PROGRAMMERS 10,000 TIMES BETTER THAN THE REST? DOES IT MATTER? THEY ARE.

Kirill just fixed a problem that has been with us for two years, that he solved in just a few hours – flawlessly. Yet, instead of being arrogant, he will also say “Alexey will do that, he has more patience than I do”. And Alexey will make fun of us both at times because we miss the logically obvious (to him). The difference is “Talent”, experience, research, persistence, hard work, and humility.

So:

– There many reasons that make a happy family, any one or more of which will make an unhappy family.

– There are many reasons that an animal is domesticatable, any one of which will make it impossible to domesticate.

– There are many reasons that make a programmer great any one of which will make the others only adequate.

We have only four substantial issues left that I know of before BETA clients can use it:

a) deliverable (sprint) accounting – which should not be hard. It means tracking the history of additions and subtractions of children from estimated and in-progress work.

b) The reports which are our last feature for v1.

c) The addition of reservations and appointments (forecasting) to the gantt chart. (I should never have cut it. it’s my fault. I know). We have to have them.

d) Then my job…. :

d0) Edit all the error and other messages.

d1) Documentation and tutorials.

d2) Default (sample) workflows and projects.

I GO THRU THE LIST EVERY DAY, AND THATS IT FOR BETA.

We’re in the last stretch!

NITS I”M CONFESSING

Some nits I’ve noticed that make me a little crazy, but aren’t blockers for release to beta sites.

d) the inconsistency of button labels when editing tables. This will be something Kirill and I do in a few hours over coffee.

e) a lot of the admin screens need to separate SELECTED items from UNSELECTED items. Right now they are combined in one table and this is confusing for users.

I SUSPECT I WILL NOW BE THE SOURCE OF ANY DELAY since the documentation is enormous, and while I write fast, and I am partly through it, I degrade quickly when switching between the screen capture and art, and the text.