sco1
Are we though?
Thank god corporate profits are ok...
It's honestly perplexing how major powers seem incapable of learning from history. Short of nukes, bombing a country into submission has never worked. Even now the Ukraine War is here just staring everyone in the face and yet the same mistakes are being made all over again?
Iran has been preparing for this for decades, and has apparently been paying attention to everything going on in the region. What has everyone else been doing? Is it just arrogance?
I tried looking into how to do things the "correct" way nowadays and they seem to have completely changed their app platform since the last time I looked. They've completely locked out the old method for requesting API access in favor of whatever this Devvit thing is: https://developers.reddit.com/docs/
If you want just plain old data access you have to submit a help ticket, which as far as I can tell just goes completely ignored if it doesn't get rejected outright by some automation.
Wait until we're old enough to retire and then can maybe afford it.
More than a year after they took office and in the middle of a war?
Like Elon's weekly 5 bullet summary of what you did this past week :)
What do you mean by this? Not having an IFR rating does not mean you're not allowed to use the navigation aids or the plane's autopilot.
They're not always lighter either :)
Many people, including myself, also like making atomic commits that may not be fully typed yet. Conditioning people to skip the hook(s), doubly so during a gradual typing rollout, just conditions them to skip them always. Leave it in CI where it's checked at a point in time where it actually matters.
Rather than doing this, which does indeed seem like a headache, it may make more sense to skip import following at the very beginning until your core is typed so you can still enforce typing on the leaf nodes moving forward.
> Eventually you get to `#type: ignore` or `Any`s being thrown around to sidestep the CI pipeline, and your typing story has collapsed again
While there are some cases where this is truly the best option, ultimately you get to the point where you just don't allow this, otherwise what's the point of all the effort?
> and for people on the team not passionate about typing, they never worried about it <...> Asking the entire team to become Python typing gurus to sort out these issues was a non-starter.
The faster the core can be typed (and typed correctly), the easier it becomes for those who are less passionate. Presumably someone has done the calculus to determine that this effort is worthwhile, so while the team doesn't necessarily all have to reach guru level, they need to be convinced to continue the work. Removing barriers is huge for this, since as you've noticed once it starts being easy to ignore it's really challenging to stop ignoring.
https://peps.python.org/pep-0585/ https://peps.python.org/pep-0484/
Education wise I likely would not have done grad school right away, at the time a 5th year masters was appealing but the shiny paper didn't really end up doing anything for my career. I enjoyed the work but I would rather have had an employer pay for it. On the flip side a PhD would appealing since I do enjoy the research process, and there are some areas in the aerospace field I would love to explore more deeply. I would likely do CS instead of AE/ME, I originally picked this field because I love aviation, but career wise I've found myself enjoying CS work much more.
I would more strongly consider ROTC; I rejections from military academies and decided to go to the university route instead (aviation generally requires a degree). I still greatly enjoy aviation but I'm not in a place financially to pursue it.
I'm not familiar with how the process works, would JetBlue now have to compete with larger airlines for these assets if Spirit goes under?