I’m not allowed to tell you that the team at Triberr has formally begun the process of rebuilding Triberr from the ground up to be better, faster and full of more awesome. I’m also not allowed to tell you that right now on my desk is a stack of Triberr stickers. I’m certainly not allowed to ask you to give me feedback on your Triberr experience in exchange for a Triberr sticker.
If I were allowed to do such a thing, I’d ask Triberr users to give me feedback on what you would like to see in a new generation of Triberr.
Which totally does not exist.
If it did exist, it’s likely that I’ll spend the next few days and weeks grueling over a software specifications requirements document in order to document the design, structure and operability of Triberr.
Because a software specifications document or SRS is the most important part of app development. Think of building a house. Would you spend money on the construction without an architectural drawing? How would you know what you are getting? How would the contractor know what to build? What if the contractor builds a perfectly functional house, but it’s not what you expected or wanted. The SRS resolves that problem. Mostly.
But it’s not just about apps. Every project needs a clear specifications document – even if you call it by a different name – so that every person understands the expected outcomes the same way. Not having specifications is almost guaranteed to result in a failed project.
Now about those stickers. Use the form here to subscribe to the Web.Search.Social list. Leave me your thoughts about what you think will make Triberr better and if you are in the continental Unites States, I’ll send you a Triberr sticker while supplies last.
These are my 300 words for the day. I am Ralph M. Rivera.[line]