No idea, I guess I'd have to learn machine code, Fortran and some COBOL. That's not going to make me millionaire. I'd look for the first opportunity to code a spreadsheet in some way, even not interactive.
Grow some crystals, build some counters, take on DoD contracts to run global surveys monitoring background radiation, expand the airframe fleet, do some broad area photography on the side.
That made one of my former bosses (an Australian) a millionaire several times over in the 1960s.
Hell, pretty much any Cold War era DoD contract would rain money .. and there was more going on than just weapons development, SIGINT and counter measures ran hot.
I have no "micro-architecture noSQL skills", I do have a few million battle tested SLOC's out in the field, know C, Fortran, ASM (for multiple archs), physics, robotics, a bit of electronics, wet photography, geophysics, mining, agriculture, etc.
I'd begin developing a very portable, very comfortable programming language and environment. Something akin to Pascal or Python, portable like Lua or SCUMM, less philosophical than Lisp or Smalltalk. I might not become a millionaire, but it'd be a lot of fun to start my "line of business" software development career as early as humanly possible.
Yes absolutely, it'll be 5+ years before anything like this is remotely conceivable. But I'll be working on it! When it does become possible then I'll be there immediately.
Patenting all basic computing algorithms and data structures that were not published yet. And add "on a network" to everything else already existing.
Maybe patenting first a few common enough practical things (I don't know, even cardboard boxes for pizzas) to have enough money to lobby legislators for accepting the big patents of above if they weren't accepted back then.
No but as others said, you can buy stock or buy up buildings in the high priced cities. In the 60s, no one wanted to live in the cities and all residential properties were cheap. For example, the Boston South End was very cheap until about the late 80s.
Wait till the weekend IBM tried to contact Gary Killdal for an OS for their new PC, and buy Seattle Software's CP/M clone to license to IBM before Bill did. ;-)
Oh, wait, that's not noSQL skills, that's people skills.
More in the spirit of the question, though, one would at least know which architectures to focus on (and I speak as an erstwhile OS/2 developer here...)
lmao, I was just wondering myself what skills in tech I would actually have in 1960s that was useful. As in: how much of what we believe to make us skilled is actually just standing on the shoulders of giants
I understand that this topic always riles people up, but I'm still curious about the technological feasibility of the problem using computers of the time.
About noSQL, all databases where noSQL back then.