The Low-Productivity Spiral

Last week was a blast!

Did so many things, had so much passion. Progress in the project was obvious and we were quickly scaling for a great GSoC result.

This week

My productivity levels fell to their minimum.
A number of personal issues, along with the 5th cancellation of my order from Amazon really broke my spirit.
I have done everything possible to acquire an XPS 13 before the coding period started, but the guys at Amazon could only postpone me, no comment on helping me out.

The problem arises because I can’t test my changes on the plugin. Opening a 2nd Eclipse instance and since my first Eclipse instance sends a thermal to my laptop within an hour I have to report little-to-none progress on updating SchemeScript’s Kawa version..

On the bright side, I did some decent research these days on the debugger matter and the code style checker issue. I think after all that the debugger can be implemented with little trouble in the plugin by re-using the existing implementation of debugger support.

This project has:

  • as its main goal research,
  • secondly to add a functioning debugger to a scheme development environment.

I think I’m doing great on the
first and that my hard work is paying off, but on the second I have fallen behind.

The spiral

That’s the developer’s spiral, lack of resources in combination with lack of time (deadlines).