jweatherby

Same. I documented my patterns and conventions into a scaffold project +Claude docs and have been able to confidently vibe code my way to very reasonable projects. My stack is sveltekit+trpc

The trick with this wave of fast apps will be getting others to use the things that are built. Sure you can build something for yourself quickly enough, but you'll likely need the rest of your team onboard, which comes with a slew of other problems and complexities.

Same. It's freed up hours to spend with the kids. Time is scarce

In my experience that's where story points come in. "This comparable project took this number of story points, therefore <new project> should be similar, resulting in a comparable amount of time." The usage of story points help to adjust for complexity.

The story points are that data point in the past used to indicate the future.

I mentioned this a few months ago, but have made progress since - I'm working on an alternative to subscriptions for online publications. Instead of subscribing to entire publications / blogs, publishers would register their publication on this network and configure thresholds and pricing. Add a bit of code to the site and a paywall will show up, allowing readers to pay for individual articles. The prices would be minimal, amounting to less than a dollar in most cases. i.e. reading articles using micro-transactions

I know it's been tried before, but I thought I'd attack it with a few different angles - web based, no chrome extension, thresholds to help verify the article is worth it, extensive use of an aggregator to help with discovery and validation.

You can see the work in progress here: https://paperwall.io

Hey, this is relevant to what I'm working on - I'm building an alternative to subscriptions for online publications. Instead of subscribing to entire publications / blogs, publishers would register their site on this network and configure thresholds and pricing. Add a bit of code to the publication and a paywall will show up, allowing configuration per article and allowing readers to pay for individual articles. The prices would be minimal, amounting to less than a dollar in most cases. i.e. reading articles using micro-transactions.

I know it's been tried before, as has been mentioned in this thread, but I thought I'd attack it with a few different angles - web based, no chrome extension, and thresholds to help verify the article is worth it.

Check it out here - https://paperwall.io

Especially considering the nature of this thread, I'd love feedback and what you'd like to see out of a solution like this.

Very much WIP: I'm working on an alternative to subscriptions for online publications. Instead of subscribing to entire publications / blogs, publishers would register their publication on this network and configure thresholds and pricing. Add a bit of code to the site and a paywall will show up, allowing readers to pay for individual articles. The prices would be minimal, amounting to less than a dollar in most cases. i.e. reading articles using micro-transactions

I know it's been tried before, but I thought I'd attack it with a few different angles - web based, no chrome extension, and thresholds to help verify the article is worth it.

You can see the proof-of-concept here: https://paperwall.io/

The better the marketing, the easier the sales.

Better than rolling out an AI to hopefully find the docs you're looking for, it would be better to create an actual framework for the docs. This would remove uncertainty about where docs live and improve discoverability to peruse as needed.

AI and search is only as helpful as the content provided, and most applicable to those already familiar with the existing domain.

If you change the base css variables, you can configure that default spacing and the corresponding ratios stay reasonable. This is how I use picocss for my high density UIs.

The docs are decent enough to configure this.

See my comment above, but maybe this tool, https://showboard.ca, that does most of what you're looking for. Except the address bar auto-complete, that would be next level.

I built a tool, https://showboard.ca, that does most of what you're looking for.

It helps visualize and organize bookmarks into boards, which you can then share with others. It also scrapes the contents of the links, which is then searchable.

You can see an example of it in action here:

- https://showboard.ca/boards/67-engineering-leadership

- https://showboard.ca/boards/15-recipes

Maybe this can help?

I see quite a few lamenting about the lost content and their bookmarks pointing to dead links. I built a bookmarking tool (https://showboard.ca), that allows you to store and organize that readable content (similar to pocket, instapaper, etc); meaning if those articles go dark, you won't lose their contents.

Clean Architecture by Bob Martin. It lays it out how to think abstractly in a systematic way and when to worry about what when designing a codebase. It applies at the micro and the macro level. However, I'd only recommend it after a few years of experience.

If a UI is needed: sveltekit, Prisma, trpc

One app, no need for an API, typesafety baked in at the DB and API layer, client-side interactivity, and server side authentication is easy to work in.

Agreed. Early on, I would enjoy solving a problem with regex, but really, that's a code smell and a red flag beyond basic validation.

Where is the best place you've found to receive this feedback?

I have 2 I've been chipping away at in my down time:

* Showboard: https://www.showboard.ca/ - a collaborative visual bookmarking tool. It started as something comparable to a visual pinboard, but then I discovered https://github.com/mozilla/readability and it turned into a cross between pinboard and pocket

* Tendee https://tendee.co/ - an attendance tracking tool for recurring events (track a team over a sports season) with a wait-list option as well. Technically it can be used to fill the void between a calendar event, an evite and a Facebook event page, but that's such a narrow use case. This one is still very new.

I'm building an attendance management app - https://tendee.co

I had a few itches to scratch:

- one off events now that fewer people are on facebook;

- planning in advance for subs in team sports;

- some work events have max capacity, so building out a wait-list

It's been a good way to play around and learn some tech I've been meaning to get around to, like NextJS and PrismaDB, but I kinda regret not giving Remix a shot.

I just discovered Santorini recently - great 2 player game with lots of replay value, if the mechanics click for you. Otherwise, my gotos are Carcassonne, Century (golem edition for great art) and the classics like backgammon and cribbage.

No, the sharing aspect is internal to the app, so each "board" can have as many users as you like. Neat idea though, I'll have to look into that.

I built a little hybrid bookmarking/notetaking app - https://www.showboard.ca/ It's not built for bulk usage like you're describing, but makes it easy enough to scrape, modify, share and search. Let me know if this is of interest (it has a python backend ;)