Then I guess the team is too busy to design it? Too busy to code it? Too busy to test it? Too busy to fix it? Too busy to help? If you’re not willing to take the first step towards resolving your problem, writing it down, then how do you expect to get others on board to help you? Aside: Needing help from others on figuring out your problem is a great idea to figure…
Said by every developer ever. “It can’t be a bug if I never had the requirements.” “It can’t be a bug if it never existed in the first place.” “It can’t be a bug because no one else is complaining about it” All valid answers. As well as opportunities to invent a new work item type that removes the stress from finding a feature at the last minute and lightens the mental state of the…
I think this term is used in reference to someone who is trying to “codify” a solution when they are not a coder. I more prefer to think of it as someone who is trying to fix something without knowing what the problem is – so they “solution” away – hoping to get there at some point.
Doing the work that you don’t really want to do but is paramount for you to do so you can focus on what will take you there. In other words: You are not going to get away from all the mundane tasks that go along with your startup when you start out (and there are many). This is a test. The test is whether you are dedicated enough to put in the effort to do…
The Hot Feature is the greatest piece of code ever realized. It starts off as a bug. But not just any but, a customer bug. And not just any bug, but a customer “going bananas, hard to find but oh so good” bug that threatens their use of your product going forward. So you promise to fix the bug. But when you look at the bug, it’s not a bug at all, it’s something new…