I had been kind of full stackish in several places because we were primarily small companies, but in a couple, frontend was a dedicated job so I did not work on frontend in those places.
Having said that, the majority of my career has been in the .NET ecosystem. In 2016, I dropped .NET completely and just went all in on the JS ecosystem. (I tweeted the wrong year in the Tweet below π)
@_esausilva@seanfitzg@housecor Most of my career has been in the .NET ecosystem doing full-stack during parts of my career. I dropped it completely in 2015 and just went full JS/Node/TypeScript/React. Best decision of my life and I didn't need to take a paycut.
16:29 PM - 04 Mar 2018
0
1
All this to say, even though I was already familiar with the frontend space, it still was a move that I made which I doubted myself and was very nervous to do.
I made the switch because I was given an amazing opportunity and I just went for it. It was the best decision Iβve made in my career.
Since then, Iβve also dabbled in a bit of Ruby on Rails as thatβs our backend where I currently work.
That's awesome! I feel like it's easy to get caught up in thinking that you can't switch without a large amount of experience to back it up. I've noticed that companies I've inquired with are still pretty receptive despite my primary stack being dissimilar to theirs. I guess the worst that comes from taking a chance is you learn something π
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I had been kind of full stackish in several places because we were primarily small companies, but in a couple, frontend was a dedicated job so I did not work on frontend in those places.
Having said that, the majority of my career has been in the .NET ecosystem. In 2016, I dropped .NET completely and just went all in on the JS ecosystem. (I tweeted the wrong year in the Tweet below π)
All this to say, even though I was already familiar with the frontend space, it still was a move that I made which I doubted myself and was very nervous to do.
I made the switch because I was given an amazing opportunity and I just went for it. It was the best decision Iβve made in my career.
Since then, Iβve also dabbled in a bit of Ruby on Rails as thatβs our backend where I currently work.
I wrote about it here.
Take chances and standout
Nick Taylor (he/him) γ» Jan 7 γ» 5 min read
That's awesome! I feel like it's easy to get caught up in thinking that you can't switch without a large amount of experience to back it up. I've noticed that companies I've inquired with are still pretty receptive despite my primary stack being dissimilar to theirs. I guess the worst that comes from taking a chance is you learn something π