<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Nir Peled on Medium]]></title>
        <description><![CDATA[Stories by Nir Peled on Medium]]></description>
        <link>https://medium.com/@nirpeled?source=rss-93821331f585------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*zKMVF23-MZqM5f9tAQrCEQ.jpeg</url>
            <title>Stories by Nir Peled on Medium</title>
            <link>https://medium.com/@nirpeled?source=rss-93821331f585------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 03:56:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nirpeled/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Here’s Why All Tech Workers Should Get A Free Tesla (#12)]]></title>
            <link>https://levelup.gitconnected.com/heres-why-all-tech-workers-should-get-a-free-tesla-12-4a2975967091?source=rss-93821331f585------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a2975967091</guid>
            <category><![CDATA[tesla]]></category>
            <category><![CDATA[hr]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[wellbeing]]></category>
            <category><![CDATA[welfare]]></category>
            <dc:creator><![CDATA[Nir Peled]]></dc:creator>
            <pubDate>Wed, 02 Feb 2022 14:02:29 GMT</pubDate>
            <atom:updated>2022-02-02T14:50:43.138Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fPwzWkBaDpDhY32BCYdHrw.jpeg" /><figcaption>A Tesla owners get-together from last month, can you guess which one is mine? Picture taken by <a href="https://www.facebook.com/cloudview4k/">Shabtai Tal</a>.</figcaption></figure><p>I started a new tradition in my last blog post from last week which is always give you the bottom line first, because I value your time and also because I sometimes use click-bait titles.</p><p><strong>So no, I don’t really think that tech companies should start giving away free Teslas to their employees but I do believe they should highly invest in their welfare and caring in general. Companies can only gain from this, people that get appreciation of their hard work will be more loyal and more productive so it’s a win-win.</strong></p><h3>Meet Webos</h3><p>Just in case you live outside of Israel or living under a rock, the great satire comedy TV show “Eretz Nehederet” (Hebrew for “A Wonderful Country”) has made up a fake tech company called Webos that takes all the good and the bad that the tech scene in Israel represents to a whole new level.</p><p>They make fun of the fancy offices, buzz words and slang-language often used, life-work balance, hiring techniques, and much more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gP6lf81Y2EPHEu6z4mdZWg.png" /><figcaption>Yes, they even have a fake <a href="https://www.webos-hightechs.co.il/">website</a> for their fake company, brilliant!</figcaption></figure><p>Why am I telling you this? Because although Webos is fake, some tech companies actually do some of the things they say. This is not new and started way back with big and rich companies like Google, Facebook or Apple but nowadays, it’s common even in small and less known startups, at least here in Israel.</p><p><strong>Is spoiling employees a bad thing? It depends. Spending ridiculous amounts of money for things like fancy offices, private chefs, spas or giving away Teslas is probably a bit of extreme. With that said, caring for your employees and showing them that they matter and that their hard work is appreciated is priceless, and this can be done with a low budget.</strong></p><h3>A Pizza Can Be Worth More Than You Think</h3><p>A few years back, I went to see a talk by Prof. Dan Arieli. One of the highlights of that night was an HR experiment he performed at Intel. In order to increase productivity and to show appreciation, they picked high-performance employees on a weekly basis and gave them a money bonus, an appreciation text message from their manager or a family pizza voucher, this was done every week for six months.</p><p>The results were nothing but shocking! Although that the money bonus was a nice gesture, people didn’t care so much for it. People were happy to get a text message from their manager that says they did a good job but the most appreciated gesture was the family pizza voucher.</p><p><strong>Ariely explained that the reason the pizza voucher ranked #1 was because not only people were happy to get a free dinner that shows appreciation of their hard work, but this kind of gesture also shows that to their family, giving the employee much pride and that’s priceless.</strong></p><h3>Let’s Get Personal</h3><p>I once worked for a startup named <a href="https://www.linkedin.com/company/wisdo/">Wisdo</a>, we were set to change the world with a life-changing new platform. We had a lot of road blockers ahead, just like many tech companies in that early stage.</p><p>In one of our milestone achievement celebration, the company’s CEO, who has a rich background in writing and journalism, gave each one of us employees, a book about new beginnings and challenges but that was not all, he added a personalized note, for each and one of us. I admit, I never read the book but I kept it, because it was a personal gift.</p><p><strong>True, that’s easier to do when the company has only 8 employees and it’s impossible to scale up when you have 50, 100 or 1000 employees. With that said, it’s really important that you do scale up the company DNA like values, leadership principles and how you celebrate achievements.</strong></p><h3>Small Things Matter Most</h3><p>If I had to choose one company that really goes above and beyond in terms of caring for their employees and supporting them in any situation that might come, my choice will be <a href="https://www.linkedin.com/company/perion/">Perion</a>. For full disclosure, my wife works there.</p><p><strong>Ever since COVID-19 has hit our lives (and also before that), this company amazes me of how well they care for their employees, and yes that involves spoiling with treats from time to time but it’s more than that.</strong></p><p>There’s the “casual” stuff like monthly packages with treats to celebrate holidays or achievements, sending out office furniture since we work from home, an all-included company trip to Morocco, get-better packages when someone is COVID-19 positive or even just in quarantine, an on-the-house day-off for your birthday or for family day, and then there’s much more.</p><p>My 3.5 years-old boy was COVID-19 positive last summer, he had no symptoms what so ever but we still had to remain in quarantine and as most of you know by now, that’s no fun especially with kids. It only took Perion a day or so to send us a huge package with toys, but not just any toys but ones for his age. This means that someone took the extra time to check how old is he and made sure we get the right stuff, incredible!</p><p><strong>Not impressed yet? About this time a year ago, we celebrated Purim here in Israel, which is kinda like the jewish version of Halloween. When Perion understood that it’s not going to be possible to throw the annual party because of COVID, they decided to send this huge and awesome food truck that visited every single one of the employees in Israel, at their homes.</strong></p><p>The trucks were fully loaded with food, toys and a crew that you can only imagine the show it gave to people it visited, definitely awesome and brilliant. I should mention that they wanted everyone to be visited by these trucks at the same day so they had not one but three trucks going all over the country.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n4AKUJlBA_3UZAfIkAfshg.jpeg" /><figcaption>Can’t come to us? No problem, we will come to you :)</figcaption></figure><h3>Show That You Care</h3><p>To wrap things up, if you have any relationship with the HR in your company or you’re in the HR business yourself, and if you could only take one insight out of this post, here’s the one I hope you’ll take; show people that you care for them, that’s all they really need from you. Won’t hurt if you throw in a free Tesla but that’s completely optional.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FhMDz_JtaQ4E%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DhMDz_JtaQ4E&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FhMDz_JtaQ4E%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/15e1c124ff21caccb7e127ee4693e4ef/href">https://medium.com/media/15e1c124ff21caccb7e127ee4693e4ef/href</a></iframe><h3>Want More?</h3><ul><li><a href="https://levelup.gitconnected.com/do-we-still-need-qa-engineers-in-2022-11-7f86b871bab6">Do We Still Need QA Engineers In 2022? (#11)</a></li><li><a href="https://nirpeled.medium.com/landing-your-first-software-engineer-job-can-be-hard-but-not-impossible-10-44cd6ed48cb0">Landing Your First Software Engineer Job Can Be Hard But Not Impossible (#10)</a></li><li><a href="https://nirpeled.medium.com/how-to-boost-your-career-as-a-software-engineer-in-2020-701b7016c5ec">How To Boost Your Career As A Software Engineer In 2020 (#9)</a></li><li><a href="https://theblog.workey.co/when-is-the-best-time-to-refactor-your-code-32be104701dd">When Is The Best Time To Refactor Your Code? (#8)</a></li></ul><p><strong><em>Any questions or comments? Ping me on </em></strong><a href="https://www.linkedin.com/in/nirpeled/"><strong><em>LinkedIn</em></strong></a><strong><em> or comment below. And if you liked this post, please give it a clap and share to all of your friends and family.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a2975967091" width="1" height="1" alt=""><hr><p><a href="https://levelup.gitconnected.com/heres-why-all-tech-workers-should-get-a-free-tesla-12-4a2975967091">Here’s Why All Tech Workers Should Get A Free Tesla (#12)</a> was originally published in <a href="https://levelup.gitconnected.com/">Level Up Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do We Still Need QA Engineers In 2022? (#11)]]></title>
            <link>https://levelup.gitconnected.com/do-we-still-need-qa-engineers-in-2022-11-7f86b871bab6?source=rss-93821331f585------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f86b871bab6</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Nir Peled]]></dc:creator>
            <pubDate>Wed, 26 Jan 2022 16:37:52 GMT</pubDate>
            <atom:updated>2022-01-27T03:08:22.744Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S0L3uR7EcBz7sLBUksdljw.jpeg" /><figcaption>Tesla Model 3 being assembled in a Tesla Gigafactory by robots</figcaption></figure><p><strong>It’s been more than a year since my last blog post and therefore, one of my new year resolutions for 2022 is to start writing again so expect more of this :)</strong></p><p>I decided to start with a topic that is bothering me for a while now but, and this is where you come in, got a topic you’d like me to write about? Please comment below or ping me!</p><p><strong>Since I value your time and I realize that I used a click-bait for a title, I’m just gonna give you the bottom line first. Do we still need QA engineers in 2022? I believe that the answer is NO, at least not the way most of us think about what does a QA engineer does. Confused? Let me explain.</strong></p><h3>Quality Matters</h3><p>It doesn’t matter what kind of an app you’re developing, whether it’s a web app or a mobile app, or both. Quality is probably the most important thing that you should provide your users.</p><p>Quality means no bugs, no performance issues, no UI glitches, great UX and much more. This is super important because if quality is poor, a user might get annoyed or perhaps even lose trust in your product which might result in looking for an alternative, and that’s a shame.</p><p>I believe we should always do everything we can and beyond in order to achieve the best quality for our products, no question about it. With that said, I believe there’s a good way and a bad way of doing so.</p><h3>Manual Testing Is Dead</h3><p>Believe it or not, some tech companies still test their products manually. This method is outdated, error prone, unscalable, slow and expensive. Not only this is a bad way of improving your quality, it also slows down your whole development cycle which is probably the worst thing for your product and most importantly, your users.</p><h3>Automation Is King</h3><p>I’m happy to say that we have come to a point, especially in 2022, that we have so many good options for automated testing. We can now easily implement unit tests, integration tests, UI tests and last but not least, flow tests (also known as E2E or end-to-end tests) that simulate user activity.</p><p>In addition, we have great ways of monitoring traffic and errors, allowing us to catch issues or bugs way before they become critical. We also have great techniques like using feature flags to turn on/off features and probably my favorite of all, the ability to rollout a specific feature to a group of users or a percentage of users, instead of rolling out to all of your users at once.</p><p>If you combine all of these options together, you get a really awesome way of providing your users with a top quality product.</p><p><strong>Not only will you gain a more scalable, more reliable and lighting fast way of testing your product, your development cycle will speed up. This will allow you to deploy changes more often which your users will highly appreciate.</strong></p><h3>Continuous Delivery</h3><p>Probably the holy grail of software development is to achieve Continuous Delivery. This technique simply means that any code change that was made, a bug fix or a new feature, once fully tested and approved, is deployed to production.</p><p>This technique will allow you to stop managing versions, setting code freezes and most importantly, deploy more frequent with fewer changes at a time. Avoiding once-in-a-while deployments with tons of changes that can be risky.</p><p><strong>If you want to learn more about Continuous Delivery, check out my talk from a meetup from last year, I should say it’s in Hebrew.</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FnpwX-HsOrAs%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DnpwX-HsOrAs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FnpwX-HsOrAs%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/066d0dcc543446ef33b985393b813157/href">https://medium.com/media/066d0dcc543446ef33b985393b813157/href</a></iframe><h3>Let’s Clear A Few Things</h3><p>I’m not suggesting we don’t need QA engineers anymore, it’s just that testing should be more automated which means QA engineers should be writing code.</p><p>Doing so will decrease the gap between a QA engineer and a software engineer in general (FE/BE/whatever). More so, I believe that in an ideal world, all software engineers should be involved in both writing the code and also writing the code that test it, from my experience, it really does the trick.</p><p><strong>May you have an awesome year in 2022, a year without Covid and also, without manual testing of any kind!</strong></p><h3>Want More?</h3><ul><li><a href="https://nirpeled.medium.com/landing-your-first-software-engineer-job-can-be-hard-but-not-impossible-10-44cd6ed48cb0">Landing Your First Software Engineer Job Can Be Hard But Not Impossible (#10)</a></li><li><a href="https://nirpeled.medium.com/how-to-boost-your-career-as-a-software-engineer-in-2020-701b7016c5ec">How To Boost Your Career As A Software Engineer In 2020 (#9)</a></li><li><a href="https://theblog.workey.co/when-is-the-best-time-to-refactor-your-code-32be104701dd">When Is The Best Time To Refactor Your Code? (#8)</a></li></ul><p><strong><em>Any questions or comments? Ping me on </em></strong><a href="https://www.linkedin.com/in/nirpeled/"><strong><em>LinkedIn</em></strong></a><strong><em> or comment below. And if you liked this post, please give it a clap and share to all of your friends and family.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f86b871bab6" width="1" height="1" alt=""><hr><p><a href="https://levelup.gitconnected.com/do-we-still-need-qa-engineers-in-2022-11-7f86b871bab6">Do We Still Need QA Engineers In 2022? (#11)</a> was originally published in <a href="https://levelup.gitconnected.com/">Level Up Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Landing Your First Software Engineer Job Can Be Hard But Not Impossible (#10)]]></title>
            <link>https://nirpeled.medium.com/landing-your-first-software-engineer-job-can-be-hard-but-not-impossible-10-44cd6ed48cb0?source=rss-93821331f585------2</link>
            <guid isPermaLink="false">https://medium.com/p/44cd6ed48cb0</guid>
            <category><![CDATA[junior-developer]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[hiring-tips]]></category>
            <dc:creator><![CDATA[Nir Peled]]></dc:creator>
            <pubDate>Wed, 11 Nov 2020 21:02:13 GMT</pubDate>
            <atom:updated>2020-11-19T03:42:28.498Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Nt7EqI1GWGaqC2LQ.jpg" /><figcaption>The intro of <a href="https://en.wikipedia.org/wiki/Silicon_Valley_(TV_series)">Silicon Valley</a>, a TV show by HBO</figcaption></figure><p>I recently gave a talk to an awesome group of people who participate in a <a href="https://www.appleseeds.org.il/bootcamp2021">FullStack Bootcamp</a>, done by an NGO called <a href="https://www.appleseeds.org.il/">AppleSeeds</a> that I volunteer at from time to time. The students are about to graduate and their first step will be looking for their job in the tech industry.</p><p>Even before the coronavirus (COVID-19) outbreak earlier this year, it wasn’t easy finding your dream job or any job when you have no experience. In today’s market, many companies are no longer hiring or only hiring developers with experience.</p><p><strong>Those who may still be looking to hire are now flooded with resumes because of the pandemic. With that said, it may be hard to land a first job without having experience, but not impossible.</strong></p><p>We talked about what they should expect, how to be prepared and what to focus on not only to find their first job but make an educated decision about it, since it’s their first step in building their career. Are you at the same spot? I believe that my tips can help you out.</p><h3>Be Active</h3><p>Even before the coronavirus hit us, about 50% of new hires are based on friend referral programs, it’s the best way for a company to hire and yes, also the cheapest.</p><p>That’s exactly why you should use all of your connections on LinkedIn, Facebook or whatever social platform to get to the hiring manager or the HR manager. Which might lead to a phone call that might lead to your next interview. You’ll be amazed how effective and priceless this is.</p><h3>Come Prepared</h3><p>Once you have an interview scheduled, do everything in your power to come fully prepared for the unknown. Start with the company’s website, check out their products and solutions. Continue with their <a href="https://www.linkedin.com/">LinkedIn</a> account, check if you have a connection that works or used to work there and can give you feedback.</p><blockquote><em>Want to read this story later? </em><a href="http://usejournal.com/app/signup?save_link=https://blog.usejournal.com/landing-your-first-software-engineer-job-can-be-hard-but-not-impossible-10-44cd6ed48cb0"><em>Save it in Journal.</em></a></blockquote><p>Use <a href="https://www.crunchbase.com/">Crunchbase</a> to find out more about who invested in the company, how much and when. Check out sites like <a href="https://www.glassdoor.com/">Glassdoor</a> or <a href="http://www.indeed.com/">Indeed</a> to find out more about their interview process from real people that interviewed before you.</p><p><strong>You’ll be amazed by how much information is out there.</strong></p><h3>Ask Questions</h3><p>One of the many things that I like to check as an interviewer is whether or not the person sitting in front of me (whether physically or on a Zoom call), is asking me questions. This shows me that the person is intrigued, interested and eager to understand or learn something new.</p><h3>Think Out Loud</h3><p>You probably heard this one before but I just want to make it super clear of how important it is to think out loud when asked a question, especially a technical one. Thinking out loud shows the interviewer the way you process information and how you handle challenges. <strong>In many cases, it’s not about the solution as much as the path that took you there.</strong></p><h3>It’s Okay Not To Know</h3><p>It’s in our nature not to admit that we simply don’t know. If you get lost in Bangkok, the worst possible thing you can do is ask for directions from a stranger, there is a very high chance although they will be very friendly, they will give you instructions, regardless if they actually know or not the right way.</p><p>When interviewed, it’s perfectly fine to say that you simply don’t know the answer to the question. You’re not supposed to know everything and on the spot. It’s better to admit it than to try to bullshit your way out of it.</p><h3>What Can I Learn For My Next Position?</h3><p>Given the fact that the average time people spend with a single company is between two and three years, you always need to keep in mind that your current position is a milestone in order to get your next one.</p><p><strong>I know, it sounds a bit harsh. What I mean is that you should always aim for a place that can teach you new tricks or in other words, when it feels that you’re in your comfort zone for too long, it’s time to make a change.</strong></p><h3>It’s (Not) All About The Money</h3><p>Money is a good incentive but not the best one. Once you have an offer on the table, your decision should be based on more important points like work-life balance, vacation policy, stock options, new technology, the people, the company’s culture, etc.</p><h3>Better To Walk Away Than To Tolerate Nonsense</h3><p>Many interviewers (and interviewees) fail to acknowledge that an interview process is actually a tool to assess how real-life looks like, a tool given to you for free. Was the interviewer late or rude? They will probably treat you the same way if you work together.</p><p><strong>Use the interview process to understand the culture of the company and of the person interviewing you. Be aware of the small minor stuff, good or bad.</strong></p><h3>Know Your Worth</h3><p>Probably the best tip on my list. Many unexperienced developers will go above and beyond to land their first job, and in some cases, will think less of themselves just because they lack experience. This might result with accepting a lower salary, taking the first offer on the table or even worst, joining a bad company or working for a bad manager, knowingly.</p><p><strong>Nobody is doing you a favor when they hire you. Yes, a good match is a win-win and believe me when I tell you, many tech companies actually prefer hiring unexperienced developers.</strong></p><p>It’s usually much cheaper, there is no ego involved and it’s much easier to shape an unexperienced mind to the methods a company believes in. This is not a bad thing, you just need to understand that in some cases, you might be doing them a favor and not the other way around.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/326/0*fBZ_8OWUqVFzYKP_.jpeg" /></figure><h3>More Blog Posts</h3><ul><li><a href="https://medium.com/@nirpeled/how-to-boost-your-career-as-a-software-engineer-in-2020-701b7016c5ec">How To Boost Your Career As A Software Engineer In 2020</a></li><li><a href="https://theblog.workey.co/when-is-the-best-time-to-refactor-your-code-32be104701dd">When Is The Best Time To Refactor Your Code?</a></li><li><a href="https://theblog.workey.co/the-difference-between-a-good-software-engineer-and-a-great-software-engineer-2726bb675627?source=your_stories_page---------------------------">The Difference Between A Good Software Engineer And A Great Software Engineer</a></li></ul><p><strong><em>Any questions or comments? Ping me on </em></strong><a href="https://www.linkedin.com/in/nirpeled/"><strong><em>LinkedIn</em></strong></a><strong><em>, </em></strong><a href="https://twitter.com/peled_nir"><strong><em>Twitter</em></strong></a><strong><em> or comment below. And if you liked this post, please give it a clap and share to all of your friends and family.</em></strong></p><h4>More from Journal</h4><p>There are many Black creators doing incredible work in Tech. This collection of resources shines a light on some of us:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fusejournal.com%2Fapp%2Fembed%2Fjournal%3Aspace%3Aproject%2F5c84f6f0-715c-48b8-9387-9e74f33b7a7b&amp;display_name=Journal&amp;url=https%3A%2F%2Fusejournal.com%2Fapp%2Fspace%2Fjournal%3Aspace%3Aproject%2F5c84f6f0-715c-48b8-9387-9e74f33b7a7b&amp;image=https%3A%2F%2Fimperio.usejournal.com%2Fimage%2Fjournal%3Aspace%3Aproject%2F5c84f6f0-715c-48b8-9387-9e74f33b7a7b%2F1602668529%3Fclient%3Dfacebook&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=usejournal" width="900" height="710" frameborder="0" scrolling="no"><a href="https://medium.com/media/ca84c63a615be91123438987244ec06c/href">https://medium.com/media/ca84c63a615be91123438987244ec06c/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44cd6ed48cb0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Boost Your Career As A Software Engineer In 2020]]></title>
            <link>https://nirpeled.medium.com/how-to-boost-your-career-as-a-software-engineer-in-2020-701b7016c5ec?source=rss-93821331f585------2</link>
            <guid isPermaLink="false">https://medium.com/p/701b7016c5ec</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Nir Peled]]></dc:creator>
            <pubDate>Wed, 01 Jan 2020 19:11:03 GMT</pubDate>
            <atom:updated>2020-11-20T21:14:16.131Z</atom:updated>
            <content:encoded><![CDATA[<h3>How To Boost Your Career As A Software Engineer In 2020 (#9)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wwhPxyYMjI3MRheMV057Tg.jpeg" /></figure><p>Today is the first day of 2020 (yay!). During this time of the year — I like to give some thought about where I am in life, evaluate if I achieved my goals for the past year and set new goals for the upcoming year. I like to do this both on a personal level and a professional level, for the sake of this post — let’s focus on the professional level.</p><p><strong>For the past decade I have worked for six startup companies — here’s my </strong><a href="https://www.linkedin.com/in/nirpeled/"><strong>LinkedIn</strong></a><strong> profile. I can’t tell for sure if it’s a bad or a good thing but it sure helped to shape the person that I am today. It helped me become better with decision making that affects my professional life.</strong></p><p>Many people find it confusing or intimidating to make hard life-changing decisions such as quitting a job, asking for a raise, asking for a promotion, etc when in fact they fail to understand that for most cases, not making a decision is simply letting someone else make that decision for them.</p><p>So, what can be done? It’s actually pretty simple.</p><h3>Be the best of what you do</h3><p>No, I don’t mean that you need to be the best at everything but you should at least be the best on a few subjects — choose the ones that inspire you and learn everything about it, become an expert, teach others and before you know it, you’ll become the go-to person within your company for that stuff.</p><p>The tech industry evolves super-fast and so should you. React, for example, was only released 6.5 years ago (2013) and it’s incredible how huge its eco-system is nowadays, with new versions coming up every few months, with new React based libraries, React Native and many more.</p><p>This is exactly why you need to focus yourself and keep getting updated on what makes you tick. Never lose focus or you’ll find yourself outdated quickly.</p><h3>Self-confidence is key</h3><p>Stop being a people pleaser.</p><p>It’s perfectly normal that you’re a nice person and you want the people around you to like you at work but be careful not to commit yourself to impossible deadlines or take tasks upon yourself that are out of your scope.</p><p>Don’t be afraid to argue your case when necessary. A technical argument between co-workers is perfectly normal as long as it’s a polite one. Be respectful but yet always raise a flag or discuss a better way to solve a problem if you have one.</p><p><strong>Be confident of who you are and the value that you bring to the company you work for — this is exactly why you were hired in the first place. You might need to remind this to the person who hired you from time to time and that’s okay.</strong></p><h3>Timing is everything</h3><p>As with everything in life, timing is key.</p><p>Are you ready to ask for that raise? Make sure it’s the right time — avoid doing so if the company is in a panic mode because of an upcoming huge release or just about to run out of funds, learn to be patient yet assertive.</p><p><strong>I was once asked during an interview — “How will I know that you’ll be loyal to the company and not leave after two years?”. I replied politely that I’m always 100% loyal to the company I work for, until the last day with the company.</strong></p><p>What I mean by that is — it’s crucial to know when to join a company and more importantly when to leave a company, especially in our industry that is super fragile. The day you lose interest in going to the office is the day you should consider your next step in your career.</p><h3>It’s okay to be picky</h3><p>A few years back, I interviewed for about 25 different companies. No, I’m not crazy (well maybe a little bit) and no, I’m not enjoying interviews (well maybe a little bit). I did so because I allowed myself to be picky about my next step in my career — and you should do the same.</p><p>It was very well planned — I only interviewed for positions in companies that really appealed to me so I won’t waste precious time. I kept it quiet while still working at my current job and it took me a couple of months which I was fine with in the first place.</p><p>Every person that ever interviewed me will tell you that I love asking questions. This is true not because I like to be a troublemaker but because I like to know exactly what I’m getting myself with. You never know what will you reveal or gain out of this.</p><p><strong>Always come prepared for an interview about who’s the company, what it does, who are its founders, who they raised money from, what’s their business model and what’s their plan for the next two years — if they can’t answer you any of these questions, decline politely and walk away.</strong></p><h3>Take risks</h3><p>Sometimes you’ll have to just trust your guts about something. You can and should always consult with friends, family, your better half but at the end of the day — you’ll have to decide by yourself.</p><p>Not always you’ll have all of the data you need to make a smart calculated decision — for example, will this new and awesome startup that just offered you that awesome position will still be alive next year? Nobody knows for sure.</p><p><strong>Just remember that when you choose not to make a decision, you let someone else to make that decision for you, for better or for worse.</strong></p><h3>Luck is when opportunity meets preparation</h3><p>Being lucky is probably the best ingredient for every success. Sometimes you just have to be a bit lucky. I was very lucky to have many opportunities in life, I was lucky to have the bosses I had, the co-workers I had, etc.</p><p><strong>With that said, if you set your goals and make the right preparations, you might get a little bit more luck in your life — give it a try, it won’t cost a thing.</strong></p><p>Six months ago, I left <a href="https://www.gloat.com/">Gloat</a> after three years in which I saw the company grow from 10 people in a (very) small office to almost 50 people, we moved to a new big and fancy office, the product grew from a not-so-fancy web app into two new shiny web apps and two new mobile apps for both iOS and Android, we pivoted the product endless times and yeah — all of that happened within three years.</p><p>I left Gloat in order to start a new adventure as the Front End Guild Master at <a href="https://www.zeitgold.com/">Zeitgold</a> and I couldn’t be happier. What exactly does a Front End Guild Master do? I promise to let you know in one of my next posts so stay tuned!</p><p><strong>Are you ready to check out your next step in your career? Go ahead and check out </strong><a href="https://www.gloat.com/"><strong>Gloat’s marketplace</strong></a><strong>. Do you wanna work with me? Check out </strong><a href="https://www.zeitgold.com/careers"><strong>Zeitgold’s open positions</strong></a><strong> or ping me </strong>🤓</p><p>May you have an awesome 2020 🥳</p><p><strong><em>Any questions or comments? Ping me on </em></strong><a href="https://twitter.com/peled_nir"><strong><em>Twitter</em></strong></a><strong><em> or comment below. If you liked this post, please give it a clap! If you really liked this post, please give it 10 claps!</em></strong></p><h3>You May Also Like</h3><ul><li><a href="https://theblog.workey.co/when-is-the-best-time-to-refactor-your-code-32be104701dd">When Is The Best Time To Refactor Your Code?</a></li><li><a href="https://theblog.workey.co/the-difference-between-a-good-software-engineer-and-a-great-software-engineer-2726bb675627?source=your_stories_page---------------------------">The Difference Between A Good Software Engineer And A Great Software Engineer</a></li><li><a href="https://theblog.workey.co/chapter-1-how-we-built-an-ios-app-from-scratch-in-less-than-90-days-ee36d2c1cedd">How We Built An iOS App From Scratch In Less Than 90 Days</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=701b7016c5ec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Is The Best Time To Refactor Your Code?]]></title>
            <link>https://nirpeled.medium.com/when-is-the-best-time-to-refactor-your-code-32be104701dd?source=rss-93821331f585------2</link>
            <guid isPermaLink="false">https://medium.com/p/32be104701dd</guid>
            <category><![CDATA[refactoring]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Nir Peled]]></dc:creator>
            <pubDate>Mon, 29 Oct 2018 12:39:27 GMT</pubDate>
            <atom:updated>2020-11-20T21:14:30.544Z</atom:updated>
            <content:encoded><![CDATA[<h3>When Is The Best Time To Refactor Your Code? (#8)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*RUS7BI4SEoWSecCyKDTi1Q.png" /></figure><p>The short answer to this question is — <strong>never</strong>.</p><p>We’ve all been there, you start working on a new feature or a bug fix that you estimated will take a day or so, but soon you realize that it’s already been two days and you’re not even close to being done; you hate to admit it, but you’re stuck.</p><p>All because of this piece of code that you depend on and all of a sudden it just doesn’t work. You check to see who’s responsible for this piece of code that’s driving you crazy — and apparently it’s you, a past version of yourself that wasn’t aware that this code will break. Another scenario is that you weren’t the one who wrote that code in the first place, but let’s face it, it’s still your problem.</p><h3><strong>Avoiding the refactor monster within you</strong></h3><p>You then face a dilemma. Should you just hack your way through it or perhaps, although you’re way behind schedule, refactor the code and make it nice and pretty? 🤔</p><h3><strong>Refactoring code does not add business value</strong></h3><p>Every time you face a dilemma like this, you should ask yourself if spending time on this will add any business value to the feature or to your company in general. 99% of the time, it just won’t.</p><p>In case you managed to convince your business and marketing departments that you have to do this refactor before continuing anything else <em>(First of all, kudos for having business and marketing departments that actually know what the hell refactoring code is )</em>— congratulations, you’re in the 1%.</p><h3><strong>So what can be done?</strong></h3><p><strong>Plenty.</strong> Although technical debt and legacy code are bad things that any good developer is afraid of, there are ways to avoid or deal with them when and if necessary.</p><h3>The best way to avoid refactors is to have clean code</h3><p>It might sound hard but it’s actually pretty easy, just do the following:</p><ol><li>Keep in mind code modularity and re-use of existing code.</li><li>Be consistent about naming and code style conventions, in fact, this should be true across your team as well.</li><li>As for shared helper methods or UI components, try to have these as generic as possible and avoid being too specific in a certain use case. It will come back and bite you in the ass one day.</li><li>Writing generic code is good, but in some cases — it’s actually easier to cover the cases you need and <em>then</em> keep improving the code to be more generic as soon as you have more than two cases of usage.</li><li>Before starting a big feature, ask someone from your team to review your strategy — the feedback you’ll get at that point might be priceless.</li></ol><h3>Plan ahead</h3><p>When planning the next items on your R&amp;D roadmap with your team, keep in mind: what could go wrong, what dependencies will you be using, and what parts of the code you might be affecting that can break or cause issues.</p><p>Review the backlog of open issues that are related to that area of code or product. The better prepared you are when you start working on something new, the less surprises you’ll have down the road.</p><h3>Refactor code on the go</h3><p>The best way to refactor code is to do so when you actually need it to behave in a different way.</p><p>For example, let’s say I’m adding a new <em>(and awesome)</em> feature that requires a new UI component. Then, a month later — I’m adding a new and completely different feature that uses the same UI component I wrote a month ago, but this time I need it to look and behave in a different way. This is a great opportunity for me to improve that UI component that will now be reused in two features, win-win.</p><h3>What about big code refactors?</h3><p>In some cases, when a code refactor is quite big and impossible to achieve in a couple of hours, it’s hard to do so on the go when working on bug fixes or adding new features.</p><p>Therefore, my suggestion is to schedule a day every once in a while, that is completely dedicated to code refactors and dealing with technical debts.</p><p>At <a href="http://www.gloat.com/">Gloat</a>, we take this very seriously and we do this every 3 weeks and it’s awesome.</p><p>Try it — you’ll thank me later!</p><p><strong><em>Happy coding!</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KVRXx8sZaieFdFBZ4W5FxQ.jpeg" /></figure><h3>Meet Daniel 👶</h3><p>In case you wondered why I haven’t posted any blog posts in a while — it’s because I recently became a dad to Daniel. Daniel just turned three months old and is already a huge fan of React, he also loves to check out career opportunities anonymously on <a href="http://gloat.com/">Gloat.com</a>.</p><p><strong><em>Any questions? Ping me on </em></strong><a href="https://twitter.com/peled_nir"><strong><em>Twitter</em></strong></a><strong><em> or comment below. If you liked this post, please give it a clap! If you really liked this post, please give it 10 claps!</em></strong></p><h3>You May Also Like:</h3><ul><li><a href="https://theblog.workey.co/the-difference-between-a-good-software-engineer-and-a-great-software-engineer-2726bb675627">The Difference Between A Good Software Engineer And A Great Software Engineer</a></li><li><a href="https://theblog.workey.co/10-facts-that-should-be-true-about-your-career-at-30-12418818eee1">10 Facts That Should Be True About Your Career at 30</a></li><li><a href="https://theblog.workey.co/chapter-3-how-we-built-an-ios-app-from-scratch-in-less-than-90-days-13205a71620a">Chapter 3: How We Built An iOS App From Scratch In Less Than 90 Days</a></li><li><a href="https://theblog.workey.co/chapter-2-how-we-built-an-ios-app-from-scratch-in-less-than-90-days-c61628ebaa9c">Chapter 2: How We Built An iOS App From Scratch In Less Than 90 Days</a></li></ul><p><em>Nir Peled is a Senior Software Engineer @ Gloat</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*X316D6OiB_oi-AqJwVcEgA.jpeg" /></figure><p><a href="http://www.gloat.com/"><em>Gloat</em></a><em> is the revolutionary AI helping to guide the careers of a connected generation. We use real time data to uncover new paths and opportunities to develop your career to its full potential. Anonymously.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=32be104701dd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Difference Between A Good Software Engineer And A Great Software Engineer (#7)]]></title>
            <link>https://nirpeled.medium.com/the-difference-between-a-good-software-engineer-and-a-great-software-engineer-2726bb675627?source=rss-93821331f585------2</link>
            <guid isPermaLink="false">https://medium.com/p/2726bb675627</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[company-culture]]></category>
            <dc:creator><![CDATA[Nir Peled]]></dc:creator>
            <pubDate>Mon, 19 Mar 2018 12:57:49 GMT</pubDate>
            <atom:updated>2020-11-18T21:18:24.495Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FNKVwr2SylDqd_02QHP4Wg.jpeg" /></figure><p>Software Engineers are expensive. Hiring a new Software Engineer is a big decision for a company. Managers, Team Leaders, R&amp;D Managers, CTOs, and CEOs all have high expectations for this pricey new hire.</p><p>Yet, no matter how fancy the title, these company leaders often fail to understand that these expectations are actually mutual.</p><p><strong>Many Software Engineers are not aware of the simple fact that their own success is very much based on the set of tools provided by the company and the managers they work for.</strong></p><p>I hear about this all the time, and have seen it myself a few times in previous companies. Very talented Software Engineers are not provided with the basics they expect from the companies they work for, which results in them leaving the company — leaving a huge void and <strong>confusion</strong> for both sides.</p><p><strong>If you’re a Software Engineer then this post will give you the tools to assess your managers to ensure that you’re in the most conducive environment to grow to your full potential.</strong></p><p><strong>If you’re a manager then this post will give you the tools to develop your team of Software Engineers to the best R&amp;D team you could imagine.</strong></p><p><a href="https://www.gloat.com/">gloat.com</a></p><h3>Transparency Is Key</h3><p>This is the first thing someone should ask and evaluate before joining a company. I believe that when companies choose to have<strong> full transparency</strong> as a general policy with their employees — everyone wins.</p><p><em>In other words, not enough transparency is a deal breaker.</em></p><p><strong>Let’s do a quick exercise — here’s a short list of questions:</strong></p><ul><li>How much money is the company making?</li><li>What are the KPIs to measure the company’s success?</li><li>What is the annual roadmap or are the company’s goals?</li><li>Are those goals or KPIs being met?</li><li>What’s the business model?</li></ul><p><strong>If you can’t answer these questions about the company you work for, I’m sure that there are many other things going on within your company that you’re not aware of — and that’s too bad, <em>for both of you.</em></strong></p><p>Software Engineering is complicated. When you build a new feature or a new product, you’ll take some time to think it over before you actually start writing code. You think about the technology you want to use, what matters most and what you need to prioritize. This is because the product that you’re building is constantly changing and evolving and you must work fluidly to keep up.</p><p>Therefore, it’s super important to know what’s going on within your company. It’s actually pretty simple: <strong>the more you know about the company’s status and goals, the better Software Engineer you’ll become, simply because you’ll know to what focus on and when.</strong></p><h3>Communication Is A Two Way Street</h3><p>As in every relationship, whether it’s romantic or professional, a relationship can only be healthy when the communication is good. I strongly recommend having a one-on-one meeting at least once every two or three months.</p><p>These frequent meetings are exactly the time and place to get feedback, talk about the things that work, and also about the things that don’t work and specifically how to improve.</p><p>It’s the time and place to talk about ideas, suggestions, problems, company goals, personal goals — you get the idea. <strong>If you don’t do it already, put something on your calendar today — <em>you’ll thank me later.</em></strong></p><h3>Millennials Work For A Purpose, Not A Paycheck</h3><p>Although this is said quite often about Millennials, I believe this is true for Software Engineers in general. We need a purpose, one that will make us feel good about what we do.</p><blockquote>“Fulfillment at work, fulfillment at home… Millennials want it all and they want it fast…They’re constantly questioning where they are going next and why. That is, which position they will hold next. If your organization can’t tell them that, they’ll seek out another firm that will.”<br> — <a href="https://www.forbes.com/sites/karlmoore/2014/10/02/millennials-work-for-purpose-not-paycheck/#37ec57266a51">Forbes</a></blockquote><p>Therefore, a good manager should avoid micro-management and learn to delegate work in a way that the Software Engineer will take full responsibility for what they’re working on. By this I mean that the Software Engineer should become the owner of that feature or product, from A to Z.</p><p>I believe that in a good R&amp;D culture, Software Engineers are integrated early on in the product process, making them active participants in the decision making process. This allows them to understand the Why and the When of their work, not just the How.</p><p><a href="https://www.gloat.com/">gloat.com</a></p><h3>When Everything Goes Wrong</h3><p>A few years back I was working for a company and I wasn’t happy — I wasn’t happy because of the lack of transparency, the lack of involvement in the product process and the overall bad R&amp;D culture.</p><p>I then met with a friend and told him all about it — and he said something that I would like to share with you.<strong> </strong>He told me that instead of working for a company with a broken R&amp;D culture that is not interested in improving, leave and find a company with a culture that fits my needs, and so I did.</p><p><strong>In other words: if it’s fixable, stay and help fix it, if it’s not fixable, move on.</strong></p><p>In conclusion, when nothing works and you feel like you’re stuck, it might be time to find a new position with a new company with a fresh outlook — and if you’re planning to do so, check out <a href="http://www.gloat.com/">Gloat</a>, <em>you’ll thank me later.</em></p><p><strong><em>Any questions? Ping me on </em></strong><a href="https://twitter.com/peled_nir"><strong><em>Twitter</em></strong></a><strong><em> or comment below. If you liked this post, please give it a clap! If you really liked this post, please give it 10 claps!</em></strong></p><h3>You May Also Like:</h3><ul><li><a href="https://theblog.workey.co/chapter-3-how-we-built-an-ios-app-from-scratch-in-less-than-90-days-13205a71620a">Chapter 3: How We Built An iOS App From Scratch In Less Than 90 Days</a></li><li><a href="https://theblog.workey.co/chapter-2-how-we-built-an-ios-app-from-scratch-in-less-than-90-days-c61628ebaa9c">Chapter 2: How We Built An iOS App From Scratch In Less Than 90 Days</a></li><li><a href="https://theblog.workey.co/chapter-1-how-we-built-an-ios-app-from-scratch-in-less-than-90-days-ee36d2c1cedd">Chapter 1: How We Built An iOS App From Scratch In Less Than 90 Days</a></li><li><a href="https://theblog.workey.co/cant-hire-software-engineers-you-might-be-doing-it-wrong-3e14237e73bd">Can’t Hire Software Engineers? You Might Be Doing It Wrong</a></li></ul><p><em>Nir Peled is a Senior Software Engineer @ Gloat</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*X316D6OiB_oi-AqJwVcEgA.jpeg" /></figure><p><a href="http://www.gloat.com/"><em>Gloat</em></a><em> is the revolutionary AI helping to guide the careers of a connected generation. We use real time data to uncover new paths and opportunities to develop your career to its full potential. Anonymously.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2726bb675627" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chapter 3: How We Built An iOS App From Scratch In Less Than 90 Days (#6)]]></title>
            <link>https://nirpeled.medium.com/chapter-3-how-we-built-an-ios-app-from-scratch-in-less-than-90-days-13205a71620a?source=rss-93821331f585------2</link>
            <guid isPermaLink="false">https://medium.com/p/13205a71620a</guid>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Nir Peled]]></dc:creator>
            <pubDate>Mon, 26 Feb 2018 15:52:31 GMT</pubDate>
            <atom:updated>2020-11-18T21:18:06.388Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qcb_rZOjbDLktAek7nCPng.jpeg" /></figure><p>This is the third and final chapter of a 3 part series on how we built an iOS app from scratch in less than 90 days. The <a href="https://theblog.workey.co/chapter-1-how-we-built-an-ios-app-from-scratch-in-less-than-90-days-ee36d2c1cedd">first chapter </a>focused on the decision making phase and how we got our app off the ground. The <a href="https://theblog.workey.co/chapter-2-how-we-built-an-ios-app-from-scratch-in-less-than-90-days-c61628ebaa9c">second chapter</a> focused on what exactly is React Native and what solutions it’s helping to solve. This chapter will focus on a few things you need to know before actually working with React Native and getting your project up and running.</p><p>Yeah I know, it’s been a while since my last post, I’ve been super busy lately — working on new and exciting stuff, for starters, we went through a full rebrand recently — <a href="https://theblog.workey.co/introducing-gloat-com-6eb54c1e032a">goodbye Workey, hello Gloat</a> (!!)</p><h3>Pixels vs Points</h3><p>This may be a shocker to you, but when developing a mobile app, you’ll never have to deal with pixels ever again. Instead, you’ll be using something called points — points is a new unit to measure dimensions on mobile apps, allowing developers to focus on screen size and not actual rendering size.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VeeBbsj9aoID2u-g_SokLA.png" /><figcaption><a href="https://www.paintcodeapp.com/news/ultimate-guide-to-iphone-resolutions">The Ultimate Guide To iPhone Resolutions</a></figcaption></figure><p>Let’s say that I have two devices, the iPhone 7 and the new awesome iPhone X, both of them have a screen width of 375 points, but if you calculate the actual screen width in rendered pixels, it will be 750 (375x2) and 1125 (375x3) on the iPhone 7 and X, accordingly.</p><blockquote>“Pixels are the smallest physical element that we can control on a digital display. The more pixels can be fitted into a specific screen size, the higher the PPI (pixels-per-inch), and the clearer the rendered content becomes.”-<a href="https://ivomynttinen.com/blog/ios-design-guidelines">iOS Design Guidelines</a></blockquote><p>Working with points, will allow us developers to always use a specific size ratio and let the device running my app render the right scale, making the app always look good with the same ratio on all devices.</p><blockquote>“Points are a resolution-independent measurement. Depending on the screens pixel density, a point can contain multiple pixels (e.g., 1 pt contains 2 x 2 pixels on a regular retina display).” -<a href="https://ivomynttinen.com/blog/ios-design-guidelines">iOS Design Guidelines</a></blockquote><p>Still confused? Check out the next video:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F169809377&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F169809377&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F574647435_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1200" frameborder="0" scrolling="no"><a href="https://medium.com/media/1bcdbd949c06ac3c8d48477593e07bdf/href">https://medium.com/media/1bcdbd949c06ac3c8d48477593e07bdf/href</a></iframe><h3>Flexbox</h3><p>Flexbox is not new and widely used on the web, however — on mobile and specifically on React Native, it’s the only way to go. This might be a bit weird at the beginning but once you learn the power of it, there’s no going back — you’ll just love it.</p><p>When I started with Flexbox, I found this “<a href="http://flexboxfroggy.com/">Flexbox Froggy</a>” learning app game which is simply awesome, it will help you understand the basics through a quick game that is very well done, give it a try!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*17XQRhN2d7sXuMneFGnzbg.png" /></figure><p><a href="http://flexboxfroggy.com/">Flexbox Froggy</a></p><p>The one thing you need to remember is that in the world of mobile, <strong>flex-direction</strong> is defaulted to <strong>column</strong> so don’t forget to set it to <strong>row</strong> if necessary.</p><h3>Navigation in Mobile Apps</h3><p>I have to admit that navigation in mobile apps was one of my biggest challenges as a web developer building a mobile app. This is truly a tough nut to crack and probably because of that, you’ll see that many developers try to tackle mobile navigation issues, unfortunately, most of today’s solutions are simply not good enough and only solve part of the problem.</p><p>On the web, we’re used to the concept of URLs, URL params and query params, but on mobile… It’s all gone! <strong>No URLs whatsoever, and on top of that, you have different ways to navigate within a mobile app — there are tabs, stacks and modals, for which you need to maintain the correct hierarchy and order.</strong></p><p>Many try to solve these issues and you’ll see many different libraries that claim to have a good solution, the most famous ones are:</p><ol><li><a href="https://reactnavigation.org/">React Navigation</a></li><li><a href="https://reacttraining.com/react-router/native/guides/philosophy">React Router</a> (Native)</li><li><a href="https://github.com/wix/react-native-navigation">Wix’s React Native Navigation</a></li><li><a href="https://github.com/airbnb/native-navigation">Airbnb’s Native Navigation</a></li></ol><p>Airbnb’s solution is still in beta, Wix’s solution is not very well maintained and has hundred of open issues, React Router has an amazing solution and it’s very well known for their awesome Web navigation <em>(I use it and I love it), </em>but it requires some extra work because it doesn’t include the animations that you’re hoping to get as part of it <em>(last time I checked, that is — it might be better now).</em></p><p>That leaves us with React Navigation — I have to say, a few months back, I tried all four of them, each one turned out to be great in some aspects and bad in other aspects, <strong>the one I liked the most back then was React Navigation because it’s fully cross-platform (for both iOS and Android), supports three modes of navigation — tabs, stacks and modals (all of which I needed) and on top of everything, it has a built-in solution for animations, it seems like I won the jackpot!</strong></p><p>However, it was lacking good documentation, had a lot of bugs and open issues and was missing features and abilities. With that said, since then it has matured a lot and it is now very stable and very well maintained. They recently announced <a href="https://reactnavigation.org/blog/2018/02/06/react-navigation-1.0.html">ending their beta period and released version 1.0</a> and it was adopted by the <a href="http://www.expo.io/">Expo </a>community, which is always a good sign.</p><p>Thinking back, I’m very happy with React Navigation and I believe I made a safe bet, but I strongly recommend checking out the competition before choosing something that might be very hard to undo in your app in the long run.</p><p><strong>Any questions or suggestions? Please ping me on </strong><a href="https://twitter.com/peled_nir"><strong>Twitter</strong></a><strong> or comment below. If you liked this post, please give it a clap! If you really liked this post, please give it 10 claps!</strong></p><h3>You May Also Like:</h3><p><a href="https://theblog.workey.co/chapter-2-how-we-built-an-ios-app-from-scratch-in-less-than-90-days-c61628ebaa9c">Chapter 2: How We Built An iOS App From Scratch In Less Than 90 Days</a><br><a href="https://theblog.workey.co/chapter-1-how-we-built-an-ios-app-from-scratch-in-less-than-90-days-ee36d2c1cedd">Chapter 1: How We Built An iOS App From Scratch In Less Than 90 Days</a><strong><br></strong><a href="https://theblog.workey.co/cant-hire-software-engineers-you-might-be-doing-it-wrong-3e14237e73bd">Can’t Hire Software Engineers? You Might Be Doing It Wrong</a><br><a href="https://theblog.workey.co/stop-being-afraid-of-git-and-start-using-it-the-right-way-e784da034ba8">Stop Being Afraid of Git and Start Using It The Right Way</a><br><a href="https://theblog.workey.co/6-reasons-why-react-is-todays-best-way-to-build-your-web-apps-9e7c6013514">6 Reasons Why React Is Today’s Best Way to Build Your Web Apps</a></p><p><em>Nir Peled is a Senior Software Engineer @ Gloat</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*X316D6OiB_oi-AqJwVcEgA.jpeg" /></figure><p><a href="http://www.gloat.com/"><em>Gloat</em></a><em> is the revolutionary AI helping to guide the careers of a connected generation. We use real time data to uncover new paths and opportunities to develop your career to its full potential. Anonymously.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13205a71620a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chapter 2: How We Built An iOS App From Scratch In Less Than 90 Days (#5)]]></title>
            <link>https://nirpeled.medium.com/chapter-2-how-we-built-an-ios-app-from-scratch-in-less-than-90-days-c61628ebaa9c?source=rss-93821331f585------2</link>
            <guid isPermaLink="false">https://medium.com/p/c61628ebaa9c</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[react-native]]></category>
            <dc:creator><![CDATA[Nir Peled]]></dc:creator>
            <pubDate>Wed, 29 Nov 2017 14:12:15 GMT</pubDate>
            <atom:updated>2020-11-18T21:17:47.374Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J6adknoL2zBoElOTfkVCdw.jpeg" /></figure><p>This is the second chapter of a 3 part series on how we built an iOS app from scratch in less than 90 days. The <a href="https://theblog.workey.co/chapter-1-how-we-built-an-ios-app-from-scratch-in-less-than-90-days-ee36d2c1cedd">first chapter </a>focused on the decision making phase and how we got our app off the ground. This chapter will focus on what you need to know before getting started with React Native.</p><p>Assuming that you read the <a href="https://theblog.workey.co/chapter-1-how-we-built-an-ios-app-from-scratch-in-less-than-90-days-ee36d2c1cedd">first chapter</a>, I hope that I convinced you of why we chose React Native to build our mobile app. The next step will be to discuss what I believe you need to know to get started. I’ll also cover issues and challenges you need to be aware of. <strong>In other words — everything I wish I knew when I started learning React Native a few months ago.</strong></p><h3>Do I Need To Know React?</h3><p>Probably the most common question about React Native, at least that I get asked is whether or not you need to have previous knowledge of React before working with React Native. <strong>The short answer is no, </strong>you don’t need any previous knowledge of React when working with React Native.</p><p>React Native shares many of the React concepts such as separating your code into small multi-use components, the life-cycle of a component, one-way data flow like when using Redux. These are just three examples of what React and React Native have in common. With that said, React Native doesn’t actually require any previous knowledge or experience with React.</p><p><strong>The long answer is that although you’re <em>not </em>required to know or build your non-mobile apps with React, you will gain a lot from doing so.</strong></p><p>I believe that the biggest advantage that React Native has to offer is that you can reuse a huge portion of your code between any web-based apps, iOS apps and Android apps. In our case, the <a href="https://itunes.apple.com/us/app/workey/id1268420519?mt=8"><strong>Workey iOS app</strong></a><strong> reuses at least 50% of the code of our web-based app (written in React) and the upcoming Android app will be reusing at least 80% of the iOS app code base — this is huge!</strong></p><p>This will not only save you precious time and effort, but also avoid spending a whole lot of time training developers with new programming languages like Objective-C and Swift for iOS or Java for Android.</p><h3>Native Mobile App vs Mobile Web App</h3><p>Before we go any further and delve deep into how we work with React Native, it’s crucial to understand that unlike any other hybrid mobile app framework or technology, using React Native will not get you a mobile web app, which is basically a web app wrapped in a native container.</p><p><strong>Instead — your JavaScript code will get compiled into a real native mobile app, making it indistinguishable from an iOS app built using Objective-C or Swift, or an Android app using Java.</strong></p><p>This is truly awesome if you think about it, React Native allows you to enjoy both worlds of native and hybrid mobile apps. With that said, it’s important to understand the difference between native mobile code, which can be written in Objective-C, Swift, or Java — and React Native mobile code, which in our case, is plain JavaScript.</p><h3>Let’s Get Started</h3><p><strong>Now that we’ve covered the basics — let’s get started!</strong></p><p>Best place to get started is probably reading all about the basics of React Native <a href="https://facebook.github.io/react-native/docs/getting-started.html">in here</a>. When you’re done with some reading, I strongly recommend using a tool called <a href="https://github.com/react-community/create-react-native-app">CRNA</a> — Create React Native App, it’s a free tool made by the React Native community to allow developers, such as yourself, to avoid the boilerplate required to build a new app from scratch.</p><p>Building your “Hello World” mobile app with CRNA will only take you a few minutes, once you have the CRNA tool installed, all you need to do is run a few lines and you’ll have everything that you need, no boilerplate necessary.</p><p>Don’t believe me? Here is what you’ll need to run:</p><pre>$ npm install -g create-react-native-app<br>$ create-react-native-app my-app<br>$ cd my-app/<br>$ npm start</pre><p><strong>Yep, that’s it!</strong></p><p>Learn more about this <a href="https://github.com/react-community/create-react-native-app">here</a>.</p><h3>Write Once, Run Everywhere</h3><p>The React Native community goes through a lot of trouble to allow developers, such as yourself, to only write JavaScript, regardless of the fact that you’re building an iOS app or an Android app, this is really awesome but it comes at a price you need to be aware of:</p><blockquote>“The main limitation of a Create React Native App project is that it must be written in pure JavaScript and not have any dependencies which rely on custom native code (i.e. ones which require running react-native link to work). This allows the projects to load directly on a phone without native compilation, and also means that it’s not necessary to install or use Android Studio or Xcode.“ — CRNA</blockquote><p><strong>This means that in case you want to integrate native mobile code, written in Objective-C, Swift, or Java, depends on the mobile platform you’re building for, you won’t be able to do so with your CRNA mobile app, not out-of-the-box anyway — I’ll explain more about this later.</strong></p><p>A few months ago, the React Native community joined forces with a company called Expo and integrated their product into the CRNA tool, Expo is a true game-changer and the key that enables this cross-platform JavaScript-only mobile framework to exist.</p><h3>Expo — A True Game Changer!</h3><p><a href="http://expo.io/">Expo</a>, a startup company based in Palo Alto, California who have recently changed their name from Exponent, is a company that offers a set of tools for React Native developers.</p><p>As mentioned early, they joined forces with the React Native community and it is now integrated in the CRNA tool, allowing developers to never have to deal with native mobile code. Here’s a short video demonstrating their abilities:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FIQI9aUlouMI%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DIQI9aUlouMI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FIQI9aUlouMI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/2b2cfe4715d6dc1699479dc1cf3b1dd2/href">https://medium.com/media/2b2cfe4715d6dc1699479dc1cf3b1dd2/href</a></iframe><p><em>So yeah </em>— with Expo, you don’t have to deal with any native mobile code since everything you need is already integrated! Authentication with Facebook? Integrated. Authentication with Google? Integrated. Sentry? FireBase? Also integrated.</p><p><strong>Think about this as a framework that has pretty much the most common 3rd party integrations necessary for an average mobile app. In addition, almost any API that Expo offers, is fully cross-platform and works on both iOS and Android.</strong></p><p>I should mention that Expo is completely free and I have to admit that I’m not sure what their business plan is — I’m pretty sure that they don’t either. They might offer paid-services like support over the phone or advanced features in the future, hopefully we’ll know more soon.</p><h3>Publish Your Mobile App With Expo</h3><p>Expo also allows you to use their eco-system for publishing your mobile app to the world. This can be easily done if you simply want to publish your code as a package, which can then be used with Expo’s <a href="https://itunes.apple.com/us/app/expo-client/id982107779?mt=8">Client app</a>, this means that if you want someone to try out your new app, simply ask them to download the <a href="https://itunes.apple.com/us/app/expo-client/id982107779?mt=8">Expo Client app</a> and send them your app’s package name or link.</p><p>Learn more about this <a href="https://docs.expo.io/versions/latest/guides/publishing.html">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/392/1*Fps73C6zebslEbhfYoMZKQ.jpeg" /><figcaption>Expo’s Client app for iOS</figcaption></figure><p>Once you’re ready and want to publish your app on the App Store or Google Play, you can also use Expo to build a binary file and submit it, this will get you your own standalone app, which means that nobody has to know that you’ve been using Expo.</p><p>Learn more about this <a href="https://docs.expo.io/versions/latest/guides/building-standalone-apps.html">here</a>.</p><h3>Over The Air Updates</h3><p><strong>This is probably the most important feature Expo has to offer.</strong></p><p>Unlike the web, when developing a mobile app, we need to keep in mind that we don’t have the ability to push code changes whenever we want or need to without going through Apple’s or Google’s eco-system, meaning the App Store or Google Play, respectively. This means that we need to build a new version of our mobile app, publish it, and wait until the user will get it. Not to mention that we need to have backwards compatibility for older versions.</p><p>This is no longer the case! With Expo, we can easily publish any code changes using their eco-system. So how does it work? Simple — we publish our code as Expo packages, which our mobile app is set to fetch upon loading.</p><blockquote>“The standalone app knows to look for updates at your app’s published url, and if you publish an update then the next time a user opens your app they will automatically download the new version.” — Expo</blockquote><p><strong>Yes, this is very similar to Microsoft’s </strong><a href="https://microsoft.github.io/code-push/"><strong>CodePush</strong></a><strong>, the only difference is that it’s available out-of-the-box, no setup required, and yeah — FREE.</strong></p><h3>So What If I Do Need Custom Native Mobile Code?</h3><p>In some cases, the base framework that CRNA with Expo comes with won’t be enough for you, for example, if you need to integrate some custom native mobile code or a 3rd party integration that requires native mobile code that is not available on the Expo eco-system, you’ll then need to “detach” your app.</p><p>Detaching your app means that your app will no longer live in the Expo eco-system and you’ll loose some of the benefits it provided, for example, you won’t be able to publish your app using Expo, you’ll have to do so on your own with Xcode for iOS or Android Studio for Android. You’ll no longer be able to use Expo’s Push Notification API, you’ll have to implement your own. Yes — this comes with a price, therefore you’ll need to be careful and think about what you really need.</p><blockquote>“Expo isn’t ready to be used for all apps yet. There are plenty of cases where its current constraints may not be appropriate for your project.” — Expo</blockquote><p>Yes, Expo may not be the best fit for your mobile app, with all of the great benefits it presents, you might be better off without it, therefore — make sure to read <a href="https://docs.expo.io/versions/latest/introduction/why-not-expo.html">this</a> “Why Not Expo” page before you start using it.</p><h3>A Quick Recap</h3><ul><li>No need for any previous knowledge of React when dealing with React Native, but you’ll gain a lot if you choose to do both, especially a huge reuse of your code.</li><li>React Native will get you a pure native mobile app.</li><li>Start with a tool called <a href="https://github.com/react-community/create-react-native-app">CRNA</a>.</li><li>Consider using Expo and its awesome eco-system and features.</li><li>Learn more about when you might need to integrate native mobile code.</li></ul><h3>A Few Words About The React Native Community</h3><p>It’s pretty amazing how quickly developers have adopted React Native and how big the community has grown since Facebook open-sourced it. The public repository of React Native in <a href="https://github.com/facebook/react-native">GitHub</a> has gained a lot of attraction and now has almost 60,000 stars and more than 1,500 active contributors — no wonder there is a new version of it every single month with tons of bug fixes and new features and improvements.</p><p>What’s even more amazing is how quickly big tech companies have adopted React Native, companies like <a href="http://www.airbnb.com/">Airbnb</a>, <a href="http://www.wix.com/">Wix</a>, <a href="http://www.microsoft.com/">Microsoft</a>, <a href="http://www.klarna.com/">Klarna</a>, <a href="https://www.walmart.com/">Walmart</a> and even <a href="http://www.tesla.com/">Tesla</a>!</p><p>But why am I telling you this? Because these companies don’t just <em>use</em> it for their production mobile apps, they are also huge contributors of the React and React Native eco-system, which is great for all of us. The more developers and companies adopt a certain technology, the better it will get and the easier it will be to use it.</p><p><strong>There are so many open-sourced projects, it is truly awesome. This is a huge plus when dealing with a new framework. There are so many developers and companies that are heavily invested in and therefore dedicated to making this work and last, so there’s no reason why you shouldn’t check it out, right?</strong></p><p>That’s all I have for you this time, but remember this is a 3 part series!</p><p><strong>On the next and final chapter we will discuss working with Xcode and the iOS Simulator, Push Notifications, handle Navigation in a mobile app, the connection between React Native and Virtual Reality and more — stay tuned!</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FIs1O1TWV0LEJi%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fexcited-the-office-celebrate-Is1O1TWV0LEJi&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FIs1O1TWV0LEJi%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="246" frameborder="0" scrolling="no"><a href="https://medium.com/media/e7b0b3e8b6f1f5ed0c0ed3ec2891f3c9/href">https://medium.com/media/e7b0b3e8b6f1f5ed0c0ed3ec2891f3c9/href</a></iframe><p>Any questions or suggestions? Please ping me on <a href="https://twitter.com/peled_nir">Twitter</a> or comment below.<br>If you liked this post, please give it a clap and send it to all your friends!</p><p><strong>You might also enjoy one of my last posts:<br></strong><a href="https://theblog.workey.co/chapter-1-how-we-built-an-ios-app-from-scratch-in-less-than-90-days-ee36d2c1cedd"><strong>“</strong>Chapter 1: How We Built An iOS App From Scratch In Less Than 90 Days”</a><strong><br></strong><a href="https://theblog.workey.co/cant-hire-software-engineers-you-might-be-doing-it-wrong-3e14237e73bd"><strong>“</strong>Can’t Hire Software Engineers? You Might Be Doing It Wrong”</a><br>“<a href="https://theblog.workey.co/stop-being-afraid-of-git-and-start-using-it-the-right-way-e784da034ba8">Stop Being Afraid of Git and Start Using It The Right Way</a>”<br>“<a href="https://theblog.workey.co/6-reasons-why-react-is-todays-best-way-to-build-your-web-apps-9e7c6013514">6 Reasons Why React Is Today’s Best Way to Build Your Web Apps</a>”</p><p><em>Nir Peled is a Senior Software Engineer @ </em><a href="https://www.workey.co/"><em>Workey</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/64/1*KFAkQwdZu7xYSd_SjAddKA.png" /></figure><p><a href="https://www.workey.co/"><em>Workey</em></a><em> is the revolutionary AI helping to guide the careers of a connected generation. We use real time data to uncover new paths and opportunities to develop your career to its full potential. Anonymously.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c61628ebaa9c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chapter 1: How We Built An iOS App From Scratch In Less Than 90 Days (#4)]]></title>
            <link>https://nirpeled.medium.com/chapter-1-how-we-built-an-ios-app-from-scratch-in-less-than-90-days-ee36d2c1cedd?source=rss-93821331f585------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee36d2c1cedd</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Nir Peled]]></dc:creator>
            <pubDate>Thu, 16 Nov 2017 16:11:36 GMT</pubDate>
            <atom:updated>2020-11-18T21:17:32.420Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wj6GTikr04rhK21t5-h9HQ.jpeg" /></figure><p>This is the first chapter of a 3 part series on how we built an iOS app from scratch in less than 90 days. This first chapter will focus on the decision making phase and how to get it off the ground.</p><p>Earlier this year, I sat with the team here at <a href="https://www.workey.co/">Workey</a> in one of our regular planning meetings and we decided that it’s about time that we offer our users a mobile application. Our platform was fully compatible with mobile devices but we didn’t have a specific mobile app. We wanted to allow our users to engage with their beloved <a href="https://www.workey.co/">Workey</a> on the go even easier.</p><p><strong>We’ve decided that this was one of our goals for 2017 — that’s all we knew at the time. First we figured out the why and then we started working on the how and when.</strong></p><p>The why was: to improve our mobile users’ experience and decided that the way to do that was to allow them to have a <strong>native</strong> mobile application.</p><h3>Native Mobile Applications Are Dead</h3><p>According to some recent studies, and many posts on different social media, many believe that the era of building a native mobile application is dead and that more and more people prefer using the web to pretty much avoid installing new applications on their phones.</p><p>Yes, in the past couple of years, mobile phones and mobile browsers have improved significantly and have changed the way we surf the web on our phones. New technologies like <a href="https://developers.google.com/web/progressive-web-apps/">Progressive Web Apps </a>are now available and widely used. This explains why people are being picky about what they do choose to install locally.</p><p>Another issue affecting the lack of app downloads is the fact that nowadays, apps are way more complex, support a wide variety of different devices and versions of iOS, causing the app size to be extremely large. Take the Facebook app for example, it’s 390MB!! Will you be willing to spend that bandwidth and storage to install it on your phone? What about downloading updates that Facebook release every two weeks?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j94GoriUGxetZEElg6p_ig.png" /><figcaption>The Facebook App for iOS devices —can be yours for only 390MB!!</figcaption></figure><h3>A $70 Billion Industry</h3><p>On the other hand, a few months ago, Apple issued a press release announcing how much money they have paid for Apple Developers (that have built apps mainly for the iOS and MacOS) since 2008, and yes, this is not a mistake, the total amount is $70 Billion! And yeah, this doesn’t include Google’s Android Store — Google Play.</p><blockquote>“Apple today announced that its global developer community has earned over $70 billion since the App Store launched in 2008.” — <a href="https://www.apple.com/newsroom/2017/06/developer-earnings-from-the-app-store-top-70-billion/">Apple</a></blockquote><p>Hmm, just to be more clear about this, $70 Billion = <strong>$70,000,000,000,000</strong>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FxT77XWum9yH7zNkFW0%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FxT77XWum9yH7zNkFW0%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia1.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExZTR6MnFoZGE1aTFoeTZrNWhpeWlyY2xiY2hsa3gzNTFuYm0zYXFiZiZlcD12MV9naWZzX2dpZklkJmN0PWc%2FxT77XWum9yH7zNkFW0%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/9ef2072a5bab8b28661940e1c82a09f7/href">https://medium.com/media/9ef2072a5bab8b28661940e1c82a09f7/href</a></iframe><h3>Confused? So Were We</h3><p>Yes, I truly believe that the entire mobile industry is going through a huge change but with that said, I also believe that in some cases, a native mobile app will allow your users to get an improved user experience by some minor yet simple things, for example — native push notifications, and a better usage of the device’s sensors, like its GPS and gyroscopes.</p><h4><strong>That’s it! We’ve decided that there’s room for a native mobile app among our web-based platform. And we’re off!</strong></h4><h3>iOS, Android or *Gasp* Both?</h3><p>Moving forward, our next million dollar question is what mobile platform should we choose to tackle first.</p><p>iOS or Android? Hmm, this is a big question to answer needless to say. I was trying to get some data about the marketshare of both mobile platforms and it’s truly impossible to find anything reliable enough.</p><p>We figured it will be impossible to choose both and we needed to pick one, mainly because of a tight schedule, we wanted to have a first version up and running within two to three months.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kppCENia148lDZVVUxwpuA.png" /></figure><p><strong>At the end we decided to start with the iOS platform for two crucial reasons:</strong></p><ol><li>According to our data, most of our mobile users use an iOS device, shocking, huh?</li><li>We believed it will be easier and therefore quicker to develop a mobile apps for iOS, given the fact that this was our first time ever developing a mobile app. We didn’t have a lot on which to base our assumption, so we kept reminding ourselves about reason #1.</li></ol><h3>Choosing The Right Technology</h3><p>This is where things got interesting!</p><p>By interesting, I mean, we decided to build a new mobile app for the iOS platform from scratch in less than 3 months— and none of us had any mobile apps under our belt at all, we had the following three options:</p><ol><li>Objective-C</li><li>Swift</li><li>React Native</li></ol><h3>Objective-C and Swift</h3><p>Objective-C has been around for a long time (since 1984) and has been serving as the main programming language used by Apple for their OSX (now called MacOS) and iOS operating systems.</p><p>In 2014, Apple introduced Swift — their new built from scratch programming language that by now is being used for all of Apple’s operating systems, such as iOS, macOS, watchOS and tvOS.</p><p>Swift is built with the open-source LLVM compiler framework but also uses the Objective-C runtime library, this allows combining C, Objective-C, C++ and Swift code all together — making the migration process a whole lot easier for an Apple Developer.</p><p>With that said and with the fact that Apple has already released Swift 4, many Apple Developers still prefer the old and stable Objective-C, shocking really.</p><blockquote>“Swift is a powerful and intuitive programming language for macOS, iOS, watchOS and tvOS. Writing Swift code is interactive and fun, the syntax is concise yet expressive, and Swift includes modern features developers love. Swift code is safe by design, yet also produces software that runs lightning-fast.” — Apple</blockquote><h3>React Native</h3><p>The third option we had on our list was React Native and we quickly realized it to be our natural winner since all of our web based products use React.</p><p>Facebook announced and released React Native to the public a few years back, on <a href="https://code.facebook.com/posts/754869551286944/f8-big-technology-bets-and-open-source-announcements/">March 2015</a> and since then it’s become one of the most loved and supported open-source projects out there, with more than 1,500 contributors, more than 13,000 forks and a little bit under 56,000 stars on <a href="https://github.com/facebook/react-native">GitHub</a>.</p><p>In fact, React Native’s public repository is ranked the 4th of most starred repository on GitHub.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1013/1*hZ7x5pHQ8rlOmNxGLkq5SA.png" /><figcaption>React Native is ranked the #4 most starred public repositories on GitHub (55.9k)</figcaption></figure><h3>Learn Once, Write Anywhere</h3><p>React Native became so famous and so well adapted by developers world-wide mainly because of the simple yet genius concept of bringing React and React’s eco-system into the world of mobile development, to be more specific, React Native basically allows a React developer to build iOS and Android mobile native apps without any iOS/Android specific language knowledge. That’s really amazing.</p><p><strong>Imagine that you have a team of Software Engineers that have some experience with React, I’ve got some great news for you — you now have a team of mobile developers as well, free of charge!</strong></p><p>As I mentioned, React Native is based on React and its eco-system, allowing you to maintain all of the good parts of it, like separating your application into Components, using a one-way flow of data by using Redux or MobX, and pretty much using the great power of any library or package based on React, out of the box.</p><p>If you’re new to React, check out my post “<a href="https://theblog.workey.co/6-reasons-why-react-is-todays-best-way-to-build-your-web-apps-9e7c6013514">6 Reasons Why React Is Today’s Best Way to Build Your Web Apps</a>” I posted a while back.</p><h3>No Boilerplate</h3><p>React Native saves you time and will create whatever is necessary for iOS and Android pretty much out of the box.</p><h3>Reuse of Code</h3><p>This is probably one of the biggest benefits of using React Native, it allows you to not only reuse your code between iOS and Android, but also from your existing React apps. Yes, this is not out of the box for some parts and does not offer a 100% coverage of reuse but it will save you a lot of time.</p><p><strong>Let’s talk numbers — our iOS mobile app reuses about 60% of our web based app and the upcoming Android mobile app will be reusing about 80% of the codebase. This is pretty amazing.</strong></p><h3>Instant Updating</h3><p>Yes, this is available on other platforms and frameworks but this is so easy to use if your mobile app is based on React Native with <a href="https://expo.io/">Expo</a>, this basically allows you to push hot-fixes instantly without going through Apple’s life-cycle of releasing a new version to the AppStore.</p><h3>90 Days Later</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FGUz4_vXumIo%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DGUz4_vXumIo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FGUz4_vXumIo%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/fb0fc3aaa838714fb22b3915bdc6a286/href">https://medium.com/media/fb0fc3aaa838714fb22b3915bdc6a286/href</a></iframe><p><a href="https://itunes.apple.com/us/app/workey/id1268420519?mt=8">Workey on the App Store</a></p><p>Please check out our mobile app and let me know what you think of it! We keep releasing new versions to the AppStore with bug fixes, new features, and improvements. We also think about developing a version for Android soon so if you have an Android based phone look for us on GooglePlay soon.</p><p><strong>That’s all I have for you this time, but remember this is a 3 part series!<br></strong>Any questions or suggestions? Please ping me on <a href="https://twitter.com/peled_nir">Twitter</a> or comment below.<br>If you liked this post, please give it a clap and send it to all your friends!</p><p><strong>*</strong><a href="https://theblog.workey.co/chapter-2-how-we-built-an-ios-app-from-scratch-in-less-than-90-days-c61628ebaa9c"><strong>Check out Chapter 2!*</strong></a></p><p><strong>You might also enjoy one of my last posts:<br></strong><a href="https://theblog.workey.co/cant-hire-software-engineers-you-might-be-doing-it-wrong-3e14237e73bd"><strong>“</strong>Can’t Hire Software Engineers? You Might Be Doing It Wrong”</a><br>“<a href="https://theblog.workey.co/stop-being-afraid-of-git-and-start-using-it-the-right-way-e784da034ba8">Stop Being Afraid of Git and Start Using It The Right Way</a>”<br>“<a href="https://theblog.workey.co/6-reasons-why-react-is-todays-best-way-to-build-your-web-apps-9e7c6013514">6 Reasons Why React Is Today’s Best Way to Build Your Web Apps</a>”</p><p><em>Nir Peled is a Senior Software Engineer @ </em><a href="https://www.workey.co/"><em>Workey</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/64/1*KFAkQwdZu7xYSd_SjAddKA.png" /></figure><p><a href="https://www.workey.co/"><em>Workey</em></a><em> is the revolutionary AI helping to guide the careers of a connected generation. We use real time data to uncover new paths and opportunities to develop your career to its full potential. Anonymously.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee36d2c1cedd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Can’t Hire Software Engineers? You Might Be Doing It Wrong (#3)]]></title>
            <link>https://nirpeled.medium.com/cant-hire-software-engineers-you-might-be-doing-it-wrong-3e14237e73bd?source=rss-93821331f585------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e14237e73bd</guid>
            <category><![CDATA[recruiting]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Nir Peled]]></dc:creator>
            <pubDate>Thu, 30 Mar 2017 15:12:06 GMT</pubDate>
            <atom:updated>2020-11-18T21:17:13.725Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zpoyt3o-GZbMMkyC6RhNwQ.jpeg" /></figure><p>Yeah, I know, the web is full with posts about how to land your dream job, how to get that one special job interview that you will change your life — but this post is different!</p><p><strong>If you’re a company looking to hire, you might be making mistakes that will eventually turn off the right people and attract the wrong type of talent.</strong></p><p>I’ve been on both sides of the hiring table, as an interviewee and as an interviewer — and I have to admit: yes — many interviewees make mistakes but in many cases, it’s actually the interviewer making the mistake causing the interview to go south. This, of course, wastes precious time for both sides and neither party goes home happy.</p><p>These mistakes can be easily avoided, resulting in a perfect match with a super fast process.</p><p><strong>Looking to hire your next Rockstar-Ninja-Guru-Wizard Software Engineer? This post is for you!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/570/1*O29Zlbjw8sH77FD2kaCGtw.jpeg" /></figure><h3>The Market Has Changed And So Should You</h3><p>The market of employers and employees has changed so much in the past decade or so. Not so long ago, people would stay at their company for at least a decade, sometimes even longer.</p><p>Nowadays, according to a survey performed by <a href="http://www.careerbuilder.com/share/aboutus/pressreleasesdetail.aspx?sd=5%2F15%2F2014&amp;id=pr824&amp;ed=12%2F31%2F2014">Careerbuilder</a> in 2014, <strong>by the age of 35, 25% of workers have held five or more jobs. For workers ages 55 and older, 20% have held ten jobs or more.</strong></p><blockquote>“Information Technology, an industry with a notable talent shortage and highly competitive recruitment tactics, has the largest percentage of employers who expect workers to job-hop.” — <a href="http://www.careerbuilder.com/share/aboutus/pressreleasesdetail.aspx?sd=5%2F15%2F2014&amp;id=pr824&amp;ed=12%2F31%2F2014">Careerbuilder</a></blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FhER0Qp6QJNU%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DhER0Qp6QJNU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FhER0Qp6QJNU%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4009303810580fb129372e12c32200fd/href">https://medium.com/media/4009303810580fb129372e12c32200fd/href</a></iframe><h3><strong>So What Does This All Mean?</strong></h3><p>It means that not only do you need to work harder to keep your talent from leaving your company, you also have to work harder to get it in the first place and you should start with your hiring process. Ready? Let’s begin!</p><h3>We’re All Story Tellers</h3><p>The best way to attract the right people for the right job is to tell them your story, the better the story is, the more attraction you’ll get — start with how you tell the world about your new job openings, it can be a careers page, a post on social media, or even a casual chat with people who might be looking and/or know people who are.</p><p>If you really want a leg up on top talent, you can open your position on <a href="https://www.workey.co/">Workey</a>, which uses AI to match your open positions with ideal candidates who remain completely anonymous until they choose to reveal themselves to you. You’re only presented with relevant candidates to save you time and effort.</p><p>The first and probably the most crucial step is to tell your story as unforgettably as possible, remember — <strong>you’re not just offering a job but an opportunity to join the best Startup company in the business, plus he/she will be working with you (yay)!</strong></p><p>Don’t believe that? You might need to reconsider your own status or perhaps you’re just not the right person to do this and that’s okay.</p><p><strong>Don’t lie. </strong>Good people will smell your lies from far away and won’t even bother coming for an interview. You expect interviewees to be honest with you about themselves so return the favor.</p><p><strong>Focus on the good.</strong> Is the office located in the best spot in town? Mention it! Are you using cutting-edge technologies? Explain how you’re using them. Got well-known talent on your team? Talk about them and their contributions, better yet — introduce them and have them be part of your hiring process.</p><p><strong>Remember, you might be thinking that you’re interviewing candidates but they’re also interviewing you and your company</strong> — and this doesn’t seem to be changing any time soon so you better adjust and go the extra mile to bring real talent to your company or suffer the fate of mediocrity.</p><h3>It’s Game On</h3><p>You’re now getting some attention, people start applying to the job and you need to start filtering the good from the bad and interviewing. Here’s my idea of an ideal quick, yet efficient hiring process:</p><h3>Step #1 — Phone Interview</h3><p>A phone interview is the very first time you talk to the person who applied for the job, this is a great chance for you to explain more about your company, the product, and what you’re looking for in your potential future employee.</p><p>This should be a casual short call (up to 30 minutes or so) where both sides get a chance to introduce themselves and based on that, decide whether or not there is a future for this collaboration.</p><h3>Step #2 — Introductory Interview</h3><p>Your new candidate<strong> </strong>just arrived for the first on-site interview — be friendly, show them around the office and start by talking about the company, the products, solutions, challenges, milestones achieved, anything you have to make a first impression that will end up with a big huge <strong>WOW</strong>!</p><p>I truly believe that the first interview is all about the introduction between the two sides and to see if there’s any chemistry. If not, there is no point in moving to the next level which is more technical. I know that you want to but try to avoid any technical questions during the first interview — there will be time for that later on the process.</p><p>Some companies start their hiring process with a technical task. I believe this is a mistake because it’s time consuming (for both sides) before even knowing if they even like your company’s mission, work, and general vibe.</p><p><strong>Your candidate doesn’t know anything about you or the opportunity that you’re offering, therefore they might not be willing to take the time and effort before at least an introductory meeting.</strong></p><p>Now that you’ve set the ground work and gave your best story about your company and the opportunity you’re offering — get personal, ask about their hobbies, ask about their likes and dislikes. Of course, it goes without saying to still keep it professional. At the end of the day, you want to see if you’d get along professionally because at the end of the day people who get along work better together.</p><h3>Step #3 — Technical Interview</h3><p>After you’ve met your candidate and you hit it off, now it’s time to get technical — some prefer doing a Q&amp;A session, some prefer giving a task that can be done on-site or at home.</p><p>I personally think you’ll get the best results out of a task that can be done at home with no time limit. The reason for that is because that when there is no time limit — there are no excuses for mistakes or anything other than super efficient and clean code. <strong>Also this is an excellent chance for your candidate to impress you with his or her coding skills.</strong></p><p>In case you decide to give a technical task — <strong>don’t make it long and exhausting,</strong> it should be something that takes up to one or two hours to finish, try to make it both challenging and fun like building a game app or something cool.</p><p>The reason that I like giving technical tasks is because you can learn a lot from it. One technique I recommend is to review the task together, ask questions about what libraries/frameworks were chosen, data structure, solution and more — <strong>you’ll be surprised how much you can learn about someone from a simple technical task.</strong></p><h3>Step #4 — A Second Technical Interview</h3><p>Just in case you weren’t quite satisfied with the results so far or perhaps you are missing some information to really decide on the candidate, it might be a good idea to ask someone from your team to interview your candidate as well — this will provide you with two great things.</p><p>The first is additional technical feedback and the second which is even more important, feedback about the fit from someone that will actually have to work with this person on a daily basis.</p><h3>Step #5 — HR Interview</h3><p>If you got to this point, it means that you found real talent to join your team — that’s awesome! Now it’s time to speed things up, your rockstar candidate is probably meeting with other companies and might have already gotten an offer or two so time is against you.</p><p><strong>Ask your HR manager to do the next interview, this will get you even more feedback about your candidate’s personality, career goals and maybe craziness, I’m always amazed at how good HR managers are at bringing hidden insights to the surface.</strong></p><p>Do everything you can to act as quickly as possible, I once waited a day longer than I should have and ended up losing an excellent software engineer who in the meantime signed with another company. Needless to say, time is crucial here.</p><p>A very common mistake is not being in touch constantly with your candidate or even worse — a late response might seem like you’re disorganized or not really interested.</p><p>Make sure to let people know what’s going on and yeah — always respond, especially if the answer is no. <strong>People have spent time and effort to come for an interview, you owe them at least an answer.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*NQRRsvupkk7Aed5JU51q7Q.jpeg" /></figure><h3>Step #6 — Make It Official</h3><p>Boom! The stars have aligned perfectly and everything worked out, you’ve found your next teammate and he or she has found you! This is the time to make it official, send out your offer, expect some back and forth but do everything within your power to make this step way less awkward than it should be and as fast as possible.</p><p>I’ve witnessed and heard about so many times that things went south pretty fast in this step and in most cases, for no good reason. Do everything you can to close the deal, the sooner the better.</p><h3>Bonus Step — Onboarding</h3><p>Some people think that the hiring process has ended once the new employee had signed the contract, but that’s not necessarily true. In most cases, they will be joining the company within 30 days or so.</p><p>Stay in touch, ask what you can do before their first day, invite them to important meetings or a fun night out with the team — make them feel they are already part of the family.</p><p>This is something we try to do here at Workey and it’s gone very well. :)</p><p>I joined a company trip two weeks before I started working for the company and it was awesome because it gave me a chance to meet my new co-workers in an unofficial scenario which then made the process a whole lot easy and nicer.</p><p>In addition, keep in mind that onboarding a new member of your team is an on-going process, make sure they have everything they need on their first day, schedule in advance time slots on your calendar available for one-on-one sessions, this will help them know that you’re doing everything you can to get them whatever they need to do their job well done.</p><p><strong>That’s all I have for you this time!<br></strong>Any questions or suggestions? Please ping me or comment below.<br>In case you liked this post, please recommend it and share it to your friends!</p><p><strong>You might also enjoy one of my last posts:<br></strong>“<a href="https://theblog.workey.co/stop-being-afraid-of-git-and-start-using-it-the-right-way-e784da034ba8">Stop Being Afraid of Git and Start Using It The Right Way</a>”<br>“<a href="https://theblog.workey.co/6-reasons-why-react-is-todays-best-way-to-build-your-web-apps-9e7c6013514">6 Reasons Why React Is Today’s Best Way to Build Your Web Apps</a>”</p><p><em>Nir Peled is a Senior Software Engineer @ </em><a href="https://www.workey.co/"><em>Workey</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/64/1*KFAkQwdZu7xYSd_SjAddKA.png" /></figure><p><a href="https://www.workey.co/"><em>Workey</em></a><em> is the revolutionary AI helping to guide the careers of a connected generation. We use real time data to uncover new paths and opportunities to develop your career to its full potential. Anonymously.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e14237e73bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>