NomadStyle

Day 92 Last day🥰

Hey there! Today is my last day of training at NomadStyle. My "100 days" of coding ended a little earlier and today I am preparing for a job interview and going into the independent life of a junior developer.🥳😎

Let's sum up:

1. 100 days of coding does not mean that in 100 days you will learn to program. I started my journey in December 2021, and I had about 100 lessons and more than half a year of practice to start understanding programming.

2. Is coaching necessary, or can you handle it yourself? The modern world is full of all sorts of information in the public domain, but I wasn't always able to find answers/solutions to my questions. My coach provided a personalized approach based on my needs👌

3. It won't be easy. But you need to remember that your future is the best motivation.

4. Share your experiences with other students or developers, it's really helpful.

5. Practice-practice-practice!

I continue to study and will wait for a reply from the companies where I sent my resume.

Thank you for being with me along my journey and thank you for your support!

Hug you all!🥰🥰🥰

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 85-87. 𝐌𝐨𝐝𝐞𝐥-𝐯𝐢𝐞𝐰-𝐜𝐨𝐧𝐭𝐫𝐨𝐥𝐥𝐞𝐫

Hi everyone! (Spoiler alert👾: this post will be long, but interesting)

These days I have been learning about one thing that juniors are often asked about in job interviews. 💁‍♀️The Model-View-Controller (MVC) design pattern.

This is a way of organizing your code, which involves highlighting blocks that are responsible for solving different problems. One block is responsible for data, another is responsible for the interface, and the third acts as the messenger between views and model objects.

MVC components:

𝐌𝐨𝐝𝐞𝐥 is responsible for data and also defines the structure of the application. For example, if you are creating a Shopping List application, the model component code will define the list of products.

𝐕𝐢𝐞𝐰 is responsible for user interaction. The view component code defines the appearance of the application and how to use it.

𝐂𝐨𝐧𝐭𝐫𝐨𝐥𝐥𝐞𝐫 is responsible for communication between model and view. The controller component code defines how the application responds to user actions. Basically, it is the brain of an MVC application.

𝐌𝐕𝐂 𝐢𝐬 𝐚 𝐭𝐨𝐨𝐥 𝐭𝐨 𝐡𝐞𝐥𝐩 𝐲𝐨𝐮 𝐰𝐫𝐢𝐭𝐞 𝐜𝐥𝐞𝐚𝐧, 𝐦𝐚𝐢𝐧𝐭𝐚𝐢𝐧𝐚𝐛𝐥𝐞, 𝐚𝐧𝐝 𝐨𝐫𝐠𝐚𝐧𝐢𝐳𝐞𝐝 𝐜𝐨𝐝𝐞.

Using the MVC pattern also allows you to follow the
𝐃𝐑𝐘 (𝐃𝐨𝐧’𝐭 𝐫𝐞𝐩𝐞𝐚𝐭 𝐲𝐨𝐮𝐫𝐬𝐞𝐥𝐟) 𝐩𝐫𝐢𝐧𝐜𝐢𝐩𝐥𝐞. If the code is not duplicated, then it is enough to make corrections in just one place to change the logic. Testing is also simplified, because it is much easier to test one function (okay, maybe more complex one🙆‍♀️) than 20 of the same type.

Day 84. App life cycle

Hey there! I've already learned about different stages of the view controller life cycle. The life cycle of an app is almost the same way.

𝐓𝐡𝐞 𝐝𝐢𝐟𝐟𝐞𝐫𝐞𝐧𝐭 𝐬𝐭𝐚𝐠𝐞𝐬 𝐨𝐟 𝐭𝐡𝐞 𝐚𝐩𝐩 𝐥𝐢𝐟𝐞 𝐜𝐲𝐜𝐥𝐞:

Not running🔴: The app hasn’t been launched or has been terminated.
Inactive🟡: The app is running in the foreground but isn’t receiving touch events.
Active🟢: The app is running in the foreground and receiving events.
Background🟠: The app is executing code but is not visible onscreen. When the user quits an app, the system moves the app to the background state briefly before suspending it.
Suspended🔴: The app is in memory but isn’t executing code.

We need to know the lifecycle of the app to execute code on time. For example, when the app launches, we could trigger a network call to fetch new data. When the app closes, we can save the user's progress.

Now I need to figure out how delegates work.😬

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 74-76. Personality quiz

Hello everyone! Probably each of us at least once played a quiz on Facebook like "What kind of bread are you?" 😄

This days i worked on guided Project by Apple – Personality Quiz in order to consolidate my knowledge of UIKit. In this project I gained more practical knowledge of working with,optional data in Swift, navigation hierarchies and creating simple workflows using tabs and navigation stacks.It was really interesting and informative 👍.

If you had to create a quiz, what would it be?

⠀

Day 74. 𝐇𝐮𝐦𝐚𝐧 𝐈𝐧𝐭𝐞𝐫𝐟𝐚𝐜𝐞 𝐆𝐮𝐢𝐝𝐥𝐢𝐧𝐞𝐬

At least a thousand new applications appear in the App Store every day. However, over 75% of them are downloaded, opened once and never used again. Most often due to poor usability.

People don't want to learn a new mobile interface every time they open an app. They need simple products, the interface should be familiar and all the steps should be logical.

Even such a small element as an icon matters. If the icon image is unknown to the user - this reduces the efficiency of the application. Users should immediately recognize the elements, and not try to understand what they are.

To help developers and designers make better and more user-friendly interfaces, Apple has released iOS Human Interface Guidlines (HIG). This is a set of recommendations and tips to help developers create the best product.

HIG describe visual design rules, including the design and style of icons and much more.

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!💕

Day 71-72.𝐔𝐈. 𝐓𝐚𝐛 𝐁𝐚𝐫 𝐂𝐨𝐧𝐭𝐫𝐨𝐥𝐥𝐞𝐫𝐬

Hi there! 🥰

A tab bar controller allows you to arrange your app according to distinct modes or sections. For example, the Clock app is divided into five modes: World Clock, Alarm, Bedtime, Stopwatch, and Timer.
A tab bar interface features a tab bar view, which runs along the bottom of the app’s screen. Each tab can contain its own independent navigation hierarchy, with the tab bar controller coordinating the navigation between the different view hierarchies.

𝐓𝐡𝐢𝐬 𝐝𝐚𝐲𝐬 𝐢 𝐥𝐞𝐚𝐫𝐧𝐞𝐝:
▫️How to appropriately use a tab bar controller
▫️How to add a tab bar controller
▫️How to add view controllers to the tab bar controller
▫️How to customize tab bar items

It seemed to me that switching between view controllers in this way is super convenient. But I'm not sure that in this case the view controllers can interact with each other🧐

Do you use tab bar controllers? What do you think about it?