Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@Lensflare the best one
@SidTheITGuy 100% agree with two. Do not agree with seven. Newbie should go to office -
@retoor Yeah no 7 may have carried some personal preferences. But face it, no one is taking my advice seriously lol.
Also @Lensflare, Coders are these days synonymous with web dev, isn't it? We have forgotten other iterations of software dev, but then again, this is an online community so mostly web devs will hang out here. -
@SidTheITGuy the c devs are ranting on their isolated embedded micro controllers
-
@SidTheITGuy online doesn’t mean web.
For instance, I’m using devRant via a native iOS app.
But it’s true that web dev is often implied by frontend dev. And it triggers me more than it should. And I want to change that. I know it’s hopeless 🥲 -
@electrineer By mistake I tagged you. DevRant doesn't support replying @ multiple people at once.
-
@SidTheITGuy depends on the client/app but you can close the text edit box, then reply to another comment and the @ mention will be added.
IIRC, web doesn’t save the text, but iOS and Android do. -
@Wolle I learned by getting yelled at by my seniors, in the beginning.
-
@SidTheITGuy nah I’m not that smart, it’s just a matter of negotiation and presentation
-
I agree with "basics first!" but at the same time us seniors often harp on it too much. 🥸
We scoff at juniors jumping into react without knowing enough plain Html and Js.
But we forget the process is often iterative. They learn a bit of React cause they get a kick out of it, then go back and learn some fundamentals about some area of plain JS, then back to React etc. ♻️
Don't be like that guy who said you shouldn't learn C because you didn't know Assembly first.
Getting shit done in a specific higher level language or framework can be the catalyst to get you interested in learning basics. -
@jiraTicket I meant more from a view point of learning concepts before jumping to hands-on experiences. OOPS concepts, types of variables, flowcharts about program executions, memory architecture etc.
HTML CSS and JS is an accepted starting point, so I don't see a problem there. -
@SidTheITGuy I'd argue learning memory architecture before trying web dev might not be the best path for some.
I think it's fine to start dabbling with some light web development, and then take some Fundamental Comp Sci classes.
Some educations will be laid out that way, with an easy introduction project to get people hooked - before going back to theory. -
@Lensflare I like web dev and I love front end but it's no good advice for every type of developer, especially not if you like logic and programming in a predictable and testable way, or if you like stability or you're prone to follow every new trend quickly.
Don't get overwhelmed or rather accept that it's normal feel overwhelmed is maybe the most important advice to new web developer apart from learning the basics.
Advice to new coders? I got multiple, unrelated to each other.
1. Start with the FUCKING BASICS !! Invest some time with fundamentals, don't just directly jump on frameworks like React or Angular.
2. You and everyone else are always going to blame your technical skills if you're unable to land a job. But you have to realize that is not always the case. Your attitude and energy towards the interviewer plays a vital role too.
3. You're gonna have to take a hit to your salary expectations starting out. It's just the way this industry works.
4. Think of yourselves as a freelancer working for companies. Those who call themselves Employees get stagnant and dependent on their company pretty fast.
5. Your objective is either to learn or earn. If there is both, amazing job. If there is either it's good enough. If there is none, time to jump ship !!
6. HR is there to protect the company from you not the other way around. Be better at spotting crocodile tears.
7. Try to find a WFH job over a WFO job. If you have an urgency, then either works but keep applying to WFH jobs. It's the best thing.
8. Focus on what you're building instead of what you're building it with. Devs have a tendency to fight over what tech stack they should use instead of focussing on the larger picture.
9. You're gonna get overwhelmed at some point when you're gonna get terms thrown at you like XML, JSON, API, Figma, Git, SOAP, REST. Don't worry though you'll get there.
10. You should know how to google your solutions, like really. This is like 60% of the job.
rant
wk377