Django, Postgres, React, Docker, Heroku, AWS S3 for static frontend deployment.

I was digging deeper into the species selector and started playing others. It really makes for a realistic bird watching/listening experience :)

Thanks for making this!

For anyone else curious, on a touch pad you need to do the two finger tap on a country to get the data to appear. Then click into the result.

In my experience a decent chunk won't, so the same info needs to be sent with email.

Something like Clerky or find a registered agent, or use an attorney for everything?

Relatedly, can anyone say if it's better to file with clerky instead of a registered agent?

cmd + b to toggle it open and closed

cmd + [any number] focuses split panes (and opens one if it doesn't exist yet)

control + [any number] to focus different files open in the existing pane

Make it based on the amount of runway you want to spend exploring this sabbatical and what you want to accomplish with your time while you're off.

E.G. a list of things to see, experience, and hobbies to pursue (possibly with specific goals/outputs, but then again I don't want that to stress you out).

It swears it has never heard of it or anything about the previous PDF (rather, it suggests you go search the web).

So, at least it doesn't seem to leak your upload to other users. But I wonder what it does with the info.

out of habit,

spreading my browsing over several browsers (because I think competition is good),

cross-browser checking work on my work since I know there are users using it (both design and javascript has occasionally looked/worked differently from other popular browsers).

and lastly I like the non-business model feel of Mozilla

Perhaps the poster is the author of article, and possibly the user gondaloof (they are both green accounts).

Or maybe the author of the article is just paying attention to HN.

Then do those tasks separately, usually the backend first, and then pass it/assign the frontend task. The backend task is only considered finished when there are passing tests written with the frontend consumer (developer) in mind, proving they are provided with everything they will need. Document the API in a way/place a frontend developer can knows and understands.

If you write the requirements for the tasks very clearly, the whole process could go smoothly without a lot of back and forth between the backend and frontend developer. But sometimes there are things that weren't foreseen and so there could be a bit more to go back and do on the backend.

More often than not there are folks that are better at/hired for backend or frontend, so only assign the appropriate tasks to each of them. Sometimes there are full stack developers/solo developers who can do both. In that case I still follow this approach.

It's open source.

NotePlan 3, a note taking app that uses local markdown files.