

They probably have an “evasive maneuvers” button that functions exactly like the close door button on an elevator.
The ship’s AI likely does the smartest possible thing in that scenario and all the other inputs are ignored.
They probably have an “evasive maneuvers” button that functions exactly like the close door button on an elevator.
The ship’s AI likely does the smartest possible thing in that scenario and all the other inputs are ignored.
It’s a meme, but! This is an excellent analogy. A “full stack” dev will definitely make a taco truck app, but maybe that’s all the customer needs.
lol, brain fart.
You get a similar story from Star Trek Protostar. Non Starfleet crew in a federation starship learning the roles as they go.
I’m sure he was just on Porthos XIV or something at that point.
ENT Explanation: Oh snap, we should DEFINITELY add some kind of filter for biological things so that never happens again.
VOY Explanation: A specific plant confused the LLM that filters shit out and it hallucinated a Tuvix.
dataclasses do this for you at the class level. They enforce type annotations at instantiation.
Oh I’m well aware. Took me a solid year to appreciate type annotations for what they are and yeah I’m happy using what we have in stdlib now and not messing with mypy tyvm. The problem is that history is lost to newcomers who have very different expectations. Modern IDE’s mostly solve it though, so for all my Java peeps dipping their toes into the snake waters, listen to your ide
The original NASA logo was the inspiration for the star trek insignia.
So really this is more like a nod to a nodder.
why would you release this cursed artifact from the bowels of the earth.
Dude, even just a “FY,I, you sure about this?” would be nice. I gladly embrace python’s by-all-means-shotgun-your-leg-off philosophy, but the noobs could use the help.
python:
a: str = 1
I was sync for me, but hell yeah, it’s been a good couple of years.
So fucking true. I’ve was in an interview, 2nd round, where the recruiter joined the call mid coding exercise to explain that a different recruiter had just given the position to someone else without waiting for feedback on anyone else and therefore they had to stop all in process interviews. She was pissed and apologized. The guy giving the interview just gave me this look like “they do this shit all the time” and ended the call.
Tech recruiters really can be this dumb. I’ve been on both ends several times.
I remember hiring for a test dev, writing the description for the recruiter, I included all the things I’d like to see. Python, test automation experience, open source contributions etc (this was for a public facing repo).
I get back a question a day later asking if they need Java or not. That felt really out of place so I walked over and had a conversation. Turns out they were filtering out anyone who had more than requested. Python AND Java experience? No thank you.
On the upside once we ironed that out I ended up hiring two people I’ve been friends with for a decade+. Sometimes the recruiters just need help.
Now the other side of things…I’ve definitely had recruiters screw up and lose very good candidates, but it was always for stupid shit like they forgot to send the offer letter for a week or they accidentally put them in the “no” pile.
Heh, this one time we got a recruiter ping our team out of the blue saying they had a candidate. No one knew what the hell the position was for. Turns out the recruiters had forgot about a bunch of openings we had closed like a year before, they just never took down the postings. We asked him how he found the job, and the candidate said he manual went through the thousands of open positions until he found one that fit him. He hired him after the first round and he turned out to be awesome.
That’s just built in with extra steps.
don’t forget the Alaskan Pipeline.
…at the same time?