CSCareerQuestions

GLAM = Galleries, archives, libraries & museums.

If you're looking to work for/with freelancers, the first step is to find them. There might be more straightforward ways, but this is how I do it:

Go to the websites of some local GLAM-type places in your area and check out any big upcoming events or initiatives - especially ones where they've partnered with other institutions - that's a good sign that the thing is grant funded, which means they had money to use for things like websites. (The websites will continue to exist for years after the thing happens so don't fixate on immediacy.)

Then go to the websites for those things and look for web dev credits, and check them out. Go ahead and email - the worst they can do is ignore you - and most people in this "industry" get into it because they like helping people. And if you get turned down (in a "we're not hiring" kind of way), turn it into a career conversation - "just trying to get started, what do you recommend," etc. That can help by getting you an answer to that question but it also shows respect and eagerness and might keep you fresh in their mind when they need someone.

Regarding that question that everyone new asks: what language should I learn: it's worthwhile to note that, in the context I've been talking about, the tech stack can vary widely. A lot of folks will use Drupal type stuff, but plenty more will use react. And, if the work is bespoke enough - and it often is bespoke enough - you can use whatever you want. Personally, I use whatever shiney new js framework I heard about that sounds cool (Qwik atm), but, if shit hits the fan and I need to get it done, I build in Svelte - it's easy, fast, rock solid builds, with fewer dependencies (aka fewer dependabot emails), and very readable.

(Regardless of whether you choose the freelance route or the stable job route, the prevailing thing about this area of tech is that, whatever you build, it needs to last for years without updates or attention. I have some sites on my server that were passed down to me that are from 15 - 20 years ago - they're rock solid because they're very straightforward HTML with minor amounts of JavaScript. Learning from them, I lean towards static site generation, low-js to no-js final builds, minimalist tooling. The sites that fell apart after 3-4 years of neglect were React - it's obviously the dominant framework, but it doesn't do well without attention. And - this goes for any industry but - do good comments. The person who has to go into your code to update some random thing - you will probably never meet that person. Don't make them hate you.)

(Make it easy to change branding elements, I beg you.)

The other option is a "real" job. Colleges and Universities almost always flood the market with job ads, so there's no particular advantage to using, say, Chronicle of Higher Education rather than Indeed.

GLAM institutions, as I said, can vary wildly in their expectations for what's a reasonable salary - but this will be across the board. What I mean by that is, if they offer you 45k, your boss will probably be making 55 - and they'll dress like they make 55k.

These are, almost invariably, wonderful people. They accept lower pay for 1) the feeling of contributing meaningfully to the world - and that's not nothing, for real - and 2) for quality of life. My boss at one such institution referred to herself as a "free range librarian" - she would start her day in some coffee shop, show up to the office at 11, bring her laptop when she went for a long lunch, etc. Her work was judged by the quality of her work - which was always good - and not by bullshit metrics or face time with the c-level. There are no important deadlines or other bullshit stress in those places - there are no emergencies in library science, as they say.

GLAM places won't flood the market - not reliably - so you may want to go to their actual websites and go to their Careers page. This goes for the ones that pay well and the ones that don't. (Yes, you can write a scraper and make yourself a feed. It's fun!)

Finally, what is probably the Holy Grail for me, the true endgame: federal jobs. The federal government hires developers all over the place, from the CIA to NIST, everybody needs us. And those federal benefits are amazing - imagine having a pension - being able to spend your career just doing your thing and not just focusing on having enough money to someday spend a few years retired before you die?

All federal jobs go up in the same place: usajobs.gov. Jobs go up for 2 weeks and then they're gone. Forwarning is not offered.

I think that's all I've got for now. I hope it helps but no worries if it doesn't. But - for me, anyway, it's a great career fit.

The idea of going back to the private sector and spending my life trying to improve the wealth generation of millionaire stockholders - and helping the middle management guys get their Christmas bonuses - I can't fathom it. I spent this week building a site in Qwik JS for a thing about the 1919 race riots. I didn't even know there were race riots in 1919. When it's done I'm going back to a larger project that's both an image gallery and a crowdsourced transcription tool for civil war letters - handwritten letters and diaries and drawings that are digitized, which, like, that's great, but - this project will allow people to search the content, and not just blindly hope they stumble across something relevant to their interests - it takes these dusty old letters from being a nifty pastime for the civil war enthusiast community to a real resource that can be used to meaningfully add to the common understanding of what the civil war was actually like.

It feels good to know that the work in doing is helping people learn and grow and understand. If course I talk shit about how long it took my academic-side colleagues to get me the i18n translations that were allegedly so important to them - but I secretly love what they're doing and I love being able to be a part of it. As an autistic academic failure with an inability to write a 5 page essay but with savant-level logic skills and extremely rigid and inflexible ethical biases, this is the perfect fit for me. I hope it is for you, too.

Holy shit I never posted my reply to this. I was at the doctor's office waiting for hours and I wrote what felt like a million pages. I'll post it when I'm home from work.