this post was submitted on 29 Aug 2023
23 points (96.0% liked)
CSCareerQuestions
968 readers
1 users here now
A community to ask questions about the tech industry!
Rules/Guidelines
- Follow the programming.dev site rules
- Please only post questions here, not articles to avoid the discussion being about the article instead of the question
Related Communities
- [email protected] - a general programming community
- [email protected] - general question community
- [email protected] - for questions targeted towards experienced developers
Credits
Icon base by Skoll under CC BY 3.0 with modifications to add a gradient
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What’s your background generally. Do you have a degree in something CS related?
I learned more in my first 6 months of hands on work than I did in all of my schooling. So if you have a cs degree and can learn enough of the basics and interview questions you’d probably be fine applying to jr dev positions whether your concentration is programming or other.
Really hard question to answer with that info though.
I have a degree in philosophy, which, as far as I can tell, is more of a "support" degree that says I like thinking and learning a lot. I've thought about going back and seeing what I can do, but I'm honestly so broke that it's not a viable option.
Related, but how much time per day did you put into learning practical skills? I put in a few hours each week, maybe somewhere between 5-10 hours, but it feels like I'm really low-balling the amount of time I should be coding and applying what I know.
I have a master's in comparative literature and I've been working as a front end/full stack developer for almost a decade. (I started as freelance but I didn't love it, personally - but more on that below.)
Obviously philosophy & literature degrees aren't going to directly help you - but they can help you shape your career, if you want. If your goal is to work as a developer in a gigantic multinational corporation, I have no advice - but if you want to stay around philosophy and philosophers, you can do what I did: work for institutions, rather than corporations.
I've been a developer for 10 years and probably 7 of them were at libraries. I've gotten to know colleagues at colleges and universities and it's a great crowd. I'm currently at an academic library and I love it: I get to work in the academic environment, be around the vibrant college vibe, but I don't actually have to interact with students, professors, or really anyone other than developers and bosses.
If you go that route, you should be aware that some jobs will just randomly pay super badly - make sure you're aware of that in advance and don't waste your time. Those institutions that can't meet industry salaries should be outsourcing - which brings me to my final tip on that topic:
There are LOTS of academic and "academic-adjacent" institutions that can't afford developers and so they outsource. The people they outsource to - that's who you want to find. Go to the websites for events and "initiatives" (ie smaller websites, not their huge ILS or DAMS software or whatever), scroll to the bottom, and find "website by FooBarBaz" - and find those people. They're usually small, and, importantly, local development firms and usually specialize in that kind of work - and they pay the kinds of salaries one would expect. So that's another route.
Those "companies" - it's weird to even call them that, because it's usually just one or two people who were freelance and just banded together and called it a company; they hired a few yous and mes and they stick with that their entire careers. They'll often have you freelance for them for a little bit until you prove your value, and then offer you a real job - or just keep you afloat until you find a "real" job.
(Getting back to my "more on that in a bit" from the first paragraph: that's the freelancing I recommend: freelance for freelancers. This goes for inside and outside the academic/GLAM world: a good freelancer will have more offers of work than they can handle - so they outsource to you, take a cut, and give you experience. It's not ideal, but it can turn into a solid, long term relationship, and having a developer as a "boss" also means they'll understand the challenges you'll be facing as a new developer.)
Good luck.
One other tip specific to library/academic/GLAM work: there's a thing called Code4Lib that's basically a community of academic/library developers. They're awesome and they have great conferences. They have a job board, but, in my experience, it's a lot of jobs from those places that don't pay enough - and they post to C4L as though people who work at libraries don't know how to find out what salaries developers expect. Don't bother with Code4Lib jobs - but definitely go to their conferences and local meetups.
This is really good advice. I had no idea I about that area of work. It makes sense in hindsight, but having it written out so clearly really gives me some ideas on where to focus. Thank you.
That was the short version because I had no idea if you actually cared. Even the best dev jobs in the academic/GLAM area don't pay Jane Street money. But, honestly, who does, other than Jane Street.
Anyway, if you want to talk about it now, let me know.
Of course. I am a bit curious about what GLAM is and any other important terms I can search that can help me find this type of work. Generally, I'm mainly curious about the whole starting process, what to look out for, and how to best approach this area.
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.
This is more than I had hoped for, thank you. I also think you're right, that it'll work for me. I'd very much like to contribute to something good in the world, and knowing that this was an option that I overlooked helps immensely. When I've tried "regular" jobs, I tended to not fit into the setting so well, being that I tend to bring up some philosophical question or ask too many questions in general.
I want to run it down real fast, to be sure I got it all:
I do have another question I'm curious about. Can you tell me about how you create your static sites? I've practiced it in the past, but how do you deal with a large amount of repeated elements? Another question is about your study or learning habits. I know we should practice, but getting some insight into how other people do things sometimes yields new information that might work with me.
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.
I have a degree in philosophy (and no other diploma) and I make $200k/year as a senior developer. The degree does not really matter.