DEV Community

loading...
Cover image for Things I wish I knew before entering the tech space ๐ŸŒŒ part 2 of 3

Things I wish I knew before entering the tech space ๐ŸŒŒ part 2 of 3

technoglot profile image Amelia Vieira Rosado ใƒปUpdated on ใƒป4 min read

Photo by Thought Catalog on Unsplash

Hey fellow dev! ๐Ÿ‘‹๐Ÿป How are you putting up in these uncertain times?

First and foremost, welcome to part 2 of the three part series titled: Things I wish I knew! If you are new here, go take a quick look at part 1. Otherwise, sit back and enjoy!

Quick recap

In part 1 we silently judged my younger self and the things she did not know back then. Just kidding. That'd be evil. ๐Ÿ˜ˆ Instead we went over topics such as:

  • the importance of version control and "vanilla" skills,
  • having proper hardware to work with,
  • the wide variety of tools at your disposal and
  • the struggle of learning tech skills.

Today we will look at a few more things I wish I knew before getting started in tech.

The importance of a portfolio ๐Ÿ’ผ

Well, I'm not really one to talk, since I don't have a portfolio in place at the time of writing, ๐Ÿ˜• but that does not mean portfolios are not important. As a matter of fact, it is the best way to showcase your skills. Portfolios are also incredibly useful when in search of a job in this field. It is the embodiment of letting your work speak for you.

My advise to beginners: start early. Don't doubt yourself so much. Build something, see it through the end and show your work. It pays off, I promise! ๐Ÿ˜‰

Work experience is key ๐Ÿ”‘

Now, this one is a no-brainer. I actually already knew this before getting in the tech space. However, it is still worth mentioning. Try to get a hold of an internship as soon as possible. If you can get a summer internship, go for it. All the internships you do, will not only help you gain some experience while studying, but it will also help you build your network.

Off you go, make a name for yourself! ๐Ÿคฉ

Skills > Certificates

Here's a personal favorite. You have NO idea how many people I have seen on LinkedIn sharing that they just got a badge or certificate for completing I-don't-know-what-course. While that is a cool feat (also, I am by no means invalidating their efforts), how relevant is that? Most people can study a certain material, pass an exam and get a shiny certificate. BOOM! You are an expert now (certainly not)!

Here's what I suggest. Take it or leave it.

  • Only get those certifications that are in line with what you want to accomplish. Passionate about web dev? Don't go and get that CompTIA+ certification. It can wait.
  • Put skills before certifications. Build something to showcase what you learned. Or write blog posts sharing what you learned. The certificate is a bonus. But please BUILD! ๐Ÿ‘ท๐Ÿปโ€โ™€๏ธ๐Ÿ‘ท๐Ÿปโ€โ™‚๏ธ (Don't be like me: portfolio-less. Yes, that's not a word).
  • Seek ways to apply your knowledge. This refers to the first point mentioned earlier: build a portfolio. Work in a project-based manner and you will see how your skills will grow stronger. (Beware of tutorial hell! ๐Ÿ˜ฑ)

And remember...don't be a certificate H03... (Sorry, I just had to.) ๐Ÿค

Tech goes beyond Software Engineering

When I enrolled at the uni to study Information and Communication Technology (ICT), I was fixated on becoming a Software Engineer. I knew damn well that there were more things one could become after studying anything related to tech. But trust me, when you first get started, you probably have no clue what a DevOps Engineer is. Or a Data Wrangler. Or a Data Plumber...(you know, the ones that fix data leaks? Just kidding, that is not a thing. Yet ๐Ÿ˜…).

Here's a little assignment for ya.

  • Check out the various job postings on your platform of choice. Don't know where to start? Check good ol' LinkedIn out for starters. Stack Overflow has job postings too, also a great place to start.
  • Browse the various jobs and read their descriptions.
  • Google search whatever sounds weird to you.
  • If a job title appeals to you, you may want to look at the skills necessary to go that route. Else, you gained good insights into the various jobs in the field.

New badge unlocked! General knowledge expanded! Great, isn't it? ๐Ÿ˜Ž

Best way to learn tech is by building ๐Ÿ”ง

I said it multiple times in this post. BUILD something. The best way to learn how to code is by DOING. Nope, your uni assignments won't be enough. That's basic. Nope, your code-along projects from tutorial hell won't cut it either. ๐Ÿ™…๐Ÿปโ€โ™€๏ธ๐Ÿ™…๐Ÿปโ€โ™‚๏ธ

Be original, build something of your own. And fear not, Google is out there. So is Stack Overflow and a loving and supporting community of devs. ๐Ÿค— You. Are. In. Good. Company. Just BUILD it!

Just Do It

The wrap-up

Hurray, you made it till the end of this one! ๐Ÿฅณ Thank you for taking the time to read this post. I hope you enjoyed it. If you did (or didn't), let me know in the comments below. Anything you'd add to this list? ๐Ÿค” There's still one more part to go, so keep your eyes peeled for that one! ๐Ÿ‘€

To infinity and code on! ๐Ÿ‘ฉ๐Ÿปโ€๐Ÿ’ป๐Ÿ‘จ๐Ÿปโ€๐Ÿ’ป See you soon!




Still here? Catch me on Twitter or find me elsewhere! If you like my blogs and are feeling generous, kindly consider to ๐Ÿ‘‡๐Ÿป




technoglot footer banner

Discussion (4)

pic
Editor guide
Collapse
miguelmj profile image
MiguelMJ • Edited

Best way to learn tech is by building

For me, this has been the most important thing. You are undergraduate? Learning theory is very important. You are self taught? The internet is full of high quality tutorials. But... what have you built? That answer is what helps me really make me an idea of you as a developer.

In my case, I learnt lots of things in university, but I never internalized them until I used them in real projects. You don't know a technology until you have used it and spent hours catching errors and bugs. Want to learn about version control? Start to use git for every project. Want to learn about making documentation? Make some wikis for your GitHub repos, try out doxygen. You name it.

Collapse
technoglot profile image
Amelia Vieira Rosado Author

Thanks for the articulate comment, Miguel! Learning by doing is definitely the approach, no matter where one comes from (be it uni or otherwise). It is something I personally struggle with given that I am more of a thinker than a doer. Hence why I brought it up here.

Collapse
egilhuber profile image
erica (she/her)

HUGE agree on the Skills > Certificates! I'm sure the courses are challenging, but those certificates aren't necessarily a sign of mastery. Sharing a project or a bit of insight on what one got out of the course (besides "I got so much out of this course!") would be much more telling.

Collapse
technoglot profile image
Amelia Vieira Rosado Author

certificates aren't necessarily a sign of mastery

Absolutely agree!

I just thought I'd mention that point because I'm seeing too many people chasing the certificates (and at the end they never use that knowledge again).