A dime worth of ideas.

Leslie Steward — Wed, 05 Feb 2020 02:49:03 +0000

They say an idea is worth a dime a dozen. Here's twelve then.

Conveyor belt tapas. Don't limit your thinking to sushi.
Distributed ledger for caucuses.
Restaurant finder app that minimizes total travel time for distributed groups. Solve "We should all go here.", "It's too far"
Siesta Wednesdays
Puppy Therapy as a Service
Site to allow simplified graph generation. Make it easier to visualize what dependencies look like.
Gamify restaurant loyalty. Complete quests to eat all salads. Unlock and upgrade bonus sauces. Buy loot crates to enable rare side dishes. Complete streaks to unlock extra savings. Compete with other eaters for prizes.
Pop Up Video for State of the Union Address.
Taking it a little easier on all the Cascade Hops there brew masters. Come on.
Savory shave ice?
Kitchen spoons in colors of cooking, good roux, golden brown of bread, translucent onions, cooked green beans, cooked shrimp. #brown
Just be a little nicer, give people the benefit of the doubt.
BONUS: GymBus™ - Don't just sit there, work out on your way to work! (liability concerns in progress)

Follow me for more "ideas".

4 easy ways to help your QA

Leslie Steward — Mon, 29 Jul 2019 04:59:34 +0000

You are a good developer, and you understand that your quality assurance team wants to help you find issues in the code. Help your friend out by doing a few simple things.

Involve QA early.

Your QA have experience understanding how systems behave and misbehave. They also have the skills to make the applications break. Use these skills and ask them to review designs before much coding work is done. I guarantee you they will be receptive, and you will get some valuable feedback on the code. The earlier you catch an issue, the easier it will be to resolve.

Be there to answer questions.

Your QA has one primary responsibility, to make sure the program does what it's supposed to do. Sounds simple, but how can the QA know the expected behavior? In a perfect world, there will be specifications, but maybe those aren't quite complete. Be available to answer their questions, even be proactive and help them out by stepping through the application with them once. This will answer the majority of the questions they have, speed up the release process, and help you each understand assumptions in the program.

Write down assumptions.

You can also help your QA by writing down those assumptions you made during the coding. Maybe you decided on some pattern because you think it will save time in the future. Maybe you exposed a value in a configuration. It's all good, your QA should value your opinion, but please write those down. It'll help save time in the long run.

Tactical things to do.

There are lots of little actions you can take to make your QA's life easier.

For your SDETs using Selenium or similar, include a unique identifier on your html actionable elements. Put on your button, on each input box, on the container for your list, on the navigation section. This allows web automation to be written more quickly and clearer.
For your SDETs using Selenium or similar, avoid animations if possible. You can ask them about their different strategies for waiting for an element if you want to know why.
For your database testers, help them with sample data for testing, or at least the domain knowledge you have when generating your data.
For your API testers, provide some way to browse the API and structures; add Swagger, Apiary, or other api generation tool
Share the code. Black box testing is silly.
Visualize it. Draw some circles and arrows on the whiteboard, describe the flow of data.

These tips will help you speed up the QA process, and get better results. Everybody wants to write good code that gets the job done. Your QA will appreciate the time you've taken.