#DeveloperTips #TechAdvice #CareerGrowth
Hey fellow developers! 👋 As a new grad who recently landed a job after a few months of searching, I realized there are some things I wish I knew sooner in my tech journey. So, here’s my burning question to all experienced devs out there:
🤔 Developer, what are the things that you wish you knew sooner?
From my own experiences, I discovered the importance of tools like WSL (Windows Subsystem for Linux) that can really make a difference in my workflow. However, there are still many areas that I feel unsure about in my current role involving .Net, React, and TypeScript.
Possible solutions that I’m considering to address this knowledge gap are:
– Taking online courses or tutorials to brush up on unfamiliar technologies
– Seeking mentorship or guidance from more experienced developers
– Engaging in side projects to gain practical experience in new areas
Do you have any other valuable insights or advice to share? Let’s start a discussion and help each other grow! 💡 #KnowledgeSharing #TechCommunity
A very small thing that increases the quality of the code you write.
The return early pattern.
I see developers with over 10 years of experience that just don’t do this and their code is hard to read when they have all of their code inside a function with an if.
I wish I knew the importance of what I learned. I wish in college that when they taught us aspects of Computer Science they would tell us “this can apply to a software developer job when you’re doing XXXX”
It kinda helps motivate me to retain info rather than just cramming for the next test and forgetting about it later.
They never teach you in college how to learn about how to learn. You kinda got to pick up your things and go
Strong debugging skills, how/where read the call stack, and also (this one is really dumb) learning to empty the browser cache. I remember being so baffled when an entire page of a project I was working on I got rid of kept showing up when I built the project and visited the URL.
You will write 3x as much code as your peers and nobody will care so why bother?
Dependency Injection. Also, probably knowing more Python while in college.
People skills are just as valuable as technical skills – the hardest part of a project is often getting people aligned of what needs to be done and making sure things stay unblocked
I wish I knew that after 9 years of hard work I would have to end this career because there’s no job opportunities.
other than what was mentioned.
the value of reading a good book and fixing weird problems. I spent about 3 years stagnant because i was solving the same problems over and over and over again the same way.
What I would definitely tell people is how to write clean code. So many of my classmates, and even some professors don’t know how to write clean code. Thankful someone I knew in the industry taught me how to do it in my freshman year, and that has helped me a lot. Clean code means it’s easy to read, good explanations in the form of comments, and apt variable names. So many teachers, books like CLES don’t do this properly, I hate the code in CLRS, since the variable names are awful, just letters.
WSL is not so much just a Linux terminal, but a hyper-v virtualization that boots an image. Similar to other VMs you’re probably familiar with.
For me, I wish I’d had learned about Docker and K8s. I heard the terms thrown around when I was in school, I didn’t realize just how utilized they are in the real world. Took me a bit to palate the idea of containerization.
I bet the majority of the folks who were taught in Linux would have no clue how to use Powershell, so it balances out.
The job is 1000 times easier than the interview.
How to write unit tests and networking
Invoke build/makefiles are great for various automation tasks