DEV Community: Gavin Rose

Zikrah Audit Logging

Gavin Rose — Fri, 12 Sep 2025 23:11:03 +0000

🚀 Introducing Zikrah - Now Free to Test!

Hey developers! 👋

We're excited to share Zikrah, our new platform that we've been building with Phoenix/Elixir. We're looking for early testers to help us shape the product before our official launch.

What is Zikrah?

Zikrah is a logging platform that helps other developers and services to offload potential risks when creating audit logs. Our logs are immutable and verified through various levels of security based on tier.

Why Test Now?

Completely FREE - Payments aren't live yet, so everything is available at no cost
Shape the product - Your feedback directly influences our development roadmap
Early access - Get familiar with the platform before everyone else
Built with Phoenix - Fast, reliable, and scalable architecture

Getting Started

Testing Zikrah is simple:

Visit our platform at [https://zikrah.dev]
Sign up for a free account
Explore all features without any payment requirements
Share your feedback with our team

We Want Your Feedback

As developers ourselves, we know how valuable community input is. We're particularly interested in:

User experience and interface feedback
Feature requests and suggestions
Performance observations
Any bugs or issues you encounter

Tech Stack

For those curious about what's under the hood:

Phoenix Framework - Robust web framework
Elixir - Concurrent and fault-tolerant
LiveView - Real-time, interactive experiences

Join Our Testing Community

Ready to give Zikrah a try? We'd love to have you as part of our early testing community!

Questions? Comments? Drop them below or reach out to our team directly. We're here to help and always excited to connect with fellow developers!

elixir #phoenix #startup #testing #developers #webdev

Help Me Test ShareShard!

Gavin Rose — Sun, 08 Jun 2025 04:51:10 +0000

We are continuing to make improvements to ShareShard and would like your feedback!

ShareShard was created as an easy to use developer alternative to other file sharing platforms. Things you share expire in 24 hours or if you are on the pro plan, never.

Still early in development, we are searching for feedback and ways to improve the service. Lets get cooking!

ShareShard

Gavin Rose — Thu, 05 Jun 2025 00:43:57 +0000

🚀 Introducing ShareShard — Effortless Sharing for Code, Images, and More

Ever wanted to quickly share a code snippet, image, or debug output with someone without creating a repo or cluttering a chat thread?

Meet ShareShard — a minimal, developer-focused sharing platform that lets you upload files (code, images, text, etc.) and showcase your stuff without any hassle.

Whether you're collaborating on a side project, showing off a bug, or just passing around a funny screenshot, ShareShard gets out of your way and lets you share instantly.

🧩 What It Does

✅ Instant uploads of code, images, logs, and more
✅ Syntax highlighting for an expanding list of languages
✅ Built-in expiration after 24 hours or never on the pro plan
✅ No sign-up needed for basic usage

⚙️ Built for Developers

ShareShard is like Imgur or Pastebin, but made with developers in mind:

Designed with a clean, no-friction UX
Respects your time
Fast enough to use during a live coding call

🎯 Why I Built It

I was tired of juggling Dropbox, Gists, and random Imgur uploads when I just wanted to share a quick bit of info. Most tools either felt bloated or lacked control. So I built ShareShard: a dead-simple tool that solves a real need without getting in the way.

🌐 Try It Out

You can start using it right now, no sign-up needed:

👉 shareshard.net

Upload. Share. Done.

🙌 Feedback Wanted

I’m actively developing new features — versioning, embeds, and more — and would love your feedback. If you have thoughts, feature ideas, or bugs to report, drop a comment!

Thanks for checking it out — and happy sharing!

Suggest some features I could add!

Gavin Rose — Sun, 11 May 2025 00:35:44 +0000

Gavin Rose

May 10 '25

Developer Utilities with Q (Docstrings, README, etc.)

#devchallenge #awschallenge #ai #webdev

Comments

3 min read

Developer Utilities with Q (Docstrings, README, etc.)

Gavin Rose — Sat, 10 May 2025 08:18:50 +0000

This is a submission for the Amazon Q Developer "Quack The Code" Challenge: Crushing the Command Line

What I Built

Dreading docstrings? Tired of writing boilerplate README files? Wish you could automate those tedious development tasks? Meet duq CLI (Developer Utility with Q) - a command-line tool that supercharges your development workflow by leveraging Amazon Q to handle the boring stuff.

duq CLI wraps the Amazon Q CLI with specialized prompt templates to automate common development tasks like:

Generating comprehensive README files for your projects
Adding proper docstrings to your code files
Creating test cases for your functions
Suggesting code refactoring improvements
Performing security analysis on your codebase

The best part? It maintains a backup system that lets you revert the most recent changes made with the duq CLI with a simple command, giving you the confidence to experiment with AI-powered code improvements.

Demo

Here's a quick example of how duq CLI can transform your workflow:
https://imgur.com/a/duq-duq-goose-32QeSBX

# Generate a README for your project
duq document ./my-project

# Add docstrings to a file
duq docstrings ./src/utils.js

# Generate test cases
duq test ./src/api.js

# Chain commands together
duq chain ./src/models.js "refactor,docstrings,test"

# Oops! Changed your mind? Revert the changes
duq revert

Code Repository

https://github.com/scarab-data/duq-cli
or
try it for yourself by running npm install -g duq-cli

How I Used Amazon Q Developer

Amazon Q Developer was the secret sauce that made duq CLI possible. Aside from Amazon Q being the brains behind the operation, it was also a valuable asset in creating the CLI tool.

To test the efficacy of the idea, I thought it important to consider prompt engineering when initially speaking with Amazon Q.
Short or rushed prompts such as...
q chat "create a readme"
Returned responses like...
Q: I'd be more than happy to assist you in creating a README for your project. Please share the path to your project so that I can get started!
Continuing on the path of chaos...
Me: just do it
Q was able to handle this hasty response with ease, and began scanning through the directory in which the chat was started. Due to lack of instruction and poor prompting, Q wound up generating a README that was seemingly perfect and detailed. Upon further inspection, it turned out Q had hallucinated a file structure that didn't exist within the directory - or anywhere on the computer for that matter.

It also seemed as if just because the word 'test' was in the directory name, Q incorrectly assumed that the whole project was for testing, when in reality, it was just a safe place to test out the duq CLI, that is, until duq revert was implemented.

Prompt engineering is definitely an important part of getting what you want out of any AI, and even more so with programming, it is just as important to give context. This is where the duq CLI really helps Amazon Q shine! Certain duq commands such as README take in a directory path, or if none is given, it will analyze the current directory. It feeds information to Q and gives it that ever-so-important context.

One important piece of insight I gained was that Amazon Q excels at understanding context and generating appropriate responses when given well-structured prompts. By designing my CLI to provide rich context (file contents, directory structures) along with clear instructions, I was able to get remarkably useful and consistent outputs.