NomadStyle

Day 91 𝐇𝐨𝐰 𝐭𝐨 𝐠𝐞𝐭 𝐫𝐞𝐚𝐝𝐲 𝐟𝐨𝐫 𝐚 𝐣𝐨𝐛 𝐢𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰

Hello! Today I had a very interesting lesson with my coach. He told me about the interview process, what questions they ask, what type of technical assignments they can give, and how to prepare in general.
Usually, communication with a technician begins with checking your theoretical knowledge. Typically asked questions such as "What is UIStackView?" or "What is the lazy property?".

In the practical part, you will be asked to solve simple (or complex👽) problems in real-time. A technician needs to understand your logical thinking and project skills.
𝐇𝐨𝐰 𝐭𝐨 𝐩𝐫𝐞𝐩𝐚𝐫𝐞 𝐟𝐨𝐫 𝐭𝐡𝐞 𝐩𝐫𝐚𝐜𝐭𝐢𝐜𝐚𝐥 𝐩𝐚𝐫𝐭 𝐚𝐧𝐝 𝐧𝐨𝐭 𝐟𝐚𝐢𝐥 𝐚𝐭 𝐭𝐡𝐞 𝐢𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰? There are platforms to help you improve your skills, expand your knowledge, and prepare for technical interviews.

Here are some of them:

𝐏𝐫𝐨𝐣𝐞𝐜𝐭 𝐄𝐮𝐥𝐞𝐫 is a platform dedicated to a series of computational problems intended to be solved with computer programs
𝐂𝐨𝐝𝐢𝐥𝐢𝐭𝐲 is the technical recruitment platform for teams to test the coding skills of developers and make evidence-based hiring decisions.
𝐋𝐞𝐞𝐭𝐜𝐨𝐝𝐞 is an excellent tool for honing your programming skills in preparation for your big tech interviews
𝐀𝐥𝐠𝐨𝐄𝐱𝐩𝐞𝐫𝐭 is an interview preparation platform for software engineers. It's specifically geared towards those who want to work at a FAANG-level.

(FAANG is an acronym referring to the stocks of the five most popular and best-performing American technology companies: Facebook, Amazon, Apple, Netflix, and Google)

Good luck! 🍀

Day 88-90

Hello! I am now intensively preparing for a working interview, indulging in all the materials that I have already studied.

And I want to tell you that I have already completed a program from Apple called "Develop in Swift, Fundamentals" (freely available). The program is designed for approximately 180 hours. This includes from the very-very base of the Swift language to the development of an application prototype, but to be honest, the material seemed to me very succinct. It was easy enough for me to study this material only because I had a coach who has been working in this field for over 10 years. I could ask all the questions I was interested in during our sessions (this helped me a lot to understand the principle of work in general).

It’s hard to believe that my training is coming to an end.😞

What materials did you use to start learning to program?

Day 80-83 News. Protocols

Hey! While I am emailing my resume, I decided to refresh my knowledge and repeat everything that I have already learned (to not fail at the interview☠️).

Today I continued to study the protocols.

The Swift standard library defines many protocols that are used when building apps. I learned about 4 basic protocols (actually 3 because I already know about Codable😋).

𝐂𝐮𝐬𝐭𝐨𝐦𝐒𝐭𝐫𝐢𝐧𝐠𝐂𝐨𝐧𝐯𝐞𝐫𝐭𝐢𝐛𝐥𝐞 allows us to control how our custom objects are printed to the console ( this looks really nice👌)

𝐄𝐪𝐮𝐚𝐭𝐚𝐛𝐥𝐞 allows us to define how instances of the same type are equal to each other.

𝐂𝐨𝐦𝐩𝐚𝐫𝐚𝐛𝐥𝐞 allows us to define how instances of the same type are sorted.

𝐂𝐨𝐝𝐚𝐛𝐥𝐞 allows us to encode our type's properties as key/value pairs that can then be saved between app launches.

Keep in mind that when we adopt a protocol in Swift, we promise to implement all the methods required by that protocol. The compiler will check that everything is in order and won't build the program if something is missing🙅‍♀️.

Day 78-79.

Hey there! I am looking for an internship to start my development career👾

These days I was creating a developer's resume and researching the job market.
To be honest, creating a resume is not as easy as I had expected!
It was difficult for me to articulate my knowledge and achievements🤯. And I got a little panic when I compared my resume and job requirements for the Junior Developer position.😅

🙏𝐂𝐨𝐮𝐥𝐝 𝐲𝐨𝐮 𝐭𝐞𝐥𝐥 𝐦𝐞 𝐚𝐛𝐨𝐮𝐭 𝐲𝐨𝐮𝐫 𝐞𝐱𝐩𝐞𝐫𝐢𝐞𝐧𝐜𝐞? 𝐖𝐡𝐚𝐭 𝐬𝐡𝐨𝐮𝐥𝐝 𝐚 𝐧𝐞𝐰𝐛𝐢𝐞 𝐜𝐨𝐧𝐬𝐢𝐝𝐞𝐫 𝐰𝐡𝐞𝐧 𝐜𝐫𝐞𝐚𝐭𝐢𝐧𝐠 𝐚 𝐫𝐞𝐬𝐮𝐦𝐞? 𝐇𝐨𝐰 𝐝𝐢𝐝 𝐲𝐨𝐮𝐫 𝐟𝐢𝐫𝐬𝐭 𝐢𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰𝐬 𝐠𝐨?

🥰

Day 77. Sad day

Hi there! My Monday started with bad news🧟‍♀️
As I told you before, I use a service that allows me to work on a Mac in a cloud since my computer doesn't support the latest versions of the Xcode. And you know what? I forgot 🤦‍♀️ to pay the bill and the administrators disabled my account with all my works that were stored there.

Fortunately, the losses are small - just a few of the last laboratory work that I did not commit to the GitHub. All big projects are safe and sound 🥳

Use GitHub and don't forget to commit the latest changes👌

And I'll go and set up reminders of important things for the year ahead😁.

Day 73. 𝐕𝐢𝐞𝐰 𝐂𝐨𝐧𝐭𝐫𝐨𝐥𝐥𝐞𝐫 𝐋𝐢𝐟𝐞 𝐂𝐲𝐜𝐥𝐞

Hi there! 🥰

View controller life cycle is a sequence of steps that begins with its creation. The creation of the View Controller comes with a storyboard or from the code. The loop begins from the moment the application starts and the first View Controller appears on the screen. The second step is initialization. We need a View Controller to set all objects. Initialization methods help to prepare it for appearance and probably disappearance on the screen.

View Controller initialization methods:

▪️𝐕𝐢𝐞𝐰𝐃𝐢𝐝𝐋𝐨𝐚𝐝

After you’ve instantiated a view controller, whether from a storyboard or programmatically, the view controller will load the view into memory. This process creates the views that the controller will manage. The method is called only once during the VC life cycle.

▪️𝐕𝐢𝐞𝐰𝐖𝐢𝐥𝐥𝐀𝐩𝐩𝐞𝐚𝐫

The method updates the View every time we enter the View Controller. It lets you know what changed in the View when we were outside of it.

▪️𝐕𝐢𝐞𝐰𝐃𝐢𝐝𝐀𝐩𝐩𝐞𝐚𝐫

The method is called at the moment when the View has already appeared on the screen. We use it for animation, starting a timer, monitoring GPS, etc.

▪️𝐕𝐢𝐞𝐰𝐖𝐢𝐥𝐥𝐃𝐢𝐬𝐚𝐩𝐩𝐞𝐚𝐫

The method is called before VC leaves the screen. Used to undo what was done in the ViewDidAppear. For example, stop timer ex*****on, interrupt animation, stop GPS observation.

▪️𝐕𝐢𝐞𝐰𝐃𝐢𝐝𝐃𝐢𝐬𝐚𝐩𝐩𝐞𝐚𝐫

The method is called after VC has completely exited the screen. It is rarely used.

💁‍♀️

Wish you all a great weekend!💕