Live data from Hacker News

Ask HN: Moving from tiny websites to serious tech skills?

news.ycombinator.com

51–60 of 88 posts

Re: Ask HN: Moving from tiny websites to serious tech skills?

#51
post #42
post #22

I don’t want to discourage you, but why do you want to learn these “large-scale” technologies? Tools are tools. They solve some problem. Many of the large-scale companies have problems you as a single frontend developer might not. If we better understand what is your motivation maybe we can better advise you which techniques are worth your time. Are you interested because you would want to join a big company? Then it…

Sometimes discouraging people is the best way to encourage them finding a better path. Over my career the golden rule i’ve learned is: Learn the technology stack when you need it to solve a specific problem. Everything else is likely premature optimisation. If you want to grow as a developer you have to join a team. There is no shortcut to this.

This is very good advice and applies to many more things than just technology.

Re: Ask HN: Moving from tiny websites to serious tech skills?

#52

Earlier quoted context omitted.

how does one simply “get hired” while being mid career with no professional sw experience? asking for a friend.

Practice algorithms and read about software design in your spare time. Apply to tons of companies, be prepared to be rejected from almost all of them, and to be asked questions that you have no intelligent answer to. Remember what they asked you, learn the problems you got wrong, and repeat. It may be brutal and embarrassing at times but if you keep at it you will eventually get a job. The only thing I can say about…

the leetcode/algo question stuff is mentioned here on HN alot but I've never gotten to the point where a test was actually offered to me. will start practicing though and hopefully an opportunity pops up.

Re: Ask HN: Moving from tiny websites to serious tech skills?

#53
I am a self-taught software engineer back in 2016. After launching my first SaaS, I realise for me to grow, I need to learn from people way better than me. I manage to find my first software engineering job in 2017 and never look back.

I believe the best way to learn is from people better than you. The problem with small projects is that it never make it to the point where certain skills/practices become important or even critical.

In this spirit, my recommendation is in this order: 1. Get a job. Learn how to work in a team. 2. If for some reasons, this is not possible, watch conference talks especially on those problems faced by big companies, and what do they do to solve it. Learn about this problem, and figure out other ways.

Re: Ask HN: Moving from tiny websites to serious tech skills?

#54
Have you thought about learning some low code tools that could get you into a position of deploying a web app quicker, albeit placing some limitations on what you can achieve? The limitations you encounter may be acceptable to you considering your goals and this way you’ll have something to show for your effort in much less time.

Re: Ask HN: Moving from tiny websites to serious tech skills?

#55
Find an interesting open source project with active and friendly maintainers (this might take a bit of looking). Figure out how to check out and build the code, then choose an open bug and fix it (or find a small open feature request and implement it). This will require learning how to read code in a bigger codebase and make targeted changes, which is basically the first thing you need to be able to do as a software professional.

Re: Ask HN: Moving from tiny websites to serious tech skills?

#56
post #16

Earlier quoted context omitted.

Look for a company where software is not their main focus. Get hired there by showing them some projects on GitHub. Don't have projects on GitHub? You can make those be there right now for free. You will also need to interview there. Your username indicates that you suck at interviewing. I hate to break it to you, but interviewing is a skill that can be learned. With. Practice. You can either interview at places or t…

i don't have any public facing repos, so i'll clean some up and try to emphasize that a bit more. in terms of interviewing, no opportunities so no experience. in the past ive had to apply to roughly 80 jobs to get one interview. recruiters on linkedin are a little better at ~30 conversations per interview but its plain exhausting, takes a ton of time, they demand replies instantly or ghost, but really its overwhelmin…

Having something that stands out on the resume will go a long way for you. A nice looking GitHub profile with some pinned repos with activity and a nice readme is what I would recommend.

You can also find an existing project and contribute to it. What's your GitHub username? I can follow you

Re: Ask HN: Moving from tiny websites to serious tech skills?

#58

You won't get there if you stay solo, so get hired, join a team and learn as much as you can from your peers. Large-scale is team-scale.

This is what I would advise as well.

Look at marketing agencies especially, where they typically do more than dev, but need some dev skills in house. Focus on Wordpress for smaller projects and use Laravel as a framework for larger stuff. You'd be surprised how many businesses just want a Wordpress site as part of a larger marketing initiative, so be proficient there and you can make money. And the Laravel ecosystem has everything you need for large scale web projects, with Laracasts being a great resource to learn.

Re: Ask HN: Moving from tiny websites to serious tech skills?

#59
I started almost exactly where you were about 12 years ago. Came from a graphic design background, knew HTML and CSS really well, was decent at client side JS. I knew some PHP from hacking on Wordpress sites, but struggled to grok the rest of the web.

The best thing I did was grab a Rails book and study it, building the sample project all the way through. Then I came up with a web app I wanted for myself and built that using what I had learned. This took some time, but taught me so much. First, it forced me to learn another ecosystem, which made me much more aware of what was “common” or “universal” among web applications versus what was environment-specific. It also made me learn a new language, which similarly gave me a much better understanding of how computer programs work (seeing the same basic things implemented differently helped me understand the fundamental concepts that every language is abstracting over).

I would definitely still recommend this approach today, specifically because Rails is such a well-documented full-stack framework, it’s really easy to learn. Start here: https://www.railstutorial.org/

Another advantage is Rails is the tech underlying many of the web giants (GitHub, Shopify, AirBNB, etc), and the Ruby ecosystem inspired many of the other cool new technologies out there today. Even though it’s not the “hot new thing” anymore it’s extremely marketable. React devs are a dime a dozen, but people with Rails experience are in high demand and much harder to find.

The last thing is you just need to get a job at a place with other good engineers who can mentor you. Ultimately everything else is just getting your skills up enough to get in the door, once you clear that hurdle you’ll be able to learn as you go.

Best of luck on your journey, it’s hard work but very, very rewarding! Happy to answer questions if you have any :)

Post reply on HN