Snippp v0.4.0 — Devlog

We’re back!

There’s curation now. Check out our new featured section.

Features are pretty light in this update, I’ve just built out a system for letting moderators and admins pick out lists from users to feature. These lists do the best job of embodying a ‘toolkit’: anywhere from flexible, reusable code all the way to niche hyper-specific code which solves problems with inventive solutions.

This can be: templates for all sorts of Postgres requests, post-processing tools for shaders, a big list of React buttons styled in Tailwind. Anything that makes use of a list being a list and having all these related tools in one place, making the most of this mechanic.

We’re approaching 1.0, so feature creation is slowing down, while bugfixing, security, and optimizing the user flow are at the top of the priority list. Check out the roadmap to see how things are doing :)

Thoughts about Snippp as a product

I’ve been thinking a lot about how to improve Snippp lately while working on various other projects. I’m doing my best to not overengineer, since in the end of the day this is a snippet manager, and doesn’t need anything too fancy. But I do have big ideas about how it could be used.

The biggest change in my thinking has been in messaging and use, without much of the functionality changing. My first version of the app was a bunch of graphics programming tools hard coded, organized for myself and shared with other people.

This was made to be an organizer for others, but maybe the real value was as a resource for the “read-only” users. This is what’s been pushing me towards the ‘toolkit’ mindset, instead of just having good storage, what if I made toolkits to be shared with others?

I’m already going to be organizing my tools here, so I’ll make it public and let people use them if they want.

But — My approach doesn’t work for everybody, and I certainly don’t know everything, what about the people working in languages and frameworks I don’t?

What if there were other developers also organizing and sharing their tools here?

That would be great, it could be a community of developers building toolkits for other developers to use, learn from, and save time with. But how do I incentivize developers to use this as a platform? I have basically 4 options that I can think of for the future:

Make it a useful, secure, and intuitive experience to use the tool, so good that other organizers are an afterthought.
Find funding to pay developers to build a few toolkits and contribute
Keep contributing by myself and hope someone else sees the value in contributing
Find another tool that already exists and find ways to contribute there, where everyone is already contributing. I’m open to letting Snippp go if there’s new information, I won’t die on the hill of forcing my own creation, I’d just like to help foster a community of devs however possible.

If you’re a developer and have some tools or toolkits you’d like to share with others that are expanding their skills, or you’re looking for a better way to organize your tools, give Snippp a try :)

If you’d like any features to better organize or search/filter tools, give me a shout, I’m happy to listen and build. I want this to be useful both as an organizer and as a resource for those still building their skills.

Send me a message on Twitter

More to read:

I finally tried Next.js

How To Create Useful Things By Yourself

Snippp v0.4.0 — Devlog

Snippp v0.3.0 — Devlog

Snippp.io — or How I Made My Organization Tool Into a Service

Snippets for Art

Intro to Polar Shapes

LUTs in Generative Art and Graphics Programming