HTML Paragraphs in BBEdit
In BBEdit, you can select a line and then apply the HTML Paragraph tag. It's a simple common task that HTML developers will use over and over.
The problem is, the paragraph tag gets applied to the line before and after the selected text:
I would rather have the tag be applied on the same line:
Hidden Config Settings
This can be done by changing a little known expert settings to get the above results. Copy/Paste the following in terminal:
If you find you like it how it works by default:
Now when you apply the paragraph command to any selected text it won't add the paragraph tags on the separate lines.
We love Smashburger, as my daughter says so often - they have the best Gluten Free cheese burger.
However has Smash Burger jumped the Shark?
Check out these photos from 2017 and 2019 from Smashburger in Natick, Massachusetts. These are the same order: A Gluten-Free hamburger with a side of fries.
September 15, 2017
September 26, 2019.
I know it's been 2-years between the two photos, but I would expect to see a better option two years later. (Whatever happened to the side pickles?)
My daughter still loves going to Smash Burger, but I think she has noticed that she isn't getting the same burger. Hopefully
New SmashBurger in Massachusetts?
There are rumors that there's a new Smash Burger opening up someplace near Boston. In Massachusetts, there are locations in Medford, Natick, and Westwood.
What Do You Think?
Have you seen a quality decline at Smash Burger?
Best QA Advice
On Twitter, someone asked, "What's the best testing advice you've ever heard?" I thought it was an interesting question, so I thought I share my "Top 5 QA Advice" that I have gotten over the years.
Top 5 QA Advice
Here are some of the best advice I have learned over the years.
"Never assume the assumption is true." - Kind of weird advice. But it was given to me when I was assuming too much when reading the testing steps of a ticket. My manager at the time said this to me so that I would try to think outside of the box and challenge the assumption that was given on the ticket. (For example, what if the user forgot the email address that they used in a "Forgotten Password" test.)
Pay attention to the details - Always make sure to check the little things when testing tickets. Because when customers are looking at the final work, they will notice the small details - especially if it doesn't seem quite right.
Learn SQL really well - Given to me by a manager a long time ago. He really stressed to make sure that I knew all the tricks of making a SQL Select statement. This not only helped me debug issues but also build some interesting QA Dashboards.
Document Everything - The manager would go on to say, "You never know when you may get hit by a bus." He was being funny. But his point was to make sure that test documents were updated and more importantly useful. This was a key thing. If I wasn't writing things down.
Always end an automation run with a validation statement. - Someone on the automation team gave me this advice when code auditing my automation. "What good is your test if you don't finish it with some validation statement." This is pretty good advice that I give to other people.