#RUNNING SWI PROLOG IN VISUAL PROLOG SERIES#

You inflate the Poyntsв„ў on their tasks, and they inflate the Poyntsв„ў on yours.

More direct version of this вЂ“ put a time waster loop in the code, hidden as something. Later do more вЂperformance improvementвЂ™ вЂ“ repeat until youвЂ™ve finished the big change you needed. Put yourself down for вЂperformance improvementвЂ™ Poyntsв„ў. Write something in a deliberately inefficient way. You now have a nice performance improvement bug you can finish off easily. Write something in the вЂsimplest way that could possibly workвЂ™. Variant вЂ“ finish a feature but hide the UI control until itвЂ™s вЂscheduledвЂ™.

Otherwise pointy haired management will get irritated at non working controls, and be frustrated cause it looked like it was вЂalmost doneвЂ™ months ago. When you are making a UI, donвЂ™t put in controls til you are ready to wire them up. Variation вЂ“ make new features like вЂText controllerвЂ™ by moving a bunch of controls into a nonmodal dialog. Icon overhaul вЂ“ If the problemвЂ™s not your individual PM, but upper level management, and your team needs a good chunk of time to fix the core engine, go ahead and take it, then spend a few hours rearranging the UI and have the graphic artist make you new icons. Then wait til itвЂ™s found and fix it вЂ“ since you know exactly what happened, itвЂ™s an easy fix and you have some nice вЂmeвЂ™ time. The fake bug вЂ“ introduce a bug by leaving out updating something. Now get a tame user to complain about it, and then get yourself assigned to fix it. Variant вЂ“ the done bug вЂ“ find an obscure low priority existing bug and fix it during a scrap of time. Eventually either somebody else will file the bug (in which case you just PR and do hero) or youвЂ™ll need to cash in the balloon (get a tame user to complain about the bug, then hide in a corner (aww, open plan, no corner to hide in) and type furiously for a couple hours on something actually useful, then PR the bug fix. Stash a bug вЂ“ See a bug? Make a quick branch and fix it. The best balloons are creative вЂ“ gotta fight off boredom вЂ“ but hereвЂ™s some examples to get you started:

#RUNNING SWI PROLOG IN VISUAL PROLOG SERIES#

You want to build into the Agileв„ў work a series of вЂballoonsвЂ™ you can use to grab time when you need it.ДЄ вЂballoonвЂ™ is a thing you can actually do in 30 minutes or less but looks to the Agileв„ў Scum Master like a 5 Poynterв„ў. So whatвЂ™s an enterprising girl to do when she wants or needs a space? And that usually takes a couple solid weeks. So, if youвЂ™re in an Agileв„ў shop, you will of course be forbidden by the rules of Agileв„ў from actually working on anything that takes more than a couple Poyntsв„ў of time.ДЄnd thatвЂ™s a problem, because anything worth actually doing in programming is done by finding a better architecture and implementing it, not by three point improve error handling in rando form.

Running swi prolog in visual prolog