It’s typically a good idea to first focus on a stack in demand, then once you have some $$$ you can enjoy the hobby of learning esoteric stuff :)

My recommendation is always the same:

1. Contact a couple local tech recruiter agencies in your city.

2. Ask them for what are the top 2-3 tech stacks most in demand the past 2 years, as well as any relevant certificates companies were looking for, and expected entry level wage for each stack.

3. Analyze those 3 stacks, pick the one that seems best for you.

4. Go learn it, make an easy application for it full stack with an open source DB like Postgres or Mongo

5. Bonus points: setup a basic dockerfile for it and docker compose

6. MOST IMPORTANT: Make detailed “how to install manually, how to compile, how to docker deploy” guides on the github README. Include pictures of your app in the README, make it look good to a cursory glance.

7. Aight now that you have a simple working app on your guthub, pin it on your profile so it’s first thing people see. Link your github to your LinkedIn, add this project to your LinkedIn profile.

8. Now go look up those certs you found about in step 2. Look up the price to get em solo proctored from home. Usually they are a couple hundred bucks.

9. Do it, study, get a cert or two and add to your resume.

10. Okay now go back to that recruitment agency, ask them for help with optimizing your resume. This is a free service they offer, you don’t have to pay as the dev, the companies pay the costs to recruit you, the process is free for you.

11. They will now find jobs for you, negotiate wage for you, and find interviews for you. Keep applying on your own and improve your app you made, study the deeper nuances of your stack, etc

12. When you do get an interview, spend the days prior studying their stack and try to get to the point you can hold a convo about . “Oh yeah, you guys use Fwibble.js? I’ve been really excited to learn Fwibble.js, I have heard cool things about how it is good for wumbling tuples!”, etc etc

Sounds like untreated ADHD mate. Frequently starting projects and then giving up is a common symptom.

Do you have tonnes of 5% to 15% done projects?

If so, it’s because the dopamine hit of (current project) has worn out, and the dopamine hit of (shiny new project) is more enticing.

Do you often burn yourself out early on in the project, your first few days you stay up til 4 in the morning grinding, you progress wicked fast, “this is easy!”

Then suddenly you crash, burnt out, exhausted?

You have to set pace limits on the first days, purposefully stop and take a break.

That rapid fire burn out on week 1 is a big productivity killer, instead literally set the kb+mouse down, get out of the chair and go for a walk. Yes, even though you could keep going, save it for tomorrow.

Try buying an egg timer and force yourself to stop and get up and stretch every hour, and go for a walk after 4 “sets”

Id expect its something akin to average half life or whatnot, such that you can make multiple backups and further improve that number.

Honestly Im curious how something could last for over a few thousand years and not be effectively speaking eternal.

Like at a certain point, if it hasnt failed by 5,000 years, what on earth would cause it to fail after another 5,000 years? What process is slow enough to “erode” the perfectly preserved object that cant get the job done in 5,000 years, but it can get it done in 10,000?

what if you lack the fragments needed to reverse engineer/reconstruct a means to access the information?

In this case the “Fragment” isnt even a fragment, it would be a completely intact start to finish monstrous amount of data.

The larger the “fragment” is, and more complete it is, the more trivial it becomes to decode it.

And since this data is being purposefully stored in a manner intended for future use, it’s very likely it will be encoded in a manner to facilitate and make it as easy as possible to decode in an intuitive manner.

Id strongly suspect every individual “glass” would have some form of “clue” or “how to” at the start of it, that serves as a guide to help the consumer know they are decoding it right.

Off the top of my head one example would be encoding a bunch of digits of the Fibonacci Sequence at the start as character literals (so text form), which even in binary form when inspected physically with a microscope, any scientist would go “oh hey thats Fibonacci!”

Then after that a large blank, followed by perhaps in order the entire ANSI character set from 0 to whatever it goes to now. Or perhaps Unicode.

The whole thing is only like a megabyte or two, so it would be less than 0.1% of the storage data, but having those 2 items at the start of every disk would be an easy way for the consumer to sanity check they are “reading” the data right, and clue them into “yo there’s data stored on here” very fast

This is awesome, I was talking about this with some friends, debating what is truly the best way to store data for long term (on the scale of thousands of years)

Backing up all of human knowledge and history onto such plates actually seems like a worthy endeavor.

Imagine if we had such detailed records about civilizations thousands of years ago!

We have demonstrated time and time again that if you have a bunch of data unencrypted, it is actually quite trivial to reverse engineer it and decipher it.

Dead sea scrolls, Rosetta stone, etc.

This would be terabytes of data, and likely organized in a way to make it very intuitive to reverse engineer even by someone who has no idea how it works.

We could even case study this. Give a loaded one of these slates to some scientists who have no idea how the data on them is stored and have them try and decipher it.

If they can reasonably succeed quickly with no knowledge on how it works, then it should be easy for someone thousands of years from now too.

It’s possible to reverse engineer data you have forgotten how to read.

It’s impossible to read data that you know how to read, but it has become annihilated by time.

The former is far more valuable.