Views : 1,279
Genre: Science & Technology
Date of upload: May 16, 2022 ^^
Rating : 5 (0/72 LTDR)
100.00% of the users lieked the video!!
0.00% of the users dislieked the video!!
User score: 100.00- Overwhelmingly Positive
RYD date created : 2024-01-25T22:03:31.261106Z
See in json
Top Comments of this video!! :3
I could not agree more. Unfortunately, I did not take this advice and now I'm kind of at an awkward spot. I got my first iOS dev job, but there are all kinds of problems. Ex. I'm literally the only iOS developer on the team...and I'm still very much a junior. The code base was written by a bunch of co-op student because the employer was very cheap and could not afford to pay for talent. I figured, some experience is better than no experience, and I still believe that to be true, but it could not have been a more awkward fit for me personally, coming in as a junior to my first job, with no mentor, no expert, and no true leader. So yeah...hear, hear!
2 |
I do not agree with this Sean. Take the job! It is very hard to get an offer for your first job, and the last thing you want to do is say no to a position, and then not get another offer for months! Take that job, do your best, and try to keep it for at least one year. Your resume will be much better received after that first position is on it: You are no longer a raw developer. Even keeping it for 6 months will be better then no job on your resume at all. No matter how bad that job is (unless it's unsafe, if so then quit immeadiately) it will be better then not being employed, and first job offers are hard to come by!
The other piece of that is that you really don't know how that job is going to work out. I got a position at two different companies, Chase Bank, and Macy's. I thought working at Chase would be fantastic. It was a terrible fit for me. I thought Macy's was yesterday's technology and would not be a great job, and it was fantastic - the people were great and we were working on exciting stuff!
2 |
@rids437
2 years ago
so true
1 |