Ask HN: Are my web dev skills still relevant?

I can&#x27;t speak from the point of view, directly, as a current web dev, but I&#x27;m 100% confident that the landscape has completely changed -- from the point of view of someone who looks at, evaluates, prototypes in new stacks all the time, and product&#x2F;project-managed modern web stacks.<p>I complain here and everywhere about the insane complexity in modern-day web app dev.<p>The truth is that, after you learn the 20 new tools&#x2F;technologies you&#x27;ll need to become semi-competent in only one stack, it won&#x27;t seem like such a massive shift anymore.<p>I think competition is not that fierce -- honestly speaking as I can -- but that&#x27;s for corporate jobs, etc.<p>And you _have_ to be competent or good or really good if you&#x27;re older.<p>Else, you&#x27;re just going to sound...like you sound -- old and washed up.<p>Not saying you are, or I am, but once you&#x27;re 25+, if you bring the &#x27;Get off my lawn&#x27; vibe, your 27-yo manager-to-be is gonna smell it a mile away, and he&#x27;s gonna be feeling awkward enough already.<p>So I think you can be fine, but you gotta actually know what you&#x27;re doing, and you have to get&#x2F;be modern.

One of my gripes with web development is that it looks like its primary driven by fads.<p>A LOT of companies change the whole stack just to copy the latest gimmick they’ve seen somewhere else.<p>Devs need to be constantly relearning how to do basic things, so you either chose some tech and hope it gets popular, or you get to know a lot of frameworks only superficially, which leaves a lot of the internet broken.

Tech interviews have been horribly broken for at least a decade now. They&#x27;ve been mostly broken for a couple decades. Fortunately I haven&#x27;t had to talk to a recruiter for a job since 1998 and hopefully I never will again. Maybe call up some people you worked with before and see if their company is hiring. They most likely are.<p>Anyway, C# is still very relevant, but it depends on location. In my city, it&#x27;s huge, in others, not so much. I tend to stick to back end work rather than front end work. Front end&#x27;s flavor of the day changes way too often, and I find it to be tedious work. Back end is much less reliant on external libraries and therefore doesn&#x27;t change as rapidly, and to me is much closer to actual programming.<p>So in summary, talk to your prior colleagues, stick to back end work (if that&#x27;s your bag). Keep on truckin&#x27;

Good wordpress developers are in great demand. If you find the right clients, you can earn above average the market standards.<p>About your skills, There are many new trends in tech in last decade. Since you have worked withe web, I will suggest you to start with HTML5, CSS3 and Javascript&#x27;s new features which you may already be knowing.<p>Start learning server side js. Node.js is bit confusing if you are old folks but see some tutorials and follow them, start with light framework like Express and make small app. The benefit of node.js is you can share many modules at both server and client sides if needed[though beware of it].<p>Alternatively if you want to stick to PHP, the easiest will be to start with codeigniter and when you feel likes getting grip move to Laravel. Laravel is in great demand. Learn to use it with docker.

It is a mix of all of it. It has changed a bit since there are more of a talent pool than ever before. Also, positions that used to have multiple engineers are now replaced by one, both my tech improvements and &quot;budgeting&quot;. With that change you are required to know more than ever before, and a way they weed you out is having insanely hard interviews that a lot of times don&#x27;t reflect the work you do(that is changing a bit as some companies are doing project based interviews). I recommend looking at &quot;Cracking the coding interview&quot;&#x2F;leet code to help you pass those interviews. This is reflective of where you are applying to, some smaller places as much emphasis, but it all depends on who your interviewer and how they choose to weed out employees.

Skew your resume toward you as a &quot;solution builder&quot; or &quot;online business builder&quot; vs. wordpress or PHP developer of which are dime a dozen.<p>Building successful solutions and helping to evolve a business is inherently more valuable skill to the guy who signs a checks.<p>If he is smart enough he is less care about technology you know at this given moment but more about you passion, inspiration and ability to help the business grow and learn new fad along the way if needed.<p>If you&#x27;re facing overzealous interviewers nitpicking your coding skills or short cycled in forcing you to solve stupid puzzles in record short time - it is likely there is a disconnect within this organization on what is really important and you&#x27;ll be wasting your valuable time agreeing to work there.

this meme[1] translates perfectly the current state of tech interviews<p>[1]<a href="https:&#x2F;&#x2F;starecat.com&#x2F;the-technical-interview-vs-the-actual-job-comparison-dinosaurs&#x2F;" rel="nofollow">https:&#x2F;&#x2F;starecat.com&#x2F;the-technical-interview-vs-the-actual-j...</a>

The landscape has shifted a little, but you can still find plenty of C# and WordPress openings. In my opinion, the biggest difference is the expectation to have experience in React, Angular, or Vue. Frontend complexity has grown a lot in the past seven years.

&quot;WordPress dev&quot;<p>Your skills are very relevant at least with WP. Are you not looking for WP jobs ?

The way it was put to me is the modern tech interview is to the job as the SAT is to college. They don’t require the same skills, and performance in one isn’t terribly predictive of success in the other.<p>Do not doubt yourself based on your interview performance. If it’s something you care about and you have the time, do your test prep properly: big O, tree traversals, etc. etc. etc.<p>I’ll add that as a primarily functional programmer who’s applied for multi-paradigm jobs, I’d say a lot of the answers I’ve been expected to give were quite absurd.

Main goal of most good interviewers is simple — hire smart developer.<p>Algorithms is one way of achieving this goal (another question if it’s good way).<p>Since CSS knowledge (and honestly wordpress) is not a big deal (you don’t have to be smart to learn them) — make sense that interviewers asking you a lot of stuff.

Are you willing to continually learn?<p>Can you complete projects of at a minimum, small size?<p>Then, yes.