Quartz 4

Getting a web dev job without a CS degree painstorming

5 min read

Source:: Realistic expectations of getting a Web Dev job without a CS degree : webdev

Do these things

  • Include SPECIFIC examples of your audience members’ pains problems, concerns, questions, etc
  • Include direct quotes, with supporting details
  • Stick to the present facts — to avoid jumping to conclusions
  • Avoid idea quicksand
  • Avoid prescribing your own solutions
  • Spend just a tiny amount of time at the end, if any time at all, grouping together notes that say similar, or related things

OP

  • “I’m unsure how far any of this will take me career-wise without either a CS degree or some form of certificate such as a bootcamp”
  • “I’m wondering if these cases (of people making it without a degree) are more of the exception to the rule”
  • “…today’s market is over-saturated with a bunch of entry-level web dev experience”
  • “What are my chances of getting a web dev position through just self-learning and building a strong portfolio?”
  • “Are bootcamps in worth it in 2018-2019?”
    • concerned that they are “expensive”
  • “Should I go back to school and get a bachelors degree in CS?”
  • “Is it worth it to pursue an AA or certificate through a community college in web dev?”

Replies

  • “(Breaking in without a degree) is definitely possible, but not without difficulties.”
    • “learn HTML, css, and JavaScript, BUT you should really LEARN them inside and out.”
    • “DON’T underestimate the importance of becoming a CSS master, no matter what area of web development you want to go into.”
    • “Learn about CSS naming conventions (BEM, SMACSS, utility css) and the benefits of each”
    • “You can also look at some CSS architecture systems like ITCSS”
    • “Learn the basics of visual web design. Just general layout principles, visual hierarchy, what a serif and sans serif font is good for.”
    • “Get a high level overview of project management and project lifecycles.”
    • UX book recommendations:
      • Don’t make me thing - Steve Krug (Nroak mentioned this too)
      • The Design of Everyday Things - Don Norman
      • Universal Principals of Design - William Lidwell (fun/cool reference book)
      • Information Architecture, For the Web and Beyond - O’Reilly book
      • How to Make Sense of Any Mess: Information Architecture for Everybody - Abby Covert
      • Exercising Influence - B. Kim Barnes (really useful info for working with stakeholders & customers, and just driving changing in general)
      • The Paradox of Choice: Why More Is Less - Barry Schwartz
    • “is there really a place for CSS floats in modern design or is it just something you run into all the time with legacy code?”
    • CSS resources:
    • JS resources:
  • “Do some projects. Deploy them. Apply to jobs, even if they say “cs degree required.” it’s not uncommon for self taught people to land a job.”
    • “I always get the impression that having the practical knowledge to make stuff is inadequate as you’ll be asked theoretical questions in the technical interview.”
  • “My only regret is thinking that it wasn’t a possibility for many years.”
    • Taking Colt Steele bootcamp
    • Bootcamp is a good option for these people, as of 2 years ago
  • “You’ll have to start at the bottom, but it’s definitely possible”
  • “depends on your city and your area”
    • “With the amount of bootcamps here, it’s hard to distinguish yourself from the thousands of graduates that come out of there each year.”
  • “would say 90% of the devs I have worked with do not have a CS degree”
    • “(self-taught devs) typically learn exactly what they need to make something work but fail to go beyond and learn more of the CS side which is needed for building more performant software”
    • “they can’t make informed decisions as to when certain patterns will not be the best”
  • “without a degree, it will be harder to find a development job”
    • may get “filtered out”
  • “My recommendation is to stop studying and start producing content. Work is the best teacher”
    • Applying for positions before you’re ready is “a great way to find what the market is actually looking for”
  • “A strong portfolio will set you apart though, even at mid level I would say.”
  • Certifications are great “if you’re applying for a job doing the exact thing the certification is for”
    • “The reason I like a degree on someone’s CV is to see whether they’re someone that’s capable of learning things, taking instructions and turning in assignments on time.”
  • Bootcamps were once worthwhile but that’s diminishing
  • “for the love of god don’t learn programming from small tutorials”
    • “A better approach would be to attend some introductory course to programming”
  • “find out what stack the company you want to work for uses (or find a stack you like and find companies which use it) and build something with that particular stack”
  • “Get in the door by showing that you’ve produced something.”
  • “It’s hard to know which bootcamps are good and which are bad”
  • Aside from my first job, I’ve basically never been asked about the bootcamp other than a passing question or two. Generally, past work experience, portfolio, side projects, and any code challenges have been the main topics of discussion in interviews.
  • Some places won’t offer an interview if you don’t have a CS degree or something equivalent
  • “CS degree seems overkill for a web dev job”
  • getting a degree is an “opportunity cost”
    • doesn’t want to “shell out thousands”
  • “A degree is better than not having a degree”
    • Being in silicon valley is a “double-edged sword:” opportunity is everywhere but competition is tough

Graph View

Backlinks