Back
Charlie Revett

Charlie Revett

@revcd

👋 bsky.app/profile/revcd.com 🇿🇦 London, currently in Cape Town (sabbatical)
35
Joined August 2024
Load previous page…

The only reason to use Heroku in 2024 is because you're a big org with a legacy system deployed to it, which would cost a tonne to migrate.

I run everything on railway.app, their platform and the team are great.

fly.io is also a good modern alternative.

I consistently fail to follow this advice myself, but in a perfect world I'd like to work as follows:

  • Start indiedev journey
  • Fail rapidly on 20+ ideas until one hits the mark
  • Do not get attached to any idea during this period
  • Work on one idea at a time
  • Grow idea that works until decent income
  • Then start exploring ideas that you like, rather than those that will generate revenue
  • Magic link for wait lists
  • Email and passwords once I know the app is worth building
  • SAML if users request for it

The stack I've used before:

React app using react-map-gl, set up to use maplibre. Then use the protomaps assets so you don't need to use a paid service, e.g. Mapbox.

@levelsio has some decent tweets on self-hosting something similar to this.

Thanks! Looks interesting - especially Maplibre. React-mp-gl unfortunately looks dead. I will have to dig those Levelsio posts. Those were related to his hotels project?

Interested in the prompt, care to share?

'''Below is a job listing from the url:'''+ url +''' I want you to extract information from the job listing, and return a json format. First I share the job listing, then the desired json output structure. Output only the json object, nothing else. Before you start, look at the job listing closely. All the required information is in there somewhere.

- Make sure dates are in a correct date format.
- For the salary, make sure you include the currency symbol (€ or $)
- Give the page a score from 0 - 100, where 0 means the page doesn't look like a job listing at all, and 100 it's most definitely a job listing page.

[JOB LISTING START]''' + page_content + '''[JOB LISTING END] [JSON OUTPUT START]

{
"joburl": "",
"job
title": "",
"jobdescriptionsummary": "",
"jobtasksresponsibilities": [],
"jobpostingdate": "",
"joblocation": "",
"hours
perweek": "",
"candidate
requirements": [],
"benefits": {
"minsalary": "",
"max
salary": "",
"otherbenefits": []
},
"contact
person": [{
"fullname": "",
"job
title": "",
"phonenumber": "",
"email": "",
"linkedin
url": ""
}],
"jobpostingenddate": "",
"company": "",
"company
description": "",
"joblistingscore": ""
}

[JSON OUTPUT END]'''

I see the prompt is a bit weird here since underscores are used to make text italic

you dont need to do that anymore with structured outputs. with structured outputs it will auto format the data based on the schema you give it 100% of the time.

Home
Search
Messages
Notifications
More