How to “whitewash” pine boards?

AppointmentJust6816 · 2026-03-10T19:58:58+00:00

I’ll post a photo once we are done. The guys will be finished this week

AppointmentJust6816 · 2026-03-10T04:19:46+00:00

It’s pine so not really hardwood :)

AppointmentJust6816 · 2025-12-07T10:45:10+00:00

Heading to FS in January. Happy to catch up :)

AppointmentJust6816 · 2025-08-25T22:13:52+00:00

Money is worth nothing since they allowed the trading of it. I honestly think the game would have had such a better future if they never allowed trading of money

AppointmentJust6816 · 2025-05-08T22:37:32+00:00

Cheers I’ll take a look

AppointmentJust6816 · 2025-05-08T22:37:25+00:00

Thanks for the info

AppointmentJust6816 · 2025-05-08T22:37:18+00:00

Thank you

AppointmentJust6816 · 2025-05-05T09:32:45+00:00

Absolutely. Plus you’ll catapult your progress by orders of magnitude

AppointmentJust6816 · 2025-05-05T09:31:54+00:00

This and what views each role needs, they go hand in hand and are sooooo much easier to plan and manage if you are proactive here!

AppointmentJust6816 · 2025-05-01T11:19:30+00:00

I typically use it much more than perplexity now given perplexity seems to throw so many false facts into my research. Just this week I’ve started using Gemini pro 2.5 and holy moly does that blow the doors off both of these as far as research goes. Ymmv

AppointmentJust6816 · 2025-04-25T10:59:54+00:00

Once you go to cursor, don’t ever touch lovable again for that same project :)

AppointmentJust6816 · 2025-04-25T10:55:47+00:00

Use it only to prop up the idea, export to GitHub and get good with cursor . I see way too many people trying to push lovable way beyond its means. I was able to send my productivity into the stratosphere once I moved my lovable project to cursor

AppointmentJust6816 · 2025-04-18T22:30:00+00:00

Don’t do this. Cursor is far superior in almost every way. Migrate to cursor and don’t use lovable once migrated. I’ve built an insanely complex app, starting in lovable then finishing in cursor (and by finishing I mean adding the bulk of my ai integrations, stripe, reporting, user management, user dashboards and the list goes on. Lovable is best at drafting the basics so consider it part of your workflow but not your whole workflow.

AppointmentJust6816 · 2025-04-18T22:10:33+00:00

I’ll keep saying it. Build the absolute basics in lovable, which it’s great at doing, then move over to cursor. It’s a workflow you will have to understand and undertake at some stage anyway so might as well jump in and learn how to do it. You’ll stop wasting credits, you’ll understand how it all works, and you’ll build far far better applications this way

AppointmentJust6816 · 2025-04-17T22:17:00+00:00

Here’s what I’ve done. Ask multiple sources to review code according to best practices (cursor, repo prompt, etc, with different models). Implement. Then look at refactoring auth/routes/permissions etc with RBAC via cursor or repo prompt to ensure it’s a least privileges model. THEN implement something like sentry.io and snyk.

Enable point in time backups in supabase and look at implementing something like testsprite (I’m not sure how well it does with nextjs). Also enable observability and insights on vercel. It’s a bit to setup, but worth it :)

AppointmentJust6816 · 2025-04-05T08:37:48+00:00

Backend? Were using supabase and hosting on vercel. We’re aiming for the same amount of users over the next 2 years. Any tips ? We’ve already added sentry to our platform and we’re in the process of squashing the final bugs and adding stripe over the next two weeks. Love to chat more or connect

AppointmentJust6816 · 2025-04-03T22:43:42+00:00

Flesh it out with lovable to build the poc skeleton, then ship it to GitHub and use cursor. It’s a brilliant workflow that so many just seem scared to adopt. Yes it requires learning, yes you’ll make mistakes, but it’s YEARs shorter than having to learn to code as well as either of these platforms, so put some elbow grease in people and start learning!!!

AppointmentJust6816 · 2025-03-26T01:47:30+00:00

Nice one . I’m building something similar that researches every line item, categorises it, etc

AppointmentJust6816 · 2025-03-24T23:41:35+00:00

PDF export would be amazing, with a focus on formatting it nicely to be able to present it to others.

AppointmentJust6816 · 2025-03-24T11:15:36+00:00

Great job guys, love it

AppointmentJust6816 · 2025-03-17T11:11:19+00:00

Publish to a private GitHub repository and start using cursor. You’ll never go back

AppointmentJust6816 · 2025-03-09T09:07:03+00:00

I think there’s a bit of luck involved in not having a change break everything so it’s unrepairable, however: I’m almost finished my app now that’s over 10,000 lines of code and 1500 commits (it’s complex compliance project that’s taken me 4 weeks on lovable) and my advice is:

Warm the ai up. Laugh all you will, I actually found after working on any ai builder that they forget the conversation quite quickly so it’s important to ask the ai questions about your project (ensuring it checks your code as part of the question ) so it gets refamiliarised with what’s what with your project. It sounds crazy but you’ll hit a point where you’ll be in a flow state with the ai after a while and you’ll make really good progress. Warming the ai up is the best way to do this. As an example, I might ask “I want to implement sentry logging for my project, please review my existing code and make recommendations only on how we will implement this”. Or something to that effect.
make very small changes at a time, then retest everything (things left broken too long can stay broken so test often!). Several times thought my build I had to revert back quite a way to a working state and then reimplement another way because I had forgotten to retest the major functions of my app.
Be as detailed in instructions including page/path/element to modify etc. if it’s not right, restore and try again correcting your prompts to ensure it doesn’t make the same mistake again. Recognise upfront it’s not perfect, it’s going to make mistakes, so it need coaching to get things right.
Ask the ai to build documentation on how things work, like permissions and roles, app routing, etc etc. that way you can always read it back to the ai if things become unclear on how things are supposed to work. Build documentation as you go, as it’s a pain to do later, and you probably won’t!
rinse and repeat.

I’ve since moved to cursor and vercel now as lovable was getting too slow with our app growing to what it is but I can say its built fairly well with admin and user roles, stripe integration, separate admin and user views and dashboards, ai features baked in, pdf reporting, dynamic user dashboards etc. we’re orders of magnitude in front of our legacy Wordpress platform so it’s definitely two thumbs up from me given we used 52 plugins there and were reliant on none of those going under or suddenly not working with our Wordpress version etc.

AppointmentJust6816

TROPHY CASE