21 karma · joined June 15, 2012
With this approach you can enforce that Claude cannot access to specific files. It’s a guarantee and will always work, unlike a prompt or Claude.md which is just a suggestion that can be forgotten or ignored.
This post has an example hook for blocking access to sensitive files:
https://aiorg.dev/blog/claude-code-hooks#:~:text=Protect%20s...
You’re blog post was 1000% better than the landing page, because it was real. Stick to that voice. Replace the stock images and marketing-speak with halt-and-catch-fire design/quotes, code snippets and sample output.
Don’t try to get customers. Get early adopters who share the vision and want to come along for the ride as you experiment and push the envelope. If you’re vision is clear and speaks to a real pain (getting structured data from the web is a pita) there will be early adopters willing to pay. Those same people are your best market and will make great future employees.
LiftForward is a marketplace lending platform for small businesses.
We're looking for our 4th (and 5th) full-time engineers so this is a rare opportunity to join a well-funded early-stage company. Just raised $250M so things are really heating up.
* Fast growing and profitable early-stage fintech startup
* Small team, so you will have an opportunity for a high-impact role
* Developers have lots of autonomy
* Great pay and a low-stress, engineering-driven culture
details here: http://liftforward.workable.com
or email me mike ~at- liftforward.com
Only exception is if someone asks comes into restaurant and goes to each table asking for money. That just drives me nuts.
I can't tell you about my way of dealing overconfident people because I don't want to brag. I'm the most modest person you'll ever f-ing meet. Way more modest than you or anyone else on this forum.
The best thing you can do now is engage the people who are interested in your app. Don't wait until launch to start communicating. Use the next 3-4 weeks to validate your assumptions by talking to as many people as possible. Making sure your app solves a real problem that your customers want solved is the best way to get traction.
Once you get into production it's a different story. A good ORM makes it easy to swap to a different DB without need for code changes. What it does not help with is the much bigger problem of how to migrate the data, indicies, backups, replication, etc. that you'd have in place for a production database.
"In well managed companies, Bad Attitude + Good Work = Your Fired" -- Dave Goldberg, Survey Monkey, http://firstround.com/article/How-Dave-Goldberg-of-SurveyMon...
Also there is a great example project available here: https://github.com/dgeb/ember_data_example