This is complete conjecture on my part, but I bet if you're late 20s - early 40s, you probably have some form of pc/laptop laying around. But people 50+ (gen x / gen boomer), a phone is likely all you use or own. My mother, aunt, et. al operate totally through their phones. The same is true for my pre-teen, teenage cousins or cousins children (ipad generation).

Pretty sure there was even a Need for Speed game on Frostbite which was... huh.

But it was a CS program, not a SWE program, the two of which the industry has confused for all of time (though there was an actual Software Engineering course offered as well).

I've not seen any burn-in.

All of these burnout 'tests' I've seen (this one, and RTings as well) purposefully use static content and are basically abusing the panel in a way that is specifically advised against. I find them pretty useless for anything not an office TV on the wall running CNN 24/7, which I will never be doing myself.

I don't think anyone familiar with the tech will deny using these panels in such a way will cause burn-in, even the test here:

> ...static desktop content such as web browsers, document editors, and spreadsheets, along with creative apps like Photoshop and Premiere. We don't recommend using an OLED monitor like this. These displays are best suited to content consumption[...]

I think it's pretty avoidable on a TV, the real issue comes from what you need out of a desktop monitor. I have a Dell/Alienware (Samsung QD-OLED Panel) that's about a year old without any visible issues, but it's still early to tell in that case.

The tech has gotten better, but the problem still very much exists.

Remote: Open

Willing to relocate: Yes

Technologies: Java, Scala, Python, Angular, React, Apache Spark, SQL & NoSQL, Dart, Typescript/Javascript, HTML/CSS/SCSS

Résumé/CV: https://drive.google.com/file/d/1tNLYIjtH8dgBSMGPbVg3qA0-6q_...

Email: hoglan (dot) jd (at) gmail

Hello!

I'm JD, a Software Engineer with experience touching many parts of the stack (frontend, backend, databases, data & ETL pipelines, you name it). Most recently, I spent several years at Google working full-stack on applications that supported our customer service teams. I then switched to working on facilitating our teams through building frameworks, teaching, and overall enabling them to quickly launch applications.

Prior to that, I spent a couple years at First Orion - a smaller data company - helping found & build out a data engineering team as one of the first engineers. We were focused on building data pipelines and models to protect our users from malicious phonecalls. If you know the phrase "Scam Likely", we were a pioneer :)

There is a noticeable gap in my resume where I was dealing with health issues from 2022 - 2024, but am looking to rejoin the software industry. I'm passionate about helping others through my work, teaching, and building tools to improve the experience for end users - including other developers.

Another point people bring up is that Capcom has been adding micro-transactions post-launch to some of the new Resident Evil remake titles, that effectively power you up to some degree... In the same way that a mod (or cheat engine or whatever you want to call it) could do for free.

Some of these mods turned into games later (Chivalry, Black Mesa, Insurgency come to mind) but without investigating I'm not sure they even use Source anymore.

The important part of pair programming isn't really the programming per se, it's the discussion.

It also requires some amount of conversational art. As for being self conscious about things, you would have poor coworkers who make you think that or some unfounded worry. A good pair programmer can have a discussion without making you feel like an idiot - much the same as a good code review.

I may end up starting from scratch and seeing what I can come up with and get further feedback from there.

Do you have some specific feedback or bullets that stand out to you? Most of Google tech is all in-house stuff that nobody would recognize, outside of a few open-source counterparts (Blaze -> Bazel). I'm confused how my resume could better convey what I'm good at. I can say I worked with Java, Angular, Typescript, etc. But that's all exceedingly generic.

If I say something like "automated X thing in WombatLand using BlogSplort tool, saving 20% of engineering time" I don't see how that is more useful than saying "Automated the creation of full stack internal web-apps to launch in a production environment [...] saved hundreds of ENG-hours for teams launching internal applications"

It's possible because of a couple reasons. The market is cold right now, and most of my network is _still at google_. There are a few folks I've worked with that have left for other places - but those places are either in hiring freezes or actively laying people off for the last few months.

You're partially right, though. Maybe I don't know how to utilize this network efficiently. Friend of friend etc, is probably something I need to work on more.

> Why would you spend that much time applying for jobs with that type of success rate?

Because I need a job?

I've spoken with recruiting firms before that literally told me companies asked them to stop sending people who were hired as a newgrad to FAANG.

If you are a new-grad and you're targeting a 'glorious' FAANG position, I would imagine the percentage is quite low.

I think I've made it to a recruiter screen around ~10 times, and I've had less than 5 actual interviews follow.

I have 6+ years in industry, 4 and some change of which were FAANG (which everyone believes is a golden ticket into any company). And I can't even get an interview.

I'm with OP. The grind is straight up depressing, demoralizing, soul crushing. I'm close to moving in with family just to preserve my money at this point.