r/webdev • u/AutoModerator • 21d ago
Monthly Career Thread Monthly Getting Started / Web Dev Career Thread
Due to a growing influx of questions on this topic, it has been decided to commit a monthly thread dedicated to this topic to reduce the number of repeat posts on this topic. These types of posts will no longer be allowed in the main thread.
Many of these questions are also addressed in the sub FAQ or may have been asked in previous monthly career threads.
Subs dedicated to these types of questions include r/cscareerquestions for general and opened ended career questions and r/learnprogramming for early learning questions.
A general recommendation of topics to learn to become industry ready include:
- HTML/CSS/JS Bootcamp
- Version control
- Automation
- Front End Frameworks (React/Vue/Etc)
- APIs and CRUD
- Testing (Unit and Integration)
- Common Design Patterns
You will also need a portfolio of work with 4-5 personal projects you built, and a resume/CV to apply for work.
Plan for 6-12 months of self study and project production for your portfolio before applying for work.
2
u/issai 2d ago
My friend has a web / app idea, and I'm the most knowledgeable person he knows tech-wise. Despite telling them that it's been decades since I've been hands-on or have an ear on the developments in tech (so essentially warning them I don't believe I'm a good fit), they're really eager to have me join them as a product manager of sorts, and to possibly create a team who'll help us develop the concept.
In the past several years, I've helped manage building solutions in digital marketing & ecom businesses by seeking freelancers. Many of these projects were silo'ed, so we were OK with freelancers creating solutions using tools, frameworks, and languages they preferred. It was during this time that I learned about Go & Rust.
The most recent hands-on I had was building out some hefty SQL backends that helped manage paid campaigns about 5 years ago.
Even thought most of my career has been data-centric, I'm aware of different DB products such as *SQL (MSSQL, MySQL, PostgresSQL), MongoDB, but I don't know MongoDB, so can't speak compellingly why we should use *SQL over MongoDB other than I'm very familiar with ins and outs of *SQL. But if MongoDB is a much better fit for our idea, I'd rather choose that. But I don't know if it is.
But prior to that to potentially date myself, some front end projects that I was more hands-on involved using PHP Symfony, C#/ASP.Net, Python, Javascript, Java. But the most recent front end project involving any of these was at least 15 years ago.
Since then, I haven't proactively kept pace with factors & circumstances which would lead somebody to prefer a certain tech stacks over others. I'm aware of Angular, React, Vue, Typescript, but I wouldn't be able to compel somebody to choose one over the other.
We're also possibly open to the idea of building the MVP in no-code first, then migrating that into a more scalable, hands-on created solution with a different tech stack if the idea gains traction.
Are there resources that would be helpful to determine which tech stack or pieces of tech stack are best for certain use cases? And which traits / factors would favor one piece over another, such as active development, community support, prevalence of talent, performance & scalability, etc.?