bmoathn

I mean across my personal projects i'm looking at around average of 40 Commits per day just myself. big days 150+. 7 days/wk, and that's NOT my regular 9-5 job. So i believe the volume is there. Yesterday I merged one feature integration branch that had 250 files changed and over 28 thousand lines changed. The whole thing was started from requirements, implemented, tested, and merged in less than 24 hours.

It's a crazy development world we are living in...

interesting concept. feels high gain at 1/wk. like, can it subscribe to my garmin connect or something?

I'd wager this is interesting, seems there are a lot of users here building things on the side (or main projects) that need clear UX if they're anything like me, they don't have that UX background to know the best practices. I know I just clicked your link anyway...

Maybe I'm missing something about the dev process here, or maybe the title needs adjusted. But, isn't this standard practice? We have a bunch of unit tests in main, and a PR is green on those before merging.

Sorry if I'm being dense, what am I missing about this?

are you asking what moat you can establish around a product that uses customer-facing LLM inference?

IMO, it's incredible the ability to build things rapidly, solo, and extremely cheaply. So as long as that's the case, the only moat left for you is customer access, customer loyalty, and pricing (though I think that last one is arguable)

The challenge as I see it is that for new products in this space to be successful, the solo dev either needs to BE or be partner with someone who has deep intimate domain knowledge and large network for the pain point their product solves (e.g. a 15 year supply chain manager for large manufacturing company rolls into solo dev a meaningful solution to a problem in their domain) or else the solo dev needs to already have a large social reach they can leverage to access customers.

Those are the kinds of moats I see being most effective.

Well I mostly had claude create skills for itself by working through what I wanted out of each stage of the process. So ultimately my workflow uses a skills toolbox that looks something like [anti-slop, brandkit, campaign-director, content-creator, output-enforcement, article-writing, visual-design, ig-content-pipeline, image-to-code, imagegen, infographic-creator, performance-analyst, reel-production, chart-reels, seo-growth, etc]

It's working ok, but not perfect. I'm not sure how much more value I would see from some of the paid services that are advertising heavily about automating the process

You can see links in my profile and probably find the IG pages if you're curious how it's going.

oh wow this is a lot more developed than i imagined - was expecting a github repo with some skills or something, this is a whole product. Some initial feedback:

Personally, if it's just informing me (hot formats, creators, topics) I am not sure I would be paying. I was hoping to see that i could connect my posting api and have it plan, develop, and run a whole campaign. - follow accounts, interact in a reasonable way with their content without spamming - design, and create a content backlog - make the posting calendar - automate the posts, comment replies, and dm replies

I like your site!

interesting, i've been thinking about this also in that I don't use tiktok but I think i need to try to get into it to market my work. feels daunting so I'll probably check out this project.

For instagram i did a similar thing with skills covering identifying formats that hook, generating campaign approaches, and then designing the actual content. mixed success so far but still early.

Oh wait so did you create your app within their little marketplace thing?

Pretty intriguing, odd but interesting site and approach. I kind of like it. I'm tempted to press the button... but i have literally no idea what is going to come out of it. Like am I sending out a fiver for the same thing if I just ask Gemini to give me a brand review of my website?

I honestly like the oddball feel of the main site. I am SUPER curious what your usage/adoption has been?? Also how are you driving traffic?

Cool project at the manyusefultools level!

In that case, awesome! I would recommend that as you go, stand up one or two boards with existing RTOS solutions, and come up with methods to measure metrics both for your solution and theirs. Would be a great way to learn and generate good information for a paper at the end.

I'm seeing that same sequence of stages with my org. In our work, we're currently at stage 3 Bargaining but there are teams here and there leapfrogging depression straight to acceptance. Exciting times if you ask me. The key is really focusing on the test and verification approach imo. Automate what you can, measure/log or proceduralize what can't be automated.

To me, just seems like a pointless statement. Yes, "good" has two meanings and therefore two antonyms... So what? Why compare them. They're independent. It's like saying "what is worse, a bee sting or stubbing your toe?"