Intro to Bard

My introduction to Bard

Semantic clarification: I’m not introducing you, reader, to Bard. This is my experience of being introduced to Bard.

The answer to my first question, probably way too Turing-ish, shows that Bard is slow on the uptake as to context. I asked “What is the best use of Bard?” and received a description of the Dungeons and Dragons role.

What is the best use of Bard?
What is the best use of Bard?

Points for the honesty of Bard, because this is very different from the description from the email confirming my access, which described Bard as “…your creative and helpful collaborator, here to supercharge your imagination, boost your productivity, and bring your ideas to life.

I was disappointed. The makers of Dungeons & Dragons: Honor Among Thieves should be disappointed it didn’t display an add along with the response (how much you wanna bet the GA version will?). I gave similar feedback to Bard and moved to my next question.

My next question was “Which is better: ChatGPT or Bard?” The response was interesting. It didn’t rise to the bait of “my dog’s better than your dog” (yes, I’m that old) and gave a good answer that you can read for yourself in the screenshot and that I will summarize as ChatGPT will do your homework and Bard will do your Googling for you.

Which is better: ChatGPT or Bard?
Which is better: ChatGPT or Bard?

But how good is Bard at Googling? Having used Google since it’s year of inception, and having struggled for many years with its predecessors, I feel fairly adept at searching on Google. I worded my next query the way I would (will?) write the actual requirement for a project I’m working on: “What is the best ReactJS compatible image viewer with vector markup capability that can be stored in PostgresSQL?

What is the best ReactJS compatible image viewer with vector markup capability that can be stored in PostgresSQL?
What is the best ReactJS compatible image viewer with vector markup capability that can be stored in PostgresSQL?

The response was literal and detailed. It described only one product (“Feeling lucky?” anyone) and gave a detailed reason for the recommendation. I will definitely include the recommendation in my comparisons, and decide whether to ask Bard for other options or go back to my normal way of searching.

If you believe the vlogsphere, the push to get Bard operational and in the hands of Google users is the threat of ChatGPT bringing everyone over to B.I.N.G (Because It’s Not Google). For the practical and technical, I think Bard is an excellent response to that threat.  For the majority of folks, I think Bard is going to have a tough time for having come out of the gate this late.

And then…

After posting the first revision of this article I went back to continue the vector library search. Interestingly, while I can see the questions (aka prompts) that I had asked previously, I cannot access the answers. Glad I took screen shots, because after pasting in the same question I received a different response. This wasn’t too surprising as I have heard ChatGPT users have the same experience. Wanting a quick finish to the task, I then asked for the top 5 options. The first of the 5 was the same as the response in this request, but the suggestion given the first time was not in the top 5. Makes me curious what changed in 45 minutes for the first option that was the best to no longer be in the top 5?

And then #1 was never heard from again
And then #1 was never heard from again
Facebooktwitterredditlinkedinmail
© Scott S. Nelson
Photo by John Schnobrich on Unsplash

3 Common QA Misconceptions

Plan Performance Testing with Platform Architecture

If there is to be performance testing both the test tool platform and the test environment need to be robust enough to support it. This will require either a server farm capable of exercising the application at a realistic load or ensuring that the application performance test interfaces can be accessed by an external cloud-based platform. In the latter case, plan security testing to be done before the performance testing.

Automated Testing is Worth the Time

Many projects do not use automated testing because of the time involved in creating the tests. This is based on optimistic estimates of expected number of defects and iterations to resolve. Ironically, not having automated testing for regression testing increases the number of iterations to resolve defects and increases the total effort of testing.

Acceptance Tests are not Regression Tests

Acceptance tests are generally limited in scope to how users are expected to use the system. Regression tests should include edge cases and dynamically-generated inputs, with the inputs recorded in the event of defects being identified in order to support re-creation and potential adjustments to test parameters.

Bonus Best Practice

Defect summaries should be formatted as TYPE: Component – Functional Error Summary

Facebooktwitterredditlinkedinmail
© Scott S. Nelson
Chaos Cats

Failing to plan is still a plan

(Featured image credit: created with Midjourney by Alison Braun)

Some planning tips from a retired page on this blog that are still relevant…


Periodically review tuning and best practice references related to the technologies, tools and products related to the project you are working on to catch potential issues before the occur.


Always include time for making necessary, realistic data available for development. Include approaches for resetting and refreshing data. The time spent up front will be half as much or less than the time spent afterwards creating it as needed.


Plan Your Monitoring Before Go-Live

This concepts sounds obvious and yet it so often does not happen even in mature organizations. Everyone will be much happier spending some time to think about scenarios where things could go wrong and determining thresholds for alerts on any area where a variance can impact functionality or availability.

Ever hear the boiling frog analogy? While the basis is not true, the concept is important, especially with software. Be alert. The world needs more lerts.

Facebooktwitterredditlinkedinmail
© Scott S. Nelson
SFDC Login Use Custom Domain

Trailhead Log In to Personal or Scratch Org SOLVED!

Having problems logging in to your dev, personal, or scratch org to verify the completion of a 500 point Trailhead lesson? Personal dev orgs are Production orgs and use login.salesforce.com and dev sandboxes are sandboxes and use test.salesforce.com and since I usually just use the CLI to log in to scratch orgs I can never remember which to use. And I don’t need to. There is enough to remember about Salesforce and technology in general, so if I can simplify something to a common approach, I always do. In this case, when authoring an org of an OAuth connection I always use the Use Custom Domain option and paste in the domain of the org I want to use.

Facebooktwitterredditlinkedinmail
© Scott S. Nelson
Bone-in or Wild Caught Lobster Tails