{"id":80,"date":"2026-10-09T13:58:42","date_gmt":"2026-10-09T13:58:42","guid":{"rendered":"https:\/\/www.glencoulson.com\/?p=80"},"modified":"2026-10-09T18:56:38","modified_gmt":"2026-10-09T18:56:38","slug":"squish-see-a-bug-squish-a-bug","status":"publish","type":"post","link":"https:\/\/www.glencoulson.com\/index.php\/2026\/10\/09\/squish-see-a-bug-squish-a-bug\/","title":{"rendered":"Squish \u2014 See a Bug, Squish a Bug!"},"content":{"rendered":"\n

<\/h1>\n\n\n\n

I’ve been building quite a few applications lately, and one thing I’ve learned is that finding bugs is easy. Keeping track of them all is another story.<\/p>\n\n\n\n

I’ll be testing something, notice a button doesn’t work, a page looks terrible on mobile, or something that worked yesterday suddenly doesn’t work today. Sound familiar?<\/p>\n\n\n\n

Sure, there are plenty of bug-tracking systems out there, but most of them seem to require a degree in project management just to report a broken button.<\/p>\n\n\n\n

I wanted something simpler. So I built Squish<\/strong>.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Squish is a lightweight, web-based bug reporter built with PHP and MySQL. The idea is pretty straightforward: See a bug, capture it, mark it, describe it, and Squish it.<\/strong><\/p>\n\n\n\n

When I find something wrong, I can take a screenshot, upload it or paste it directly from my clipboard. Squish lets me mark up the image right in my browser, highlighting exactly what’s broken. No need to open another graphics program just to draw a circle around a problem.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

I can attach up to three screenshots, give the bug a short description, and assign it to the application I’m working on. Squish automatically gives it a bug number so I can keep track of things without inventing my own filing system.<\/p>\n\n\n\n

It even keeps the original screenshot along with my marked-up version, just in case I need to go back and see what things looked like before I started drawing all over them.<\/p>\n\n\n\n

Everything goes onto a simple bug board. A problem is either OPEN<\/strong> or SQUISHED<\/strong>. That’s it. When the bug is fixed, I mark it SQUISHED, and the report stays around in case I need to reference it later.<\/p>\n\n\n\n

I’m also using AI coding agents to help develop my applications, and screenshots make it a whole lot easier to show an agent exactly what’s wrong instead of trying to explain that the third button from the left is overlapping the thingamajig underneath it.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Eventually, I may tie Squish into FortiDude, my project development and planning system, so bug reports can become punchlist items. But I deliberately kept the two independent. Squish doesn’t need FortiDude, and it doesn’t need to grow into another complicated project-management application.<\/p>\n\n\n\n

That’s really the whole point.<\/p>\n\n\n\n

I didn’t want another system to manage. I wanted a quick way to point at something broken, explain what’s wrong, get it fixed, and move on.<\/p>\n\n\n\n

Find it. Mark it. Fix it. SQUISH IT!<\/strong><\/p>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

I’ve been building quite a few applications lately, and one thing I’ve learned is that finding bugs is easy. Keeping track of them all is another story. I’ll be testing something, notice a button doesn’t work, a page looks terrible on mobile, or something that worked yesterday suddenly doesn’t work today. Sound familiar? Sure, there […]<\/p>\n","protected":false},"author":1,"featured_media":81,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-80","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"blocksy_meta":{"styles_descriptor":{"styles":{"desktop":"","tablet":"","mobile":""},"google_fonts":[],"version":8}},"_links":{"self":[{"href":"https:\/\/www.glencoulson.com\/index.php\/wp-json\/wp\/v2\/posts\/80","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.glencoulson.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.glencoulson.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.glencoulson.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.glencoulson.com\/index.php\/wp-json\/wp\/v2\/comments?post=80"}],"version-history":[{"count":3,"href":"https:\/\/www.glencoulson.com\/index.php\/wp-json\/wp\/v2\/posts\/80\/revisions"}],"predecessor-version":[{"id":87,"href":"https:\/\/www.glencoulson.com\/index.php\/wp-json\/wp\/v2\/posts\/80\/revisions\/87"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.glencoulson.com\/index.php\/wp-json\/wp\/v2\/media\/81"}],"wp:attachment":[{"href":"https:\/\/www.glencoulson.com\/index.php\/wp-json\/wp\/v2\/media?parent=80"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.glencoulson.com\/index.php\/wp-json\/wp\/v2\/categories?post=80"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.glencoulson.com\/index.php\/wp-json\/wp\/v2\/tags?post=80"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}