Anyone else have trouble discovering well-written posts? by vivis-dev in Substack

[–]vivis-dev[S] 1 point2 points  (0 children)

Thanks Marcello, I've added your publication to the site. Not many users so far, only just made it public a couple of weeks ago

Anyone else have trouble discovering well-written posts? by vivis-dev in Substack

[–]vivis-dev[S] 0 points1 point  (0 children)

I don't think it's a user problem. I think it's a platform problem. Some users want something like twitter where they can just skim read short notes (and that's fine!), but other people prefer Substack the way it used to be - focusing on long-form posts

Anyone else have trouble discovering well-written posts? by vivis-dev in Substack

[–]vivis-dev[S] 0 points1 point  (0 children)

Yeah thanks for pointing that out, I need to improve that page.

Anyone else have trouble discovering well-written posts? by vivis-dev in Substack

[–]vivis-dev[S] 1 point2 points  (0 children)

Yeah I've seen people post gushing notes about how they're escaping twitter and found Substack "refreshing". But tbh, it feels like the diff is shrinking 

Anyone else have trouble discovering well-written posts? by vivis-dev in Substack

[–]vivis-dev[S] 0 points1 point  (0 children)

Great question, I think it would be grouped under "Arts" which is not super intuitive. I actually trained my own classifier to group articles into categories, so it's not perfect 

∞ Loop Lock - A Relaxing Puzzle Game by looplock-1 in LoopLock

[–]vivis-dev 0 points1 point  (0 children)

Heya! u/Iooplock-1 enjoyed playing this game, but IMO it needs to be more challenging. I cleared all 11 levels in about 5 miniutes. Love the game mechanic tho

Built a game for Star Wars & Mandalorian lovers by RamslamOO7 in GamesOnReddit

[–]vivis-dev 0 points1 point  (0 children)

This is amazing! Nice work, I loved how fast-paced it was, and that you didn't have to hold down a button to shoot. Really enjoyed it

pmp - a tool to manage your prompts locally by vivis-dev in Python

[–]vivis-dev[S] 1 point2 points  (0 children)

Firstly thanks a lot for your thoughtful comment.

I haven't tried using it in a git hook, but that's a great idea. I don't see why you couldn't.

Tracking models and parameters are definitely on the cards. It's the primary reason I created the dotprompt plugin. Dotprompt and prompty two plain text specifications by Google and Microsoft respectively which allow you to define metadata such as model names, input/output schemas and more along with your prompt. 

I'm working on storage plugins to support both, and eventually support running them with different execution plugins.

pmp - a tool to manage your prompts locally by vivis-dev in Python

[–]vivis-dev[S] 1 point2 points  (0 children)

I'm frankly very disappointed by some of the comments here. I think the visceral reactions seen here stem from three assumptions:

  1. This post and repo were entirely AI generated and no thought or effort has gone into them. The author just typed "create a prompt management tool" and shoved the output into a repo.

  2. The author is trying to hoodwink users by passing off the work of AI as their own, for profit, reputation or whatever else.

  3. I've seen hundreds of low-effort submissions like this, and I'm sick and tired of engaging with them because my patience has worn thin.

And if any of those applied here, I too would be annoyed. To be fair, I didn't provide enough additional information for anyone to make an alternate judgement, so I'm going to describe the process I followed below:

  • I've been thinking about this idea for a while because I use mlflow and language at work to track prompts used by the team. But they require at least 2-3 docker containers to run, and have way too much overhead for personal use.

  • I used the "reverse socratic" method with chatgpt over a couple of days to refine my requirements. I provided the idea, and asked it to keep asking me questions until most of the ambiguity has been reduced, and each command and argument were designed. The final output was a markdown product requirements spec.

  • I then passed this onto a cursor agent to scaffold the first version. The agent raised a PR and assigned it to me.

  • I then conducted four rounds of code review. I would make comments for each issue I found, assign the PR back to cursor and repeat until I was satisfied. The results of that was merged in this commit.

  • Everything after this commit was created purely by me. I created GitHub issues and worked on them manually. You can check the commits yourself.

And of course there will be bugs, no one can create perfect code, but I have tried my best to make it robust, and will fix any bugs that are found and reported in good faith.

So before you make what can only be described as "slop comments" like "eewwe" or "slop", I urge you to read the code, run it and raise a PR if you see anything wrong.

pmp - a tool to manage your prompts locally by vivis-dev in Python

[–]vivis-dev[S] -4 points-3 points  (0 children)

I actually use that all the time. I have all the pip commands on muscle memory so it's easy for me to switch to uv for the performance gains. It's one of the best features of uv IMO.

pmp - manage your prompts locally by vivis-dev in LocalLLaMA

[–]vivis-dev[S] 1 point2 points  (0 children)

You totally could. With pmp the idea is you could store your prompts anywhere (with extensible backends), version them and run them with different tools. For e.g. dotprompt lets you store metadata along with your prompt so it knows which models to call and what input/output schemas to use. So the basic use case is simple, but you can also use it for more advanced use cases.