0 is usually for operator

Dave, this may be too personal, but have you done a lot of bit stuffing in your career? I have, I think that it made a man out of me.

I don't remember this at all during the past 10 years... then again, I don't make many calls.

In any case, point taken, I didn't read the original post correctly.

They've got their nice little base 10 system and they start counting at 1.

I'm looking for some suggestions. I'm about to graduate with an honors bachelor degree in physics with a minor in comp sci. I'm not exactly sure what kind of jobs I should be looking for. Something like coding javascript doesn't seem too appealing to me, but I don't know what kind of jobs are open to me with my degree. I was thinking of looking into data science. Any ideas?

Are you wanting to include physics as part of any job search or just looking for any programming job?

Both really. Something related to physics/science would be great, but a pure programming job would be fine. I'm just trying to figure out what kind of higher paying and more specialized roles would be interesting for someone with my background (and where I'd be attractive to employers) so I'm not just applying to w/e generic junior developer jobs.

w/e junior developer interviews are loaded with computer science questions and programming puzzles

Yep. 0 is usually "i want to talk to a human, k thanks"

I'm having trouble thinking of a job that wouldn't hire a physics major. Aside from doctor and lawyer you can pretty much work anywhere you want.

One of my best coworkers has his degree in Physics. He is a fantastic debugger / problem solver.

I took my physics degree straight out of college to (checks notes) - mail room, delivery driver, landscaper, waiter, home theater installer, network engineer and eventually at age 29 - programmer.

Yep, confirmed you can land any job.

Physics and Math majors don't have trouble finding good jobs

In 1992 in Kansas City no one was lining up to hire me. The only people I knew who got real jobs right out of college were accounting majors and engineering majors.

I should have immediately moved to Silicon Valley. Actually I should have gone to college in Sili Valley - 2 years at a community college then transfer.

I was browsing posts from 2011 and found Jeffrey Epstein's lesser known web hosting hobby, his HTTPS tutorials are top notch

lol ok thanks for the reassurance everyone. I was definitely a little worried about how my degree would look to jobs in the real world.

Unfortunately some of job searching is being in the right place at the right time and who you know. Also there are other factors like are you willing to change cities, etc. But keep at it. Even if you land a so-so job now there's no reason you can't keep searching for that dream job.

My first online interaction with a computer used a teletypewriter that punched a paper tape, that was then read in by the PDP-9. It responded by punching out a paper tape, the teletypewriter then read the tape and printed out the reply. #Methuselahisayoungster

Your degree doesn't matter much except your first 1 or 2 jobs. Then it is based on how good you are and your experience (and ability to do leetcode problems quickly)

Is somebody here well-versed in MongoDB? I need to do some stuff in it, but my previous background in non-relational database languages is pretty much non-existent and I'm having trouble transferring my knowledge from relational to non-relational domain.

As a simplified example of how Mongo joins would work, lets say we have three collections - person (includes id and name), occupation (id and occupation type), and a "junction" collection that has personId and occupationId where rows correspond to people and their occupations. How would I go about getting the list of all people in the "person" collection and their occupations? Or all of the people who work in some certain field? Or the occupation of a specific person?

All of this would be pretty trivial if I was using a relational system, but converting the entire database is not an option so I have to do with this.

It sounds like maybe you should be using a relational system. Non-relational DBs are best when you need one record accessed by an ID or a small group of records looked up by a secondary index. In your case I'd probably store the occupation information with the user.

If you need a list of all persons then you probably don't want to us a nosql DB. That doesn't scale.

I am aware of that and it is beyond me why anyone would model relational data using noSQL, but as I mentioned in my previous post, re-writing the schema is really not an option (many documents in a single collection have varying number of properties and other such things that make it difficult to convert). For this reason, it seems easier just to suck it up and do the required queries on the data as it is, but I'm having a hard time understanding how joins work in Mongo.

Hopefully someone else can chime in. I've never tried to do that in mongo. Mongo has a merge but I'm not sure if it works in an "all union with all" mode like the SQL join you want.

You may have to fall back to gathering both lists of objects and merging them in code.

You can move to postgres even with those issues.

Create a database table with the id in one column and a json column type as the second column for both people and jobs.

Throw the id in the id column and the other data in the json column for both data sets and then create a lookup table for the id's.

Added benefit: Postgres json is faster than mongo.

Well put.