Has anyone experienced a drop in recruiter spam when removing your information from databrokers with those services? I have daily unsolicited recruiter emails in the last few years, and I'm not on linkedIn since 2018-ish, so I have no idea where they are getting my info from.
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).
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
I break down the feature/story into several tasks and label them as A) backend or B) frontend (occasionally there is only 1 or the other but usually there will be at least 1 task for backend and 1 for frontend).
Link those tasks back to the master feature /story item. It will be marked done only when all the associated tasks are finished.
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.
GoAccess to analyze logs in a terminal and some interactivity as well. It was a big step up from manual analyzing (which I think still has its place as well).
I've found myself in situation as well.
Does anyone have advice on how to deal with the fear of handling users/user data for a product that you think people would love?
Is it incorporation for liability protection?
Terms of service docs that state nothing is hack proof?
Getting the right liability insurance?
In depth penetration tests prior to launching and continuously thereafter?
Continuously monitoring for suspicious activity on a server to detect hacks?
Django, Postgres, React, Docker, Heroku, AWS S3 for static frontend deployment.