DeprecatedCompatV2

Microsoft Word for my resume. I'm not sure what I can do to change that, I don't want to risk a(n accidentally) badly formatted resume losing me an opportunity...

...is the second to last panel what it looks like?

As someone who switched from another domain to tech, I suggest trying to reason through your hesitation to switch away. Do you want to stay in tech because you like tech or because you're afraid of "giving up"?

In my other domain, I worked hard and did OK, but not stellar. In tech however, it's a completely different story. The other domain was "cool", and I don't regret what I learned along the way, but tech clearly comes easier to me compared to someone doing well in the other domain.

You need to be honest with yourself before you make the decision to switch. Are you running away from tech or towards something else?

Android belongs on the bottom of this, respectfully.

I recall snapshots not being quite as cheap as on ZFS.

This is not the kind of ad most people are talking about though. This is like Amazon trying to get me to buy insurance whenever I purchase electronics (which I never do, of course).

You can also use Intellij Ultimate, the only big missing features are project config if you have mismatched versions of Gradle/AGP/Kotlin as well as the profiler.

Based on the sparse information in the article, they're training the model based on actual data points, not just feeding the data in human-readable format to a LLM.

Wow this is awful on mobile lol

How do you feel about Kotlin?

Here's a simple approach:

• Basic auth via a custom header, like X-Auth
• JWT auth on Authorization header
• uuid on the JWT (as a claim) that gets stored temporarily (until it expires) to allow the server to revoke the token

Initial request -> server looks for Authorization header, falls back to X-Auth header -> generates JWT and sends back to client in Authorization header (or whatever makes sense)

Subsequent request -> server looks for Authorization header -> checks JWT against revocation database/table and that it isn't expired

Subsequent request with expired token -> server returns 401, client retries using X-Auth header -> server sends back JWT on Authorization header -> client updates locally-stored JWT for future requests

There are probably ways to make this more standard or optimal, but this is a simple approach.

It can depend. Sometimes sprawl is car-centric because it's heavily developed with no alternative, but sometimes there'a a lot of undeveloped land in between things.