1,567 karma · joined August 25, 2018
* had someone make a giant cheat sheet with interview questions and taped it to the wall behind their computer. Part way through, the tape gave out and covered him.
* had someone attempt to lip sync the answers. The guy talking and the guy on screen were not the same guy. There was a bit of pretend 'oh just lag' for a while.
* Person we interviewed was not the same one who showed up for work. Great answers, great experience on the interview. Asked about some things we had talked about for quite a while - and he could not recall anything. Came to realize not the same person.
* the glorious mechanical keyboard furiously googling for an answer.
* the sample project they were asked to create as starting point for the interview, they had never run before. They sat and read through what was likely AI generated docs to run the app. Took them a while to realize they needed something other than Java 8 installed to run the sample.
(Never flown into that one as not an ATP. I'd never be able to get closer than College Park. Even that was a non-trivial exercise in paperwork.)
I did try my hand at a translation tool, as it was all i18n up proper. Watched one guy blow coffee through his nose when I demo'ed - and the 'BACK' navigation was the French word for a persons back or something like that.
One question: is there going to be another 3.x release? The popup takes you to a 4.x release, which is great if you are on 4.x. If it hit EOL, it makes it easy for us to force the update. Right now, it is in a bit of a weird in between.
We picked up a house that needed updates. A few miles from work (were I to drive in) and on a lake. When we looked at the house, it showed terribly. We had replaced our bathrooms and a few other 'major' things in our previous house, so what might scare some folks is a few hundred to a few thousand at home depot and some possibly long weekends. Chunk by chunk, we've been making the house the way we want it.
I should be doing some drywall this long weekend. Way to dang cold to go out and pick up supplies.
Ryan, if you are out there reading this - ty.
The point here is that Java is getting updated and the core JDK is just fine. We are seeing components drop support for Java 1-8, requiring 9+. And yes, that could happen in any ecosystem. It is happening in Java ecosystem today. If you crawl GitHub and look at what is vibrant and what is becoming abandoned, you will see the unmaintained legacy stuff stuck on Java 8. CVEs are a terrible way to say security risk - but it does show trends.
Since about 80% of our Java apps are SpringBoot based, when SpringBoot 2.7.18 being the last 2.x community release that reached EOL in November of last year. That version released with Spring Framework 5.3.31 - Spring Framework is currently 5.3.41 or so for those getting commercial patching. This is the last version that supported Java 8 through 11. Similar issue with MapR. This traps people on specific Java versions, which then traps them to an aging ecosystem of components.
The parent asked - why not target Java 8? That is why. If the parent asked, should I be compatible with Java 21-8, I'd say fine. It is a company's fault if they found themselves on an EOL product. Please, for the love of god... don't enable teams to remain there by making ANYTHING that requires Java 8.
None of this is hard until you have so many that it is.
Watching a couple hundred of them try to get out of a parking lot was comical.
I'm not a mayo fan, so was a condiment for guests. Whoops.