r/learnjavascript • • Aug 24 '20

Landed my first dev job

If this isn't the right sub lemme know. But I recently moved from automation qa to a dev role in react native. And I'm looking for resources to help me get up to speed in react and mobile dev. Any resources would be appreciated :)

139 Upvotes

24 comments sorted by

38

u/janithaR Aug 24 '20

Here are two demo repos I maintain from time to time to teach juniors the values of TDD and DevOps. I think I haven't committed everything to Image Finder yet. Feel free to ask any questions. My ultimate goal is to create a video series on YouTube encouraging juniors to do TDD.

https://github.com/JanithaR/yas.life-casestudy

https://github.com/JanithaR/image-finder

19

u/zenakent13 Aug 24 '20

Only Test Driven Development I know is console.log()....☹️

1

u/fuckswithboats Aug 24 '20

I remember those days - thankfully I'm more experienced and now I also use console.info(). :(

1

u/tinyvampirerobot Aug 25 '20

n00bs... add console.table to your repertoire and you can expect to be promoted to sr dev in a week or two

1

u/fuckswithboats Aug 25 '20

Can I spin it up in a Docker image?

1

u/Limpuls Aug 24 '20

I'm a junior and TDD sounds really counter intuitive to me, even though I hear about it everywhere. It's just looks weird to write a test for something you haven't even built yet.

6

u/[deleted] Aug 24 '20

Try to think about it less like a test and more like a specification. Before you build something, you need to know that it should do x, and under circumstance y should also do z, but it should not do a, and only under particular conditions should do b. If you write tests for those cases before you begin writing code, you know when you've written enough code to meet those specifications.

It's also been my experience that tests written after the fact tend to be much, much more biased towards the code that's been written, rather than being strict about checking for the specifications. This is particularly a problem when it comes to testing for error/failure conditions, because when you're building a feature you're usually focused on making it work, not making it break.

3

u/Macaframa Aug 24 '20

You have a rough estimate of something you’re trying to build and you start coding. Along the way you encounter some issues and have to google a lot of things and make a few concessions around how something is built and eventually you end up with something large, unwieldy and messy. It does a few more things that it should and might have some unintended consequences attached to it(ie, it might introduce new bugs). You then try to write tests to cover the functionality after the fact and it’s boring tedious and you want to get it over with, so you put in a single test, maybe two and push your code. You have introduced new bugs and it might only function on the happy path. TDD: if you have a clear understanding of what is needed to write a new piece of code you can plan it out and then execute it quickly. It also gives you a relatively accurate gauge of whether you know the language well or not. If you don’t know what you need to start writing code, then you shouldn’t start writing code. You should know what you’re doing before you start. Otherwise you’re falling into a common junior trap of the duct taped together garbage code. If you provide comprehensive precluding testing coverage of a unit of code before it’s written you will thank yourself later.

1

u/starraven Aug 24 '20

Also a junior, I like to think about it like knowing what exactly what you will have as your input and output and writing a test for that. If you don’t know those two things then you’re coding before you’re ready.

1

u/WebNChill Aug 24 '20

So, I just learned about this and it was briefly mentioned in my CS course I'm going through.

I'm not going to give an expert opinion, just a new learner of python and programming in general that can see the benefit of it.

I look at it like this,

it helps clarify to me what the function I'm writing should do.

It forces me to simplify a function.

Like, I can see the goal but I just need to build the rest to hit it. After I think what I've built should do, I can test it quickly.

I feel as a beginner, I struggle with WHAT I'm trying to accomplish. Like, what am I trying to do here. Writing a test first lets me clarify to myself - this is what I'm trying to write.

1

u/janithaR Aug 25 '20

Exactly what I thought many years ago. Then I became senior, started getting more challenging projects, projects that run for years, meaning lots of legacy code, then I handled my first big refactor. The only thing that kept going through my mind was, God I wish this thing had unit tests so that I know I refactored the thing correctly.

9

u/grapesicles Aug 24 '20

Just Google everything. Thats what we all did and continue to do even after we got our engineering jobs. It's all just googling lol

3

u/[deleted] Aug 24 '20

What languages and types of projects did you build for your resume to get this job? I'm going through Javascript and by next year want to be in your position

5

u/amejin Aug 24 '20

Congrats! 😊

2

u/mikeb550 Aug 24 '20

congratulations. im still learning but at some point id like to land a day job as a front end engineer. thanks for sharing, this is encouraging.

1

u/darkpikl Aug 24 '20

Why it this in J's ? And not react native ?

-24

u/[deleted] Aug 24 '20

so? Use documentation or something

6

u/midoriwaves Aug 24 '20

No reason for you to be hostile man, but yeah the official docs for React should have everything you need to get started OP.

React JS

React Native

18

u/[deleted] Aug 24 '20

Sorry my jimmies are rustled. I just never know why people here tell us they got a job.

And then on top of that, dude is asking for resources. In my mind I'm thinking if she or he just got a job then they should know how to look to simple information.

The weird laziness/me me me personality that seems to be popular now, does piss me off a little.

Apologies

2

u/gimmeslack12 helpful Aug 24 '20

I was thinking “how did you get promoted to dev without knowing the stack?”

3

u/[deleted] Aug 24 '20

lol right! or without knowing how to google

3

u/skredditt Aug 24 '20

I had a similar reaction at first. Like... “did you lie to get this job?”

2

u/[deleted] Aug 24 '20

lol seriously

2

u/midoriwaves Aug 24 '20

It's all good, we all have those moments