“Talented juniors are doing fine”. Isn’t that a “No True Scotsmen” argument? Are you really saying that anyone who can’t find a job or can’t be noticed when every job opening gets hundreds and sometimes thousands of applications within a week must not be “talented”?

My anecdote is that when I was experimenting with ATS just to see what type of shit show the market was like in 2023 after being Amazoned, LinkedIn showed my application was hardly ever viewed let alone my resume downloaded.

I say experimented because in the first two weeks I had offers via my network and reaching out to a couple of companies who specialized in a niche of AWS where I was at the time considered one of the industry experts (trust me on this). A junior won’t have the network of CTOs and directors I had nor will they have the credentials.

Again if you think there is only a slight difference between how to best use Snowflake a column oriented OLAP database and your standard row oriented OLTP, you’re kind of making my point for me. I even gave you a hint that one way to store data in an OLAP database that you wouldn’t do in an OLTP is right in the name of the database.

And going from C# to C++ I can guarantee you you’re going to have all sorts of issues if you are use to using managed memory based runtimes. The canonical example is doing something like

char *foo() { char *bar = “Hello World”; return bar;}

char *retvalue = foo();

Will compile and might even work depending on the day of the week. But hilarity will ensue at some point and you will get weird errors that are almost impossible to debug.

While doing the equivalent in C#

string foo() { string bar=“Hello World”; return bar; }

string retvalue = bar()

Is perfectly acceptable.