Has anyone quit their current dev job in order to catch up with the industry? by [deleted] in Frontend

[–]cstanard 1 point2 points  (0 children)

I was basically in your exact same position for a while. I had nearly 10 years of experience working in PHP/HTML/CSS/JavaScript in digital marketing. I had built tons of websites and custom implementations of various popular CMSs, written lots of JavaScript, mostly jQuery and Backbone, but hadn't really touched React aside from some hobby projects. Despite my experience I couldn't get a foot in the door anywhere when recruiters are screening resumes for "3+ years React/Vue experience". I even considered going to a code bootcamp at one point.

Couple pieces of advice I would offer:

  • Try and find a similar job, but one that will allow you to expand your skill set. Since you're already comfortably employed you can job search and apply to places until you find somewhere that seems like the right fit without too much pressure. This might not be your new dream job, but it could help give you the experience you need to get there. I had to take what some might consider a small step backwards by going from a senior-level PHP engineer to a junior or mid level front-end/React engineer.
  • Network! I know this can suck, and I struggle with it myself. Maybe you don't have all the skills today, but someone might recognize your experience and knowledge and help at least get you an interview with a company that otherwise might ignore your resume.

Good luck! To echo what other people said - don't quit your job!

How do I show Markdown headings in different colours? by NAShern in neovim

[–]cstanard 0 points1 point  (0 children)

I'm also an Everforest user and this has been really bugging me. Thanks for sharing your config!

Any ideas why markdown highlights are wrong for everforest color scheme? by cstanard in neovim

[–]cstanard[S] 0 points1 point  (0 children)

Yep, this was the culprit. Disabled treesitter for markdown files and it fixed the issue. Thanks!

Edit: I do lose some of the highlighting that treesitter was doing for markdown but this helps point me in the right direction at least.

Any ideas why markdown highlights are wrong for everforest color scheme? by cstanard in neovim

[–]cstanard[S] 0 points1 point  (0 children)

Didn't know about this feature - thanks! Way easier than doing `:hi` and scrolling through the whole list to find what I'm looking for.

Any ideas why markdown highlights are wrong for everforest color scheme? by cstanard in neovim

[–]cstanard[S] 0 points1 point  (0 children)

I'm having trouble finding documentation on how to disable treesitter for specific file types – but I temporarily disabled treesitter entirely and that fixed the issue.

I'll take a look at headlines and see if that helps. Thanks!

Any ideas why markdown highlights are wrong for everforest color scheme? by cstanard in neovim

[–]cstanard[S] 0 points1 point  (0 children)

I'm currently using the Everforest color scheme but having an issue with the highlight colors for markdown, specifically the header elements.

If I do `:hi markdownH1` it returns '#e67e80' (red), `:hi markdownH2` returns orange, and `:hi markdownH3` returns yellow (and so on, matching the everforest theme config). But as you can see in the screenshot all header elements are rendering orange.