I've lived in Georgia (the U.S. state) my whole life, and when I read "Georgian" as an adjective, I usually assume it means Georgia the country. People here typically use "Georgian" only as a noun to refer to a resident of the state. In adjective form, you usually just hear "Georgia" (e.g., Georgia coast, Georgia pines).

I wrote this elsewhere as an expanded form of my other comment here:

In the pictured headline, if "Georgian African American newspapers" is using "Georgian" as a demonym, then it means newspapers published by African Americans from Georgia.

But if the headline is using "Georgian" as an adjective, then lacking hyphenation, it's ambiguous whether it means newspapers published by African Americans from Georgia /or/ newspapers published in Georgia by African Americans.

We rarely use the adjectival form of U.S. states ("Georgia Peaches", not "Georgian Peaches"), so I found the headline a little garden path and initially started parsing it as if it were referring to the country of Georgia.

Then, right below the headline, the text reads "Georgia African American newspapers" which isn't ambiguous and means newspapers published in Georgia by African Americans. That's confirmed by the rest of the article.

Of course, the African Americans in question were likely also from Georgia, so to be pedantic, it's Georgian African American Georgia newspapers.

(I doubt any African Americans from Georgia emigrated to the Russian Empire at the time, otherwise we could be talking about African American Georgian Russian Georgia newspapers ... or something.)

Anyway if I were the headline writer, I think I would have used "African American Georgia newspapers..."

I was born in Georgia-the-US-State, and yet I stumbled a bit on the headline, parsing it as Tblisi-not-Atlanta.

Your careful analysis might explain my brain. (In this particular case. If that is even possible, because my brain...)

Agreed, as an midwestern American. Hearing "Georgian", I would think of the country, then the Georgian era (especially regarding architecture) and only then the state.

Yeah, had it said "Georgia" instead I would not have had the same confusion OP had.

I guess it's one of those unspoken rules we don't know we know.

> Also seems like Gen X has pretty good musical knowledge overall! But probably due to being the 'right age' for having been able to listen to a lot of stuff.

I came to this same conclusion. Growing up, I heard a little '40s music from my grandparents and a lot of '50s, '60s and '70s from my parents. Hip-hop, new wave, alternative and grunge all came along during my lifetime.

I used to work for a credit bureau, and a lender once asked us to build an application that could pull credit files based on SSN only. (Pulling a credit file normally requires multiple identifiers.) Fortunately, someone foresaw the very problem that you mentioned, and we declined to build it.

When the Department of Revenue published the proposed designs, some of them contained the phrase "In God We Trust," while others didn't. It wasn't made clear that the phrase "In God We Trust" wasn't part of any of the designs; it's just an optional sticker that goes where the county name (also a sticker) is usually found on the plate. The miscommunication upset just about everyone because the vote (which was just an online poll, not an official vote) to select a new design effectively became a referendum on whether the state's license plate should contain the phrase "In God We Trust." The Department of Revenue decided to republish the proposed designs without the sticker so that the public could vote again.

Two things that come to mind are sales engineer (tech skills, sales, training) and consultant (tech skills, project management, team management, sales). If you've worked with a particular software vendor's products, it could help you get your foot in the door as a sales engineer for that vendor. You could also do technology consulting at one of the Big Four or a similar consulting firm. And you can leverage your reputation and network to go back into industry if consulting isn't a long-term fit. (A few years ago, I was in a similar place career-wise and went to one of the Big Four for a while. It was a good experience for me because it basically forced me to improve my weaker skills, and it exposed me to new domains outside of my areas of expertise.) The downside is that you'll travel a lot in either job.

"Beasts of expert domain knowledge hidden in shitty codebases" is a great way to describe most of the enterprise software I've spent my career configuring and administering. And it highlights what most users of enterprise software don't fully grasp: You don't buy it because it's user-friendly or because it's the most modern technology; you buy it for the battle-tested built-in domain knowledge.

> you buy it for the battle-tested built-in domain knowledge.

This was my hardest lesson to learn. Code is only as good as the domain knowledge going into it. I love games because the domain is more often than not in the realm of fellow programmers and erudites like mathematicians and 3D animators that capture their domain knowledge in physics, sound effects, motion capture, fluid dynamics, FSM AI, or combining geometric and linear algebra to improve gimbal lock.

An ERP on the other hand captures the domain of accounting, finance, procurement, manufacturing (bills of material), order management, taxes, product lifecycle management, and other considerably less sexy but equally important subjects.

captured a bunch of "domain knowledge" of which only 20-30% is relevant to your business.

let me guess, they did not captured/predicted the domain knowledge required to run the following business huh: - search engine (google) - marketplace for arranging or offering lodging ( airbnb ) - ride sharing ( uber ) - social networks (twitter/facebook)

if all businesses does everything the same way (because some german company thinks it is), all end-products will look all the same. The same way if all chefs is following the same recipe.

IMHO the tools/choices to send invoice, manage orders, product lifecycle can also be a differentiator for your business.

> The same way if all chefs is following the same recipe.

It's more like chefs using the same kitchen appliances, pots, pans and equipment as everyone else. And they do. You use a Salamander Broiler because it does the job.

I didn't even know that an out-of-network provider was involved in my surgery until after it was over. A couple of weeks after the surgery, my insurance company sent me an unexpected check for $3,000. I called and asked them about it. They said, "It's to pay the surgical assistant. They're out of network, so we can't pay them directly." I had no idea that a surgical assistant was even there. (I hadn't yet received the bill.) The insurance company told me that since I had already been anesthetized and couldn't ask the surgical assistant if they were in-network, I didn't have to pay anything out of pocket for the surgical assistant.

I don't have any other recommendations for studying, but as someone who made the transition from IT to GRC, I can offer some advice about getting practical experience.

A Big Four firm is a good place to get started in a GRC career. You'll get pretty broad exposure to the field, and you'll have the opportunity to develop expertise in specific GRC domains.

If you're already working in a regulated industry (especially for a publicly traded company), you may be able to move into a GRC position at your present company. Compliance, internal audit, third party risk management, business continuity/resiliency and disaster recovery are common areas that fall under the broad GRC umbrella.

I worked in various IT roles at a financial services company, and I was able to move into a risk analyst role, then I went to a Big Four firm, and I'm now back in industry.

As far as certs go, CRISC, CISA and CISSP are the most common I've seen among GRC folks, although most of the people I've worked with didn't have any of them.