# Breaking things with a fake goal for API tinkering **URL:** \ **Category:** Bugabee\ **Created:** [February 4, 2017, 7:53pm UTC](https://forum.beeminder.com/t/breaking-things-with-a-fake-goal-for-api-tinkering/2970 "2017-02-04T19:53:02Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![dreev](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/dreev/32/4311_2.png) [@dreev](https://forum.beeminder.com/u/dreev)\ **Post date:** [March 27, 2017, 2:49am UTC](https://forum.beeminder.com/t/breaking-things-with-a-fake-goal-for-api-tinkering/2970/2 "2017-03-27T02:49:03Z")
Beautiful bug report; thank you! For prioritizing purposes, were you able to work around it ok for your api test goal? Easier way to get a goal with no risk of derailing is to dial the road to a rate of zero. Sort of related: > [@"Rate cannot be 0"](http://forum.beeminder.com/t/rate-cannot-be-0/2917/7): > > These counterarguments are excellent but I still think there’s a lot to be said for hard nudges and opinionated software. It used to be horribly common for newbees to set the initial slope to zero for lack of having thought of something better. Then Beeminder would just never make them do anything and all the mustering of willpower that made them set up the goal was wasted. Or, worse, they’d not understand anything about setting slopes of yellow brick roads and such and Beeminder would just seem… --- _[View the full topic](https://forum.beeminder.com/t/breaking-things-with-a-fake-goal-for-api-tinkering/2970)._