[Raidion]

This is such a click bait headline I don't even want to comment. Web Development is boring if you think it's boring. A lot of people don't. If you do think it's boring, there are a lot of industries that need programmers to solve different problems in different ways. If you don't think it's boring, hey that's awesome, you keep on making cool stuff.

If you're bored, it's probably time to start job hunting.

[orblivion]

> If you do think it's boring, there are a lot of industries that need programmers to solve different problems in different ways.

Dumb, overly broad question, but I gotta ask at some point - does anyone have suggestions for figuring out what industries are out there, what they're like, where one may want to try next, how one might break into them? Career navigation isn't my strong suit, as you can probably guess.

[BossingAround]

That's actually a really good question. The thing is, this differs wildly on where you are (or where you want to be, geographically wise). In some cities, you might see entirely different positions just because there are different companies with different needs (e.g. security analysts near big bank headquarters). I too would like a general list of popular programming-related positions though.

[indigochill]

As a general rule of thumb (not that I'm great at this), physical networking might be the most tried and true. Look at whatever local conferences there are, go there, ask people what they do and what challenges they face. Their challenges could be your opportunities if you can find a way to leverage your strengths to solve them in a way that they can afford/use.

At least, that's one idea.

[rat9988]

> If you do think it's boring, there are a lot of industries that need programmers to solve different problems in different ways.

My experience is a bit more mitigated here as a junior dev. No one wants to recruit a software dev who has only webdev experience somewhere else.

Unless I have some serious open source contributions to prove myself I guess, but my point is it's not as straightforward or easy as I felt it is implied.

[Raidion]

Web dev is a fairly broad term. If you only know Angular/CSS/Typescript, you're kinda out of luck unless you start brushing up on your Node chops. If you're writing web APIs, it's a much smaller jump. Embedded systems are a whole different ballgame though.

[rat9988]

I'm full stack, react/redux/typescript front end, and restful api in go/python for the back end. So I presume the jump is not that high in theory, but there are always better fitting candidates.

I'm not saying you are wrong though. Just trying to tell the other new grads that switching might not be straightforward and might require some effort on their part.

[raviojha]

Hiya! Author here. I can't comment on why you felt this was clickbaity. The intention was to give a third-person perspective of the life of an engineer as a webdev at a startup, emphasis on _startup_.

The post is largely targeted at beginners. I think giving this perspective to fresh grads can help them take a decision to atleast clear up the dilemma when they have to choose to work at a startup/corporate during internships or right after college.

The reason I wrote it was because during my four years at college, we had this perception that webdev was boring and nobody used to opt to interview for companies which were into it. And the joke was, "All you do is change the colors every 6 months". I had the chance to intern at a SaaS startup and then worked there for more than 2 years and then figured students back at college needs to know more about this experience.