Have you thought about how energy, food, security and the internet comes about, and how the infrastructure that produces them is kept safe? \n\nThe world currently uses large offshore vessels because of decades-long investments in ensuring its safety and efficiency at oil and gas platforms

BeeX

beex

Despite the somewhat pretentious title, the purpose of this article is not to present a success story or give some “hot tips” based on useless platitudes and truisms. I just want to share a few stories about the company I've spent almost my entire professional career with. About how this service came to life in a distant and cold city called Yakutsk, I share my perspective on inDrive from an engineer's point of view. Hi everyone! My name is Michil Androsov, and I've been with for 10 years now. I joined the company when there were three people on the development team, and left it as CTO with 500 people under my command. Over the years, the company has grown from a local startup to a unicorn company with hundreds of invested by the world's top funds. inDrive millions of dollars (former inDriver, short for “ dependent s“), is a ride-hailing service from (the capital of ) with one big difference from all the others: the fare for the trip is set by the passengers themselves. inDrive In Driver Yakutsk Sakha Republic Unlike its competitors, inDrive’s pricing model involves no complicated algorithms based on hundreds of criteria. The entire system is as transparent as it can be, with only two parties involved in the process: the driver and the passenger who negotiate the fares amongst themselves and agree on a price that works for both parties. This is a self-balancing system. Sakha Republic, also known as Yakutia, is a republic located in the Far East of the Russian Federation. Mostly inhabited by the local indigenous people, the Yakuts, but quite multiculturalized. The republic has a reputation for an extreme and severe climate. The Yakutsk vibe Here is why the service emerged in Yakutsk, of all places. In my book, two reasons explain this: With temperatures outside dipping down to 50 degrees Celsius below zero, rather than go for a walk in the park or take a nature hike, people tend to stay at home. They have to find ways to keep themselves entertained and, more often than not, they spend their time in front of a computer. Combined with the top schools that lay a special focus on physics and math, of which there are many in the area, there is a chance that a lot of these kids will become programmers. At least, that's how I explain this to myself. Cold climate. Because of this, the Internet was very expensive and slow. The Internet worked with radio relay technology. And you had to pay for every megabyte. A couple of downloaded movies from the internet could cost a worker's salary. So employees of Internet service providers would download something from the Big Internet and put it on the . I remember some of the guys who even engaged in satellite fishing. Isolation from the mainland. intranet It’s due to these two factors that Yakutsk ended up having its own"Internet", and with it the Internet portal (currently down) - local web portals like yahoo or dmoz, craigslist, napster, image photo board, news, forums all in one. It was a local variety of Alphabet, and all of the few IT specialists in Yakutsk wanted to get a job there. The company that owned the portal was called Sinet(short for Sakha Internet) — a company within which inDrive was soon established. Ykt.ru It's worth pointing out here that in addition to Sinet, there was a large game-development company called in Yakutsk, and it also acted as a magnet for local IT guys. That company started with two brothers from the small northern village of Khonuu who borrowed some money from their parents to start developing their first indie game. As things stand today, inDrive and Mytona have "moved" out of Russia. Mytona Independent Drivers As far as cab services were concerned, it was difficult and expensive to get a ride in Yakutsk before inDrive made its appearance on the scene. Things worked the old-fashioned way, and you had to call first and book a vehicle via the dispatcher and then wait a long time for the driver to arrive. To make matters worse, your call might be forgotten and then the wait for the car exceeded all possible limits. A separate pain point was the New Year holidays(major holiday in the country, two weeks of partying, no one works), when cab services upped their prices multiple times over, thus pushing the passengers over the edge. In the winter of 2012, several smart guys created a group called "Community of Independent Drivers of Yakutsk". In it, you could indicate that you needed to go from point A to point B and leave your phone number. Then a caring driver who just happened to be headed that way might call you to arrange a ride. At the end of the trip, the passenger had to leave money with the driver to cover the cost of gas. Vkontakte Sure thing, very soon, instead of gas price compensation, people started paying for the ride. Over a short time, the group gained massive popularity and began to gradually cut out traditional cab services. inDrive. Early days At that time, Arsen Tomsky, the director of Sinet, saw this group as a promising idea for expanding his business and decided to buy it out. Essentially, that point marks the beginning of inDrive's existence. In October 2013, I joined the company as the third developer when the startup was in its fifth month of operations. At that time, the app's Android version was already available, and our guys were looking for an iOS developer. Before joining the company, I worked for a year in a small startup studio developing interactive books on iPad for kids, first in our native language. Right at that point, I was thinking of changing jobs. I had one big advantage going for me - my MacBook, which was a rarity in Yakutsk at the time. I thought this was my chance to try and get a job at Sinet. I had no experience in iOS development, but somehow (most likely due to a lack of suitable candidates) I succeeded in landing a job at my dream company. iOS development was native: I coded in Objective-C. Now the situation hasn't changed much, the only difference being that is now commonly used instead of Objective-C. While Android was coded in Java, the backend was written in PHP. Many of the things laid down back then remain at the core of the inDrive codebase today. Swift The core iOS development team at that time was just me. In 2015, a second person came on board to join me. Once a third one was hired in 2016, we started growing very fast. There were no cross-platform teams back then— just iOS-, Android-, backend development teams, and QA testers. It makes me wonder how the inDrive driver accepted ride requests in those days. It was called a : a passenger places an order, nearby drivers simultaneously see it on their request list, and those who like the offer click on it. The peculiar thing back then was that we just connected a driver and a passenger via the cellular communication network! Sometimes, multiple drivers would call in for the same ride request at the same time. After the call, we would show the passenger a list of all the drivers who had called so they could pick the most suitable one. The whole set-up seemed to operate based on the principle of "the order goes to whoever calls first". Because of this, there were customer support complaints from drivers reporting that they didn’t have enough time to pick up the order. call-based arrangement For a long time, there was a legend that iOS had a much higher chance of securing an order than Android. There was some truth to this, as the interface did indeed run faster on iOS. For a long time, we did not introduce"call-less" order acceptance processes, which were more commonly used by other ride-hailing services, thinking that passengers would have more trust in the driver if they had time to talk to each other on the phone before the ride. Obviously, such a strategy had its limitations, and quite serious ones at that. Also, the first version of the app had an interesting tab called "Available Drivers". By clicking on it, you could go to the map, find an available driver, call them personally, and arrange a ride. Understandably, back then there were no encrypted connections yet. In addition, there was a third way to find a driver: after creating a ride request (order), I could find a suitable driver on the map and send them my offer via a personal message. This was called "Personalized Order”. Nowadays, the guys sometimes miss the days when everything was as easy, fast, and as fun as possible. I didn't know what repositories were, and after the release of each version, I archived the project folder and saved it on my hard drive (hundreds of archives are still stored there) and Google Drive. In the early years, our project in Xcode was called , whereas our product tasks were written down directly on the whiteboard. startPage I wasn’t yet familiar with the basic programming patterns and architectures of iOS development. The end result was a stack of Massive View Controllers and storyboards with dozens of screens. This was genuine StackOverflow programming. Expanding beyond Yakutsk Gradually, our startup team began to grow. New people joined, and the first simple processes emerged. In 2014, the company already had 10 staff members. It was at that time that we flew over to Novosibirsk to participate in a conference. It was the three of us, the whole development team. This was another significant milestone in the company's history, as in Sakha Republic you feel isolated from the big wide world outside. Trips like this were a major event for us. At the end of 2013, we were joined by Sasha Pavlov, the creator of the VKontakte group, which was bought out by Arsen Tomsky. With him on board, we began our first attempts to launch in other cities. One day, Sasha flew to Sakhalin to talk things over with drivers. He printed out some promotional pamphlets and started handing them out in the mall parking lot, but was chased away by security. Eventually, though, we had a successful launch in Sakhalin and it immediately showed excellent growth. Then we started launching in other northern and eastern Russian cities: Irkutsk, Tomsk, etc. These areas resemble Yakutsk in that they have similar severe climatic conditions, and there are no other major apps there. In those cities, the app started showing growth almost instantly. We used to sit in our little office and daydream, "Just imagine, one day we will be earning more than ." We had a laugh, but in reality that moment came very quickly. Ykt.ru Our CEO always wanted a bigger story, and not related to Yakutsk. He's an entrepreneur to the core, and he always seeks new challenges. It seemed obvious and logical to us, so no one questioned why we were doing what we were doing. It was always cool to figure out how much we, some guys from Yakutsk, could compete with the big companies. At that time, our main competitors were and . We weren’t thinking about yet. But soon we had to give the situation plenty of thought, but I'll tell you more about it in my next posts if you're interested. Taxi Maxim Yandex Taxi Uber This is my first experience writing an article and I want to write more about the history of inDrive’s evolution, how I became CTO, and what technical and non-technical challenges we faced and had to overcome. So it would be awesome to get your feedback on what could be improved upon here and what you'd be interested in reading about in future posts. P.S. Share them in the comments! P.P.S. The milestones of Sinet’s and inDrive’s evolution are described in more detail in the book by the company's CEO: “inDriver: From Yakutsk to Silicon Valley”.

Building a Unicorn: My Decade-Long Career With inDrive

একটি ইউনিকর্ন তৈরি করা: ইনড্রাইভের সাথে আমার দশক-দীর্ঘ ক্যারিয়ার

Ein Einhorn bauen: Meine jahrzehntelange Karriere bei inDrive

Construyendo un unicornio: mi carrera de una década con inDrive

Construire une licorne : ma carrière d'une décennie avec inDrive

एक यूनिकॉर्न का निर्माण: इनड्राइव के साथ मेरा एक दशक लंबा करियर

ユニコーンの構築: inDrive での私の 10 年にわたるキャリア

유니콘 만들기: inDrive를 사용한 나의 10년 경력

Construindo um unicórnio: minha carreira de uma década com inDrive

Создание единорога: моя десятилетняя карьера в inDrive

Bir Tekboynuz Yaratmak: inDrive'daki On Yıllık Kariyerim

Xây dựng Kỳ lân: Sự nghiệp kéo dài hàng thập kỷ của tôi với inDrive

打造独角兽：我与 inDrive 长达十年的职业生涯

Barchester Towers by Anthony Trollope is part of the HackerNoon Books Series. You can jump to any chapter in this book . Slope versus Harding here Slope versus Harding Two or three days after the party, Mr. Harding received a note begging him to call on Mr. Slope, at the palace, at an early hour on the following morning. There was nothing uncivil in the communication, and yet the tone of it was thoroughly displeasing. It was as follows: My dear Mr. Harding, Will you favour me by calling on me at the palace to-morrow morning at 9:30 a.m. The bishop wishes me to speak to you touching the hospital. I hope you will excuse my naming so early an hour. I do so as my time is greatly occupied. If, however, it is positively inconvenient to you, I will change it to 10. You will, perhaps, be kind enough to let me have a note in reply. Believe me to be, My dear Mr. Harding, Your assured friend, Obh. Slope The Palace, Monday morning, 20th August, 185–– Mr. Harding neither could nor would believe anything of the sort, and he thought, moreover, that Mr. Slope was rather impertinent to call himself by such a name. His assured friend, indeed! How many assured friends generally fall to the lot of a man in this world? And by what process are they made? And how much of such process had taken place as yet between Mr. Harding and Mr. Slope? Mr. Harding could not help asking himself these questions as he read and re-read the note before him. He answered it, however, as follows: Dear Sir, I will call at the palace to-morrow at 9:30 a.m. as you desire. Truly yours, S. Harding High Street, Barchester, Monday And on the following morning, punctually at half-past nine, he knocked at the palace door and asked for Mr. Slope. The bishop had one small room allotted to him on the ground-floor, and Mr. Slope had another. Into this latter Mr. Harding was shown and asked to sit down. Mr. Slope was not yet there. The ex-warden stood up at the window looking into the garden, and could not help thinking how very short a time had passed since the whole of that house had been open to him, as though he had been a child of the family, born and bred in it. He remembered how the old servants used to smile as they opened the door to him; how the familiar butler would say, when he had been absent a few hours longer than usual, "A sight of you, Mr. Harding, is good for sore eyes;" how the fussy housekeeper would swear that he couldn't have dined, or couldn't have breakfasted, or couldn't have lunched. And then, above all, he remembered the pleasant gleam of inward satisfaction which always spread itself over the old bishop's face whenever his friend entered his room. A tear came into each eye as he reflected that all this was gone. What use would the hospital be to him now? He was alone in the world, and getting old; he would soon, very soon have to go and leave it all, as his dear old friend had gone; go, and leave the hospital, and his accustomed place in the cathedral, and his haunts and pleasures, to younger and perhaps wiser men. That chanting of his! Perhaps, in truth, the time for it was gone by. He felt as though the world were sinking from his feet; as though this, this was the time for him to turn with confidence to those hopes which he had preached with confidence to others. "What," said he to himself, "can a man's religion be worth if it does not support him against the natural melancholy of declining years?" And as he looked out through his dimmed eyes into the bright parterres of the bishop's garden, he felt that he had the support which he wanted. Nevertheless, he did not like to be thus kept waiting. If Mr. Slope did not really wish to see him at half-past nine o'clock, why force him to come away from his lodgings with his breakfast in his throat? To tell the truth, it was policy on the part of Mr. Slope. Mr. Slope had made up his mind that Mr. Harding should either accept the hospital with abject submission, or else refuse it altogether, and had calculated that he would probably be more quick to do the latter, if he could be got to enter upon the subject in an ill-humour. Perhaps Mr. Slope was not altogether wrong in his calculation. It was nearly ten when Mr. Slope hurried into the room and, muttering something about the bishop and diocesan duties, shook Mr. Harding's hand ruthlessly and begged him to be seated. Now the air of superiority which this man assumed did go against the grain with Mr. Harding, and yet he did not know how to resent it. The whole tendency of his mind and disposition was opposed to any contra-assumption of grandeur on his own part, and he hadn't the worldly spirit or quickness necessary to put down insolent pretensions by downright and open rebuke, as the archdeacon would have done. There was nothing for Mr. Harding but to submit, and he accordingly did so. "About the hospital, Mr. Harding?" began Mr. Slope, speaking of it as the head of a college at Cambridge might speak of some sizarship which had to be disposed of. Mr. Harding crossed one leg over another, and then one hand over the other on the top of them, and looked Mr. Slope in the face; but he said nothing. "It's to be filled up again," said Mr. Slope. Mr. Harding said that he had understood so. "Of course, you know, the income will be very much reduced," continued Mr. Slope. "The bishop wished to be liberal, and he therefore told the government that he thought it ought to be put at not less than £450. I think on the whole the bishop was right, for though the services required will not be of a very onerous nature, they will be more so than they were before. And it is, perhaps, well that the clergy immediately attached to the cathedral town should be made as comfortable as the extent of the ecclesiastical means at our disposal will allow. Those are the bishop's ideas, and I must say mine also." Mr. Harding sat rubbing one hand on the other, but said not a word. "So much for the income, Mr. Harding. The house will, of course, remain to the warden, as before. It should, however, I think, be stipulated that he should paint inside every seven years, and outside every three years, and be subject to dilapidations, in the event of vacating, either by death or otherwise. But this is a matter on which the bishop must yet be consulted." Mr. Harding still rubbed his hands and still sat silent, gazing up into Mr. Slope's unprepossessing face. "Then, as to the duties," continued he, "I believe, if I am rightly informed, there can hardly be said to have been any duties hitherto," and he gave a sort of half-laugh, as though to pass off the accusation in the guise of a pleasantry. Mr. Harding thought of the happy, easy years he had passed in his old home; of the worn-out, aged men whom he had succoured; of his good intentions; and of his work, which had certainly been of the lightest. He thought of these things, doubting for a moment whether he did or did not deserve the sarcasm. He gave his enemy the benefit of the doubt, and did not rebuke him. He merely observed, very tranquilly, and perhaps with too much humility, that the duties of the situation, such as they were, had, he believed, been done to the satisfaction of the late bishop. Mr. Slope again smiled, and this time the smile was intended to operate against the memory of the late bishop rather than against the energy of the ex-warden; so it was understood by Mr. Harding. The colour rose to his cheeks, and he began to feel very angry. "You must be aware, Mr. Harding, that things are a good deal changed in Barchester," said Mr. Slope. Mr. Harding said that he was aware of it. "And not only in Barchester, Mr. Harding, but in the world at large. It is not only in Barchester that a new man is carrying out new measures and casting away the useless rubbish of past centuries. The same thing is going on throughout the country. Work is now required from every man who receives wages, and they who have to superintend the doing of work, and the paying of wages, are bound to see that this rule is carried out. New men, Mr. Harding, are now needed and are now forthcoming in the church, as well as in other professions." All this was wormwood to our old friend. He had never rated very high his own abilities or activity, but all the feelings of his heart were with the old clergy, and any antipathies of which his heart was susceptible were directed against those new, busy, uncharitable, self-lauding men, of whom Mr. Slope was so good an example. "Perhaps," said he, "the bishop will prefer a new man at the hospital?" "By no means," said Mr. Slope. "The bishop is very anxious that you should accept the appointment, but he wishes you should understand beforehand what will be the required duties. In the first place, a Sabbath-day school will be attached to the hospital." "What! For the old men?" asked Mr. Harding. "No, Mr. Harding, not for the old men, but for the benefit of the children of such of the poor of Barchester as it may suit. The bishop will expect that you shall attend this school, and that the teachers shall be under your inspection and care." Mr. Harding slipped his topmost hand off the other and began to rub the calf of the leg which was supported. "As to the old men," continued Mr. Slope, "and the old women who are to form a part of the hospital, the bishop is desirous that you shall have morning and evening service on the premises every Sabbath, and one weekday service; that you shall preach to them once at least on Sundays; and that the whole hospital be always collected for morning and evening prayer. The bishop thinks that this will render it unnecessary that any separate seats in the cathedral should be reserved for the hospital inmates." Mr. Slope paused, but Mr. Harding still said nothing. "Indeed, it would be difficult to find seats for the women; on the whole, Mr. Harding, I may as well say at once, that for people of that class the cathedral service does not appear to me the most useful—even if it be so for any class of people." "We will not discuss that, if you please," said Mr. Harding. "I am not desirous of doing so; at least, not at the present moment. I hope, however, you fully understand the bishop's wishes about the new establishment of the hospital; and if, as I do not doubt, I shall receive from you an assurance that you accord with his lordship's views, it will give me very great pleasure to be the bearer from his lordship to you of the presentation to the appointment." "But if I disagree with his lordship's views?" asked Mr. Harding. "But I hope you do not," said Mr. Slope. "But if I do?" again asked the other. "If such unfortunately should be the case, which I can hardly conceive, I presume your own feelings will dictate to you the propriety of declining the appointment." "But if I accept the appointment and yet disagree with the bishop, what then?" This question rather bothered Mr. Slope. It was true that he had talked the matter over with the bishop and had received a sort of authority for suggesting to Mr. Harding the propriety of a Sunday school and certain hospital services, but he had no authority for saying that these propositions were to be made peremptory conditions attached to the appointment. The bishop's idea had been that Mr. Harding would of course consent and that the school would become, like the rest of those new establishments in the city, under the control of his wife and his chaplain. Mr. Slope's idea had been more correct. He intended that Mr. Harding should refuse the situation, and that an ally of his own should get it, but he had not conceived the possibility of Mr. Harding openly accepting the appointment and as openly rejecting the conditions. "It is not, I presume, probable," said he, "that you will accept from the hands of the bishop a piece of preferment with a fixed predetermination to disacknowledge the duties attached to it." "If I become warden," said Mr. Harding, "and neglect my duty, the bishop has means by which he can remedy the grievance." "I hardly expected such an argument from you, or I may say the suggestion of such a line of conduct," said Mr. Slope with a great look of injured virtue. "Nor did I expect such a proposition." "I shall be glad at any rate to know what answer I am to make to his lordship," said Mr. Slope. "I will take an early opportunity of seeing his lordship myself," said Mr. Harding. "Such an arrangement," said Mr. Slope, "will hardly give his lordship satisfaction. Indeed, it is impossible that the bishop should himself see every clergyman in the diocese on every subject of patronage that may arise. The bishop, I believe, did see you on the matter, and I really cannot see why he should be troubled to do so again." "Do you know, Mr. Slope, how long I have been officiating as a clergyman in this city?" Mr. Slope's wish was now nearly fulfilled. Mr. Harding had become angry, and it was probable that he might commit himself. "I really do not see what that has to do with the question. You cannot think the bishop would be justified in allowing you to regard as a sinecure a situation that requires an active man, merely because you have been employed for many years in the cathedral." "But it might induce the bishop to see me, if I asked him to do so. I shall consult my friends in this matter, Mr. Slope; but I mean to be guilty of no subterfuge—you may tell the bishop that as I altogether disagree with his views about the hospital, I shall decline the situation if I find that any such conditions are attached to it as those you have suggested;" and so saying, Mr. Harding took his hat and went his way. Mr. Slope was contented. He considered himself at liberty to accept Mr. Harding's last speech as an absolute refusal of the appointment. At least, he so represented it to the bishop and to Mrs. Proudie. "That is very surprising," said the bishop. "Not at all," said Mrs. Proudie; "you little know how determined the whole set of them are to withstand your authority." "But Mr. Harding was so anxious for it," said the bishop. "Yes," said Mr. Slope, "if he can hold it without the slightest acknowledgement of your lordship's jurisdiction." "That is out of the question," said the bishop. "I should imagine it to be quite so," said the chaplain. "Indeed, I should think so," said the lady. "I really am sorry for it," said the bishop. "I don't know that there is much cause for sorrow," said the lady. "Mr. Quiverful is a much more deserving man, more in need of it, and one who will make himself much more useful in the close neighbourhood of the palace." "I suppose I had better see Quiverful?" said the chaplain. "I suppose you had," said the bishop. About HackerNoon Book Series: We bring you the most important technical, scientific, and insightful public domain books. This book is part of the public domain. Anthony Trollope (2002). Barchester Towers. Urbana, Illinois: Project Gutenberg. Retrieved October 2022 https://www.gutenberg.org/cache/epub/3409/pg3409-images.html This eBook is for the use of anyone anywhere at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this eBook or online at , located at . www.gutenberg.org https://www.gutenberg.org/policy/license.html

Slope versus Harding

229 Stories To Learn About Economics

Moby-Dick; or The Whale: Chapter 32 - Cetology

When it comes time for an employee to leave your organization, you want it to be on friendly terms. But there are definitely limits to how friendly you want folks to be after they leave. Especially when it comes to accessing materials from their old position for their new endeavors. In a recent bizarre case, it was reported that a former acting has pleaded guilty to stealing government software and data for use in his own product. Department of Homeland Security Inspector General According to reports from the Record, Charles K. Edwards allegedly stole proprietary software and personally identifiable information (PII) belonging to federal employees from both DHS and the U.S. Postal Service where he had previously served in their Office of Inspector General division. He apparently used these ill-gotten resources to sell a similar version of his former office’s case management software to other federal agencies. Interestingly, besides the fact that the person who was supposed to be in charge of investigating misdeeds themselves being the thief, was the reports that he had inside help. He is alleged to have worked with a former employee of his who was still at the DHS at the time, who helped him not only steal the software and databases, but set him up at home to work with it as well. While there are no details in the Department of Justice explaining how he got caught, it is possible that he might have set off some spidey senses when trying to sell other federal agencies a version of the software. A string of other convictions in his not-so-recent past may have led folks to believe that he may have been up to no good, leading them to alert authorities. release Employees Who Take More Than Just Good Memories However, he was found out and his case provides a good reminder of the need to ensure that soon-to-be-ex-employees do not leave with more than they are supposed to. As well as another reminder that those still working at your organization do not aid in leaking valuable information to their former colleagues. Data loss by former employees is exceedingly common. A report from 2019 showed that to taking materials from their previous employers. 72% openly admitted In most cases, these incidents likely included lower-risk data like contacts or other bits that were probably not that harmful to their organization. These folks know that they should not be taking company property with them, but they do not intend to use them for harm or out-of-bounds advantages for their next gig. But in other cases where critical data like intellectual property, trade secrets, customer lists, and plenty of other valuable items like source code are taken, catching the perpetrators is essential. 3 Tips and Tools for Mitigation of Insider Threat Risks Here below are a couple of tips to keep in mind when thinking about how to . minimize your risk from insider threats 1. Monitor for Data Downloads or Transfers An employee knows that they are going to quit long before your security team does. This gives them plenty of time to start storing away bits and bytes of information that they may want to take with them on their way out. While an employee can become a malicious insider at any time, they are most likely to act in devious ways in the lead up to their departure. This is because they have already made their decision to leave so feelings of loyalty are low and incentives to take something of value is highest. It is at this time that they may decide to start downloading data or moving it out to different cloud services where they have personal accounts that they can later access after they leave. Organizations should always have monitoring tools that look for and log downloads of data or other large transfers. This should be running regularly in the background, flagging when valuable data is being exported. That is just good security practices. But you especially need to put focus on those employees who have already given notice. Be sure to keep an extra set of eyes on these individuals’ activity before and after they leave to make sure that there is no untoward activity afoot. 2. Monitor Employee Communications As we saw in the case with Edwards, he had help from the inside. It has become increasingly common for hackers like ransomware crews to reach out to employees to “entice” them into helping with their attacks, so the concept of an insider being used by external baddies is far from something new. But it is not uncommon for employees to keep in touch with their former colleagues in activities that might otherwise pass as normal. Those former employees may try to leverage their relationships for personal gain. Monitoring employee communications, including email, chats, and others can be a good deterrent since it can raise the risks of getting caught. It is key though that you remind people that they are being monitored for both transparency and deterrence reasons. We need to consider here that if the bad actors here are smart, then they will avoid using any company resources, like Slack or their email, that can be monitored. That is if they are smart. Many more are not. It is surprising how often people will use channels that they should otherwise know are monitored for sending messages that they should not be. In monitoring the communications technologies that your organization owns, you are potentially making it more difficult for the insider to operate by denying them channels. In addition, you are increasing your probability of catching them in the act. 3. Monitor Behavior for Abnormalities Over time, we become creatures of habit. We use the same tools, access the same kinds of folders and files, etc. In short and with some variation, we become fairly predictable within the scope of our work and create a baseline of behavior. If we deviate from this baseline, it should at the very least raise a red flag or two. Monitoring employees for taking actions that fall outside the boundaries of their normal activities is generally considered to be best practices. The most common example here is if they are accessing resources that they normally do not, but of course, file transfers and similar out-of-character activities that do not match their user’s standard behavior may also serve to draw attention. If your organization is practicing good segmentation between resources and responsibilities, then no one person should be able to come away with too big of a data haul based on their own domain. In this case, they will either have to recruit more co-conspirators or step outside of their normal habits to get ahold of larger amounts of data. If you are monitoring with User Behavior Analytics (UVA) tools, then we stand a better chance of catching them at this point of departure. What’s a Little Data Sharing Between Old Friends? Working with colleagues over time builds bonds of trust. Or at least it should if your culture was a good one. And it makes us want to be helpful to the people that we like and work with. The challenge for organizations is to clarify where the lines lie when it comes to helping out former colleagues. Give a reference or return a personal item that they left in the office? Sure, help a pal out. Pass along proprietary information or help them to set up their new business at your organization’s expense? That is a line too far. This is never a fun conversation but it is a necessary one. The past few years of remote work have meant a lot of career shifts for people leaving jobs, going out on their own, moving to new companies. Building a real esprit de corps within organizations is tough when folks do not show up to the office on a regular basis. Moreover, we are probably now more entrepreneurial than before. Having experienced how our own job situations are more than a little unstable, we are all on the lookout for opportunities. Even if we are just keeping them in our back pockets. Saying no to helping out a friend who has left the organization and might give you a hand down the line can be hard. Some folks might edge up to the gray, fuzzy line. Or even cross it. Hopefully, well-defined policies and training can clarify what is and is not ok, and when backed up with monitoring, organizations can significantly reduce their risk.

How to Reduce the Risk of Former Employees Coordinating with Insider Threats

Ex-Google Tech Lead explains why programming is so hard. Join me in my new coding interview training program: http://techinterviewpro.com/ 👨‍💻 Join ex-Google/ex-Facebook engineers for my coding interview training: http://techinterviewpro.com/ 👨‍💻 Videos of 100+ programming interview problems explained: https://coderpro.com/ 👨‍💻 Sign up for my FREE daily coding interview practice: http://dailyinterviewpro.com/ 🎬 Learn how I built a $1,000,000+ business on YouTube: http://youtubebackstage.com/ 📈 Get 2 FREE stocks on WeBull (valued up to $1,400): https://act.webull.com/k/S4oOH2yGOtHk... 🛒 My computer/camera gear: http://amazon.com/shop/techlead 💳 The TechLead "ultra-thin" wallet https://amzn.to/2WNhqEP ☕ The TechLead custom coffee-maker: https://amzn.to/3dxwrzr 💬 Join my Discord: https://discord.gg/pFUBUtE Party up: http://instagram.com/techleadhd/ / http://twitter.com/techleadhd https://www.linkedin.com/in/patrickshyu/ Disclosure: Some links are affiliate links to products. I may receive a small commission for purchases made through these links. #techlead Video Transcript: Note: This transcript is auto generated by YouTube and may not be entirely accurate. 00:00 hey tech late here and welcome back to 00:01 another episode of the tech lead and I 00:04 know what you may be thinking this must 00:05 be lemonade it's not actually that's too 00:08 expensive I decided to recycle for the 00:11 meanwhile oh that's warm so today I 00:16 wanted to talk about why programming is 00:18 so hard and the fact is it's actually 00:21 not that hard but there are a certain 00:23 number of roadblocks and if you don't 00:25 clear these out of the way or if you're 00:26 not mentally prepared for these then 00:28 it's going to really mess you up and you 00:30 may find yourself stuck on some of these 00:31 you may even be banging your head 00:33 against the wrong wall when you realize 00:35 you're not even going in the right 00:36 direction here I know that there have 00:37 been some people who say maybe you have 00:40 to be born to code kind of like how you 00:42 may need to be born to be a really 00:44 gifted musical composer and I can tell 00:46 you that at least for myself I learned 00:49 to code but it was a real struggle even 00:51 for me I started at a very young age and 00:53 say sixth grade but even as I was 00:55 getting through learning pointers I 00:57 remember crying during those first few 00:59 lessons because it was just so difficult 01:01 I know this though that those who 01:03 persisted were able to get through it 01:05 and there are a number of things to 01:06 watch out for on your journey 01:08 into software engineering if that's what 01:10 you're going for here now before we get 01:12 started here I do want to mention that 01:13 this video is sponsored by myself I've 01:17 actually written up a little speech for 01:18 you guys here for my 15 minutes of fame 01:20 do I get 15 minutes I have been running 01:23 this program this tech interview 01:25 training program in which I will 01:26 actually help fast-track your career 01:28 with Joma check out their training 01:30 program tech interview procom you get 01:32 the first episode free when I first 01:34 began learning to code it was so 01:36 difficult look I'm not going to read 01:40 this whole thing for you guys just don't 01:43 be stupid check out the program tech 01:45 interview procom so one reason that I 01:47 think coding may be difficult is because 01:49 it is a combination of three different 01:51 skills actually not just one so you do 01:54 need the coding ability but to really be 01:56 an effective software engineer and to 01:58 actually get hired as one which 02:00 validates your skill sets 02:02 you also need problem-solving ability 02:04 algorithmic ability right that ability 02:06 to analyze a problem and come up with 02:08 the solution not just coding it we just 02:11 say the implementation and then you 02:13 also need communication ability because 02:15 coding is very much about teamwork if 02:17 you go into an interview and you are not 02:20 able to communicate properly you're not 02:22 able to express your ideas and thousand 02:24 to have that teamwork capability then 02:26 you're not going to get hired and then 02:27 you're going to go around thinking that 02:29 you're not a really good programmer you 02:31 may actually be fine in terms of 02:32 technical skills but maybe you were 02:34 missing that communication portion and 02:36 the problem is that many people will 02:38 have say two out of three of these 02:40 skills right you may be good at coding 02:42 and algorithms but you're not very good 02:44 at communicating or maybe you can do 02:46 some communication and coding but then 02:47 you don't have that algorithmic 02:49 analytical portion and you really need 02:51 to have all three portions to be 02:53 effective now the second reason that 02:55 coding is difficult I believe is because 02:57 it requires an inordinate amount of time 03:00 sitting in from the computer and just 03:02 staring at that screen and this is going 03:05 to be probably far more time than you 03:07 may be used to right for most other 03:09 disciplines you don't need to be sitting 03:11 down for a large amount of time focused 03:13 on something like say two to three hours 03:15 you can learn on the go right you could 03:17 go to a restaurant while you're eating 03:19 maybe you could read up on a little bit 03:21 of biology right learn a little bit of 03:23 chemistry while you're in the car spend 03:25 twenty minutes at the beach reading a 03:26 chapter of your history book that's okay 03:28 that's fine then that type of learning 03:30 can be done in segments but for computer 03:32 programming you really need to be 03:33 sitting at a single place at your desk 03:35 at the computer for a long period of 03:37 time many people are just not used to 03:40 being able to do that and they think 03:41 that that is just way too much and 03:42 they're not able to handle that and as 03:44 soon as they've sat down for say even 30 03:46 minutes they just say this is way too 03:48 much you know this must not be normal 03:50 they must not be good at it no that's 03:52 fine that's actually the proper path and 03:54 the way to do it the thing about 03:56 programming is that there's a certain 03:57 flow of things and you have to get into 03:58 that rhythm the study patterns are quite 04:01 different than other things that you may 04:02 be normally used to now another reason I 04:05 think that coding is difficult for 04:06 people is that it requires abstract 04:08 thought which is a skill that most of us 04:11 have not really been taught and many 04:12 people can go through life without 04:14 really using much abstract thought you 04:16 go through most of your say high school 04:18 without having to actually touch 04:20 abstract thinking at all and even many 04:22 people will go through college and their 04:23 whole lives without doing this but it is 04:25 about elevating your thinking 04:27 and generalizing towards more broader 04:29 concepts and relationships between 04:31 objects and concepts instead of looking 04:34 directly at the specific objects right 04:36 so for example if you take a look at the 04:38 dog 04:39 you may say at first that the dog's 04:42 color is brown and you have a computer 04:44 program that does this but then you may 04:46 be thinking if you were to start 04:47 thinking about this more abstractly why 04:49 do you even assign the dog's color to be 04:51 brown in the first place right 04:53 maybe the dog's color should be assigned 04:56 when the dog is born when the dog's name 04:58 is assigned at the same time that seems 05:00 to make more sense so you group all of 05:01 those things together but then you start 05:03 thinking well why is the dog a special 05:06 object within your whole entire system 05:08 should the dog be a special object and 05:10 should you be the one assigning it right 05:12 here in the program is the dogs more 05:14 special than anybody else why not assign 05:16 the cat a name why not assign the person 05:18 a name and the color as well so then you 05:21 may say okay well let's generalize the 05:22 concept of a dog to an animal and then 05:25 you have an animal factory that is able 05:27 to initialize these objects and assign 05:29 them names and colors and then you may 05:32 start thinking well why are you even 05:33 doing this client-side should then they 05:35 all be driven by the server and it 05:36 should be the server which is the source 05:38 of truth so you move everything to the 05:40 server and then the client has no 05:42 concept or notion about what an animal 05:44 even is the client is just a dumb but 05:46 view for rendering things so that gets 05:49 towards abstract thinking it helps you 05:50 generalize your concepts in the computer 05:52 system many people though they're just 05:54 going to say well why do you have to go 05:57 through all that the dogs color is brown 05:59 and let's just leave that that if you're 06:01 good at abstract thinking I believe that 06:02 it will also make you a good problem 06:04 solver another interesting facet about 06:06 coding is that you're never actually 06:09 done learning and there is no true sense 06:11 of accomplishment the field is just so 06:13 big so usually you just start learning 06:16 something and you feel that you've only 06:17 scratched the surface of it maybe you 06:20 only really understand 10% of it and 06:22 that's about right let's say you're 06:23 trying to learn react is you pretty much 06:26 just learn whatever you need to get your 06:28 portion of the work done but you never 06:30 really try to learn the whole thing the 06:31 framework is always changing and there's 06:33 always new technologies coming in and 06:35 parts of it being outdated and 06:37 deprecated all the time such that you're 06:40 sense of knowledge is always incomplete 06:42 and for some people they may not be used 06:45 to that right you may be learning a 06:47 physical equation or a math equation and 06:49 that's complete and you have the entire 06:51 knowledge right there you could be 06:53 reading a history book you've read the 06:55 whole chapter and that's about all there 06:56 is to it and you can piece together the 06:58 events 100% almost but in programming is 07:01 more like you only know about 10% and 07:04 sure there's a whole bunch more that you 07:05 can learn but that's fine and you just 07:07 leave it at that 07:08 the other thing is because the field is 07:10 so broad it is easy to get lost in the 07:12 weeds somewhere and it is easy to get 07:14 off track if you're not focused and 07:16 you're learning you could be wasting 07:17 your time learning all sorts of random 07:19 stuff that aren't really useful you can 07:21 spend all your time learning about 07:22 assembly code optimization which very 07:25 few people are going to need or you 07:26 could be wasting your time learning some 07:28 technology that's just not very useful 07:30 like how to decompile n64 game 07:32 cartridges in many ways learning code is 07:35 a battle against time in which you want 07:37 to prioritize your learning and make 07:38 sure that you're always on the right 07:39 track and not learning some piece of 07:41 technology that's not very useful and I 07:43 think people also really need to ask 07:45 themselves do you really want to code do 07:48 you think it is cool I think a lot of 07:50 people maybe they look at the amount of 07:52 money the salary income that software 07:54 engineers are making they think that 07:56 part's cool maybe they look at the 07:57 lifestyle but do they truly want to be a 08:00 programmer themselves or do they see 08:02 that as something that they may be doing 08:04 for say 1 or 2 years and then just give 08:06 that up because their heart was never in 08:08 it in the first place they don't think 08:09 it's cool most of us we are not brought 08:11 up thinking that software engineering is 08:13 very cool right we take a look at rock 08:16 bands singers musicians being an actor 08:19 or actress well that seems cool and a 08:21 lot of people would be willing to put 08:22 everything else on how to chase their 08:24 dreams for that but how willing are 08:26 people to give up say a Friday night out 08:28 at a bar with their friends to just sit 08:30 down and code not many people are 08:33 willing to do that because they just 08:34 don't think that coding is that cool a 08:36 lot of people think that coding is 08:37 something that you just pick up on the 08:39 side like learning to play that ukulele 08:41 it's not quite like that it requires 08:43 more commitment than that now one more 08:46 thing here is that the results will 08:47 validate you so you may think that 08:50 program is hard until you land the job 08:52 as soon as you have a job then you'll 08:53 feel 08:54 like oh hey yeah it was pretty easy and 08:56 this is where one big disconnect is is 08:58 that the coding interview process is 09:00 often completely different than actual 09:03 practical real-life programming and it 09:05 is actually a separate skill set right 09:07 you got to go through whiteboarding 09:08 questions and solve a bunch of brain 09:10 teasers and specific coding related it's 09:12 questions and there's a whole different 09:14 set of skills involved in that so the 09:16 challenge is that people maybe they get 09:18 through some coding practice and they're 09:19 actually pretty good by then but they 09:21 can't get the job so then they think 09:23 well coding is just seems so difficult 09:24 it's actually a different skill set that 09:26 you have to learn to pick up and this is 09:29 where I recommend you get some interview 09:30 training ex-google and X Facebook 09:32 engineers we're putting together a 09:34 training course program for you tech 09:36 interview procom so check that out we'll 09:38 get you all set that will teach you 09:39 everything you know to pass the coding 09:41 interview for large tech companies in 09:43 thing so I'm talking about coding data 09:45 structures analysis communication 09:47 behavior and all the other skills that 09:49 you're going to want to watch out for 09:50 you know one quote that I always think 09:53 about is the smallest decisions in life 09:56 often have the greatest impacts when you 09:59 invest in yourself maybe one day for in 10:02 the future you will look back on that 10:04 day that time and you'll say that was 10:07 the turning point right that smart 10:08 decision to invest in yourself I 10:10 invested myself my own skills and that 10:13 just sent me on a totally different 10:14 career trajectory and brought me to the 10:16 success that I have today let me know 10:18 why you think coding is difficult if you 10:20 liked the video give it a like and 10:21 subscribe and I'll see you next time 10:23 Thanks bye

You’re Not Alone, Coding is Hard! How to Deal with Programming Roadblocks

Ex-Google Tech Lead walks you through the career paths for software engineers and computer science majors. Join me at for daily coding interview practice. http://dailyinterviewpro.com And to really fast track your career, join me at for interview training with Live sessions. Intentionally navigating your career path is essential for programmers.  Learn your options and position yourself.  The website I referenced for job searches on Hacker News is http://techinterviewpro.com http://www.hnhiring.me 👨‍💻 Join ex-Google/ex-Facebook engineers for my coding interview training: http://techinterviewpro.com/ 👨‍💻 Videos of 100+ programming interview problems explained: https://coderpro.com/ 👨‍💻 Sign up for my FREE daily coding interview practice: http://dailyinterviewpro.com/ 🎬 Learn how I built a $1,000,000+ business on YouTube: http://youtubebackstage.com/ 📈 Get 2 FREE stocks on WeBull (valued up to $1,400): https://act.webull.com/k/S4oOH2yGOtHk... 🛒 My computer/camera gear: http://amazon.com/shop/techlead 💳 The TechLead "ultra-thin" wallet https://amzn.to/2WNhqEP ☕ The TechLead custom coffee-maker: https://amzn.to/3dxwrzr 💬 Join my Discord: https://discord.gg/pFUBUtE 🎉 Party up: http://instagram.com/techleadhd/ http://twitter.com/techleadhd https://www.linkedin.com/in/patrickshyu/ Disclosure: Some links are affiliate links to products. I may receive a small commission for purchases made through these links. #techlead Video Transcript: Note: This transcript is auto-generated by YouTube and may not be completely accurate. 00:00 hey Tech later and welcome back to 00:01 another episode of the tech lead it is 00:03 tea time with your host the tech lead 00:05 the tech lead now as an ex-googler at 00:09 lead I wanted to talk to you about the 00:11 potential career paths that you can be 00:13 taking as a software engineer you know 00:15 I've seen some people going around 00:16 learning machine learning and JavaScript 00:19 and just so you know that's just a 00:20 combination that is unheard of in tech 00:22 there is no role for something like that 00:24 you generally aren't running machine 00:26 learning in JavaScript on client-side 00:28 web browsers so I would encourage you 00:31 that if you really want to fast track 00:33 your career that you sign up for my 00:34 program daily interview procom so then 00:37 the interview Pro is a website in which 00:40 I will send you a free whiteboard an 00:42 interview question every day check it 00:43 out daily interview procom so what we're 00:46 going to do here today is we're going to 00:47 cover some of the top career paths and 00:50 also go over why some of these may not 00:52 actually be good choices for you some of 00:54 these are really only for senior people 00:56 and you need to start building your base 00:57 off of something simpler for entry-level 00:59 people there are certain career paths 01:02 that are far simpler to get into than 01:04 others you know if we take a look at the 01:06 beginning when you start off most 01:08 computer science students and even if 01:10 you didn't go through a computer science 01:11 school a lot of people start off 01:12 learning say Java or C C++ and this gets 01:16 you a standard role as a back-end web 01:18 engineer say another problem is if all 01:20 you know is Java or C then that really 01:22 limits the scope of work that you can do 01:24 and you'll be competing with everybody 01:26 for a few Java based on webpack and 01:29 engineer roles the fact is that most 01:31 companies are not running their backends 01:33 in Java these days a lot of companies 01:35 may be running Python or PHP on their 01:37 backends you know we're talking about 01:38 YouTube Instagram Pinterest uber and 01:41 more so that's our first role here web 01:43 back in engineer and this one of the 01:45 most common types and there's a pretty 01:47 good decent road to get started in it's 01:49 very traditional and so what you really 01:51 want to do here is pick up some common 01:52 languages like say Python or PHP maybe 01:55 pick up node.js and if you know Java or 01:58 C than all the better that's just going 01:59 to make you a stronger candidate and 02:01 more fleshed out and what you want to be 02:03 focusing in on here are web projects the 02:05 REST API contract between client and 02:08 server and what that API looks like what 02:10 the inputs and outputs are are you using 02:13 protocol buffers if you're looking to be 02:15 a an engineer and then you 02:17 certainly start mixing in a little bit 02:18 of graphics development game development 02:21 that's just going to end up kind of 02:22 wasting your time you know all learning 02:24 is good is great but it's not really as 02:26 focused and going to land your job as 02:29 quickly as if you had just really 02:31 focused in on that in 02:32 engineering role now the other type of 02:34 role we have here the second one is web 02:37 front-end engineer and this is an 02:39 especially easy entry point I think if 02:42 you're just looking to land a job in 02:44 tech you pick up a web front-end 02:46 technologies we're talking about 02:48 JavaScript CSS HTML learn some new 02:51 frameworks like say angular react view 02:54 Jas and these are going to get you set 02:56 up to be a web front-end engineer and 02:58 that's really all you need you don't 02:59 really need to touch the backend code 03:00 which generally requires a little bit 03:02 more Theory on the computer science side 03:04 if you take a look at many boot camps 03:06 out there that are aimed at people who 03:08 have no programming experience you may 03:10 notice that a lot of them they kind of 03:11 train you towards being a front-end 03:13 engineer and maybe they give you a 03:15 little bit a full-stack experience as 03:16 well so you can get prepared for that 03:17 but I've seen plenty of roles and 03:19 companies startups where people really 03:22 want is somebody working on the front 03:24 end building up those user experiences 03:26 buttons UI color fonts graphics 03:28 positioning layout hooking up api's onto 03:31 the back end but the front end usually 03:33 does not do much more than simple 03:35 rendering and if all you did was know 03:37 JavaScript very well then I think that 03:40 this could be an excellent entry point 03:41 for you to start getting your foot into 03:43 the door in tech now if you were to 03:46 actually combine say some of the 03:47 back-end and front-end and learn both of 03:49 these then you would be considered a web 03:51 full stack engineer which is excellent 03:53 for a long time I have been a web full 03:55 stack engineer and then the way I still 03:57 amp 03:57 the reason full stack engineer is so 04:00 good is because web is here to stay and 04:02 especially as mobile phones have been 04:04 getting more powerful a lot of companies 04:06 they don't really see the need to create 04:08 native applications they just create a 04:09 very good responsive website and that's 04:12 really all they need and it is also 04:14 perhaps the most entrepreneurial form 04:16 right if you are able to develop an 04:18 entire website back-end through front 04:20 end that you're able to pretty much 04:21 launch your own companies so this is one 04:24 big appeal for me 04:25 I didn't really want to be just a pure 04:27 back an engineer writing a bunch of 04:29 Python scripts because that would not be 04:31 sufficient for me to be entrepreneurial 04:33 in that sense so I think that the web 04:35 full-stack engineer is an excellent goal 04:37 for many people and it's a road that is 04:40 in high demand by many startups people 04:42 who just want you to do kind of a little 04:44 of everything put a whole feature 04:45 together front end through back ends 04:47 start to finish and for this sort of 04:49 role you're going to want some of that 04:51 front-end experience like JavaScript CSS 04:53 HTML maybe angular or react and that on 04:56 the back end you're going to want to 04:57 know maybe like Python PHP Ruby on Rails 05:00 Django Java nodejs golang some backhand 05:04 language like that and if you know some 05:06 databases like my sequel and then some 05:08 Linux to just glue everything together 05:10 then that's really going to get you all 05:12 set up there and so that brings us to 05:14 our fourth category here which is mobile 05:16 engineering it turns out that mobile 05:19 engineers are one of the biggest 05:21 categories of Engineers which may come 05:23 as a surprise to some people Mobile is 05:25 big and it has surpassed desktop usage 05:28 many software engineers including myself 05:30 have built their entire careers on being 05:32 a mobile engineer iOS or Android those 05:35 are the two big ones and you can pick 05:36 one to specialize in this is also an 05:38 excellent entry point by the way if 05:40 you're trying to get into tech if all 05:43 you knew was iOS engineering and you 05:46 decided to get good at that or Android 05:48 engineering then that's pretty much all 05:50 you need for a roll you don't need 05:52 JavaScript you don't need databases or 05:54 Python all you need is to know how to 05:55 build an Android app using say 05:57 Coughlin's or Java or for iOS it would 05:59 be swift or objective-c 06:01 so this is a very clean and easy path 06:03 right because all you have to do is just 06:05 learn one single language and you're set 06:08 and the other great thing about this is 06:10 that it can actually help you be 06:12 somewhat entrepreneurial as well right 06:14 it's pretty fun to be able to put 06:15 together an entire app front through 06:17 back launch it and you can have some 06:20 results there too you could put together 06:21 a game and try your luck at the App 06:24 Store maybe it will become popular maybe 06:26 you can build a useful service or 06:28 something like Twitter and that could be 06:30 quite useful as well if you were to mix 06:32 some of that client-side code experience 06:34 with a little bit of the backend code 06:35 back in the day 06:37 to be that iOS was the far better 06:39 platform but these days 06:40 Android is big in fact Android has 06:43 surpassed iOS a long time ago you know 06:45 the number of Android users is probably 06:47 four to one or five to one maybe more 06:50 than that by now Android has been 06:52 growing very quickly and even though iOS 06:54 is very popular in the United States 06:56 Android is by far the biggest global 06:58 market share 06:59 now another career path here that we've 07:00 talked about somewhere is game 07:02 development or graphics development and 07:04 this was something that I had been doing 07:05 straight out of college and a lot of 07:08 people I would say tried to get into 07:10 game development because that's really 07:11 the first interaction people have with 07:13 computers maybe they play a computer 07:15 game when they're a kid I played one and 07:17 then I was inspired by that and I wanted 07:19 to make my own games and really get into 07:21 graphics because it's so visual but the 07:23 funny thing is that you know Fame 07:24 companies they don't build games and the 07:27 game industry if you were to get into it 07:28 it's pretty notorious for low pay and 07:30 hard working conditions and they just 07:32 don't treat you with the same level of 07:34 respect as top tier tech companies in 07:36 Silicon Valley that's why it's a little 07:38 unfortunate that companies like Google 07:39 aren't making games they're not in that 07:41 game business if they were I think game 07:43 development would be an excellent field 07:45 to get into it's so fun you and they're 07:47 often working in C++ under type 07:49 performance limitations memory 07:51 requirements and performance 07:53 requirements they have to stay at 60 07:55 frames per second and then the graphics 07:56 programming portion as well often 07:58 requires a lot of knowledge about 07:59 physics shaders GPUs a whole set of 08:02 skills over there luckily because of 08:04 virtual reality and augmented reality 08:06 starting to gain traction graphics 08:09 engineering is actually becoming a 08:11 viable field here you know it used to be 08:13 that you could only do graphics 08:14 engineering if you were building like a 08:16 game engine and that was pretty much 08:17 about it but now you know you could be 08:20 working as a Google under VR or AR next 08:22 year and hardware or maybe simply on 08:24 some camera app or on creating YouTube 08:26 video filters now another area that we 08:29 haven't talked so much about and I don't 08:30 hear that much about but it turns out is 08:32 pretty popular is data engineering now 08:36 what I did here was I went to H and 08:38 hiring me and you can do this too this 08:40 is a list of job postings from hacker 08:42 news they just scraped the whole website 08:44 and then form 08:45 nicely for you and you can see that if I 08:47 were to look up data engineer there's at 08:50 least eighty matches for this and so 08:52 that's pretty much a lot of people are 08:54 looking for data engineers here data 08:56 engineering is really about organizing 08:58 data you may have tons of data logging 09:00 coming in and then you need to build 09:02 data pipelines in which you write 09:05 scripts and say Python or something like 09:07 that and you consume a bunch of data you 09:09 write sequel queries and then you output 09:11 that into a nice pretty table that is 09:14 fast query and then like a day the 09:16 scientists make worry that and just 09:18 present some data in a nice way so 09:20 that's data engineering and then there's 09:22 a whole bunch of other specialty fields 09:23 one of which is machine learning which 09:25 seems to be all the rage now it's very 09:27 popular I would encourage you that if 09:29 you are interested in machine learning 09:31 and it is a very popular thing that you 09:33 take a look at some of the job 09:34 requirements out there I don't think 09:36 it's the easiest thing for entry-level 09:38 people to start getting into it requires 09:40 quite a bit of math and experience in 09:42 this area to really be effective at 09:44 machine learning and oftentimes it's 09:46 funny that if I were to ask a new 09:48 college grant what they're interested in 09:49 90% of them will say machine learning 09:52 the thing is we don't need 90% of people 09:54 to be machine learning engineers right 09:56 we need like maybe say 10% to be machine 09:58 learning engineers and then for the rest 10:00 you know building like say some Android 10:02 app iOS app some back-end some front-end 10:05 and that there's really a whole host of 10:07 other interesting engineering types you 10:09 have cybersecurity DevOps 10:11 right that's like site reliability 10:12 engineering and this is one thing to 10:14 think about if you dig yourself into 10:15 Linux and Perl and scripting and bash 10:18 Unix commands that's not quite the same 10:20 thing as software engineering it's 10:22 actually closer to site reliability 10:24 engineering or DevOps so just understand 10:27 that there is a distinction between the 10:28 two they're both fine careers right any 10:31 career is actually fine you can just 10:32 pick whichever one that's exciting for 10:34 you and then there's QA engineer as well 10:37 and that really has to do with the 10:38 writing test automation software and 10:40 coming up with the test Suites to test 10:42 programs and systems front to back 10:44 integration testing unit testing 10:46 automated testing all sorts of stuff 10:49 like that if that's your interest and 10:50 other more power to you as far as that 10:52 goes I know that some people they get 10:54 into QA engineer 10:56 and then they hope that from there 10:57 they'll be able to springboard into 10:59 actual software engineering which is a 11:01 path that I've seen some people do but I 11:04 would just warn you that if you do take 11:06 this route there's a chance that number 11:08 one you could be digging yourself deeper 11:10 into QA engineering and it would 11:12 probably require you to actually be good 11:14 at that job to be able to transfer out 11:16 right like you would have to have enough 11:17 sufficient passion in test automation 11:20 engineering to really be doing that for 11:22 say six months to a year and you may not 11:24 be able to transfer out it may just dig 11:26 you deeper into that area whichever path 11:29 you choose I would recommend that you be 11:31 passionate about the work that you're 11:32 doing not just so that you can be in 11:34 there for like a show amount of time and 11:36 search out because I've heard stories 11:37 about people who get trapped in these 11:39 rows and then they realize that they 11:41 didn't really want to do this from the 11:42 first place and then that's a whole 11:44 other mess yourself so overall I would 11:46 recommend that you think about the 11:47 career path that you're taking and 11:49 position yourself correctly and navigate 11:51 that focus you're learning and yeah I 11:54 mentioned this because this seems to 11:56 happen so many intents I've been 11:58 reviewing a lot of resumes and here's a 11:59 quick plug for tech interview procom 12:02 where X Facebook engineer Joma and I 12:05 ex-google engineer we prepare you for 12:08 the technical interviews and that's part 12:10 of this we've also been reviewing 12:11 resumes so check it out Tech interview 12:13 procom work when the fast track your 12:14 career I've been reviewing resumes and I 12:17 just see some people there all over the 12:19 place they seem to be doing a little bit 12:21 of everything or they maybe have been 12:23 building up a skill in something that 12:24 just doesn't seem very useful you maybe 12:26 they've been learning some thought net 12:28 Java and then a little bit of JavaScript 12:30 and HTML and when I look at that profile 12:33 set it's just not clear what type of 12:35 person this is right what is that 12:36 profile is that a back-end engineer web 12:39 front-end engineer your Java engineer it 12:41 seems like just an engineer generalist 12:43 like just a standard coder but the thing 12:45 is I think that when people say they 12:46 want a generalist engineer what they 12:48 really mean is they're looking for a 12:50 full stack web engineer who understands 12:52 a specific tech stack check out the 12:54 roles that companies are looking for 12:56 even if you're not planning to apply now 12:58 you can take a look and just prepare 13:00 your path and think about the skills 13:01 that you may need to learn and that I 13:03 can just help you focus your learning 13:05 and land a job faster so that though for 13:07 me remember to give 13:08 video alike I really appreciate that 13:10 subscribe and I will see you next time 13:12 thanks bye

Overview of the Top Available Career Paths for Software Engineers With Advice on How to Navigate it 

Ex-Google TechLead explains his learnings from leaving Google. Thanks to Skillshare, an online learning community, for sponsoring this video. Receive a 2 month free trial at https://skl.sh/techlead3 Preparing for Technical Interviews? Join me at http://techinterviewpro.com/ 👨‍💻 Join ex-Google/ex-Facebook engineers for my coding interview training: http://techinterviewpro.com/ 👨‍💻 Videos of 100+ programming interview problems explained: https://coderpro.com/ 👨‍💻 Sign up for my FREE daily coding interview practice: http://dailyinterviewpro.com/ 🎬 Learn how I built a $1,000,000+ business on YouTube: http://youtubebackstage.com/ 📈 Get 2 FREE stocks on WeBull (valued up to $1,400): https://act.webull.com/k/S4oOH2yGOtHk... 🛒 My computer/camera gear: http://amazon.com/shop/techlead 💳 The TechLead "ultra-thin" wallet https://amzn.to/2WNhqEP ☕ The TechLead custom coffee-maker: https://amzn.to/3dxwrzr 💬 Join my Discord: https://discord.gg/pFUBUtE 🎉 Party up: http://instagram.com/techleadhd/ http://twitter.com/techleadhd https://www.linkedin.com/in/patrickshyu/ Disclosure: Some links are affiliate links to products. I may receive a small commission for purchases made through these links. #techlead Video Transcript: Note: This transcript is auto-generated by YouTube and may not be entirely accurate. 00:00 hey tackle it here and welcome back to 00:01 another episode of the tech lead now 00:03 today I'm going to be talking about how 00:05 I quit Google it is tea time with the 00:08 tech lead your host the X Google tech 00:10 lead now while many of us know that I 00:13 used to work at Google what we don't 00:15 know was how I left Google and what my 00:18 learnings were from there and I think 00:20 that these learnings will be applicable 00:22 to anybody who is working in any job 00:24 really because as a society we don't 00:26 talk much about quitting jobs right we 00:29 talked plenty about how to get jobs but 00:31 we don't talk about how to leave a job 00:33 properly and make sure that you're doing 00:35 it correctly and getting what you 00:37 deserve in that process you could get 00:39 pretty screwed over if you don't do it 00:40 correctly you know for example when I 00:42 left Google I tried to give them a four 00:45 to five week notice but they wanted me 00:47 out of there much faster like one week 00:49 and then I was out and they almost 00:50 didn't even pay out my health insurance 00:52 there's a lot of pitfalls there so we're 00:54 going to be covering these tips and more 00:56 this video by the way is brought to you 00:57 by skill share Scotia is an online 01:00 learning community with thousands of 01:01 classes covering dozens of creative and 01:03 entrepreneurial skills check them out 01:05 link in the description below so back to 01:07 my story when I left Google I gave them 01:09 a four week notice because I felt that I 01:11 was a pretty important guy over there 01:12 and I wanted to just you know make the 01:15 transition as smooth as possible but you 01:17 know I think what really happened was 01:19 that as soon as HR heard about this they 01:21 probably checked some things like maybe 01:23 stock vesting dates they check the 01:25 valves leaving for a competitor and they 01:27 just decided you know what they just 01:29 wanted me out of there in a week and you 01:32 know that wasn't really my plans right I 01:33 have planned to be working there longer 01:35 but eventually I even qualified for 01:37 unemployment insurance which is 01:39 ridiculous but I did collect that 01:41 because I qualified for it and I think 01:43 what you need to understand here though 01:45 is that HR is not your friend the job of 01:47 HR is to protect the company from 01:50 employees so if you're dealing with HR 01:53 you need to always have your guard up 01:55 and make sure that you're keeping your 01:56 cards close to your hand and even though 01:58 you may be friends and buddies with your 02:00 co-workers or even your manager they're 02:02 not necessarily able to protect you from 02:04 HR right that's an entirely different 02:06 organization and so let's get into tip 02:08 number one which is to use up your 02:09 vacation days it's 02:11 that many companies will say well hey if 02:13 you quit they'll just pay out your 02:14 vacation days anyways so you don't have 02:16 to use them if you don't want to but the 02:18 great thing about using them up is that 02:20 it helps you hit additional vesting 02:21 dates 02:22 it may help you hit additional bonus 02:24 dates maybe you can just stay around 02:26 stick around with the company and see 02:27 what other extra goodies you get maybe 02:29 some off sites right whatever that is if 02:31 you just personally use up those 02:33 vacation days you just get those extra 02:34 benefits of staying with a company 02:36 hitting your stock vesting dates is a 02:38 big one and you earned it so you deserve 02:40 it I didn't get mine by the way when I 02:42 was forced out earlier than I expected 02:45 so there were several thousand dollars 02:46 for me lost in that one there's also 02:48 additional benefits like you may get 02:50 access to remote offices you know I was 02:53 going to take a vacation to Japan at 02:54 that time I wanted to check out the 02:56 offices over in Japan I didn't get a 02:58 chance to do that there may also be 03:00 additional corporate discounts and perks 03:02 employees stores movie ticket discounts 03:04 things like that so use up those 03:06 vacation days instead of having them 03:09 paid out to you when you leave and then 03:10 just quit within two weeks or so when 03:12 you come back from vacation the second 03:14 tip I have for you is to never give more 03:16 than two weeks notice 03:17 never give more than that you know I 03:19 tried to give four weeks I thought I was 03:21 being nice I thought was important 03:22 you're not that important nobody is that 03:24 important you know I've seen directors 03:26 get terminated within one day for 03:28 violating some policy and the company is 03:31 still fine without them so they're gonna 03:32 be fine without you as well the second 03:35 you tell people that you're thinking 03:36 about leaving whether that's in two 03:38 weeks or four weeks you should be ready 03:40 to leave on that very same day because 03:41 HR can just come and terminate you right 03:44 away so a few tips you're number one 03:46 make sure that you handle your notice 03:47 after any of your stock vests right 03:49 check that invest in calendar number two 03:52 you want to make sure that you're 03:53 backing up anything on your computer 03:54 that may belong to you personally right 03:56 you don't want a backup company data but 03:58 if there's anything on your computer you 04:00 want to get that and secure any of your 04:02 personal belongings in the office 04:03 because you could be walked out that 04:05 very same day they could take your 04:06 laptop away immediately shut off access 04:08 if they suddenly just decide that you're 04:10 not team player if you're going to a 04:12 competitor any of those reasons like for 04:15 example I know a guy he used to work at 04:17 Google and he took a three-month 04:18 paternity leave and then when he came 04:20 back he gave a two weeks notice and then 04:22 he left 04:23 and you know I think that was a really 04:24 smart move actually because he had given 04:26 a two-week notice before he went on 04:28 paternity leave HR would not have given 04:31 him that paternity leave they would have 04:33 terminated him that very same day if 04:35 they needed to but they would not have 04:36 paid that out if they could have saved 04:38 that for themselves which in my opinion 04:40 may not be entirely fair right maybe he 04:42 earned that paternity leave and it would 04:44 have been probably fairly brutal on him 04:46 if he was having a new kid and then he 04:48 was terminated from his job that very 04:50 same day but the company may just do 04:52 that and you need to protect yourself 04:53 the third tip I have for you is just 04:56 make sure that you're checking the 04:57 company calendars bonus calendars look 04:59 for any additional events coming up it's 05:01 funny that if you detract like when 05:03 people quit a lot of people are smart 05:05 enough to know that you quit after bonus 05:07 season you know in my very first job as 05:09 so many pictures I quit on the 05:11 anniversary date that I had joined which 05:13 I thought was very cool very interesting 05:16 I could say hey I work there exactly one 05:17 year but I did not get my bonus bonus 05:20 comes a little bit after that so there 05:22 were several thousand dollars that I had 05:23 lost right there the fourth tip is to 05:26 take a moment and check your benefits 05:27 portal if you have one and make sure 05:29 that you're maximizing all of that so 05:32 I'm talking about like 401k matching I 05:34 like to front-load my 401k so I will 05:37 always put in like a hundred percent of 05:38 my paycheck into that and just max it 05:40 out as soon as I can 05:41 each year such that if for any reason I 05:43 left my job I could at least get my 401k 05:46 contributions in and if there was an 05:48 employer match then I would get that as 05:50 well by the way not all employers are 05:52 going to be matching you 100% rather way 05:54 sometimes our caps and limits but you 05:56 can check with your plan about that you 05:57 know if there are other things like FSA 05:59 flexible saving account plans dependent 06:02 care accounts try to get those maxed out 06:04 as well use them up because they could 06:06 expire at the end the fifth tip I have 06:08 for you is to never quit a job without 06:10 having another job in hand why is this 06:13 important you know because I think this 06:15 is leverage right when you're getting 06:18 another job and you're trying to 06:19 negotiate that compensation if you don't 06:21 even have another job in hand and you've 06:23 got nothing then you've got no leverage 06:24 but if you already have a job and then 06:26 you're trying to apply to another 06:27 company that company knows they need to 06:29 at least beat your current compensation 06:31 and there may even be an additional 06:33 counteroffer that they don't need to 06:35 beat as well 06:36 so you already have leverage right there 06:38 that's actually kind of acting as you're 06:39 competing offer right there just by 06:41 holding on to that job if you gave that 06:43 up because you just decided to rage quit 06:45 you don't have any leverage you don't 06:47 have power and then you're essentially 06:49 willing to work for zero dollars right 06:51 even if someone were to pay you ten 06:53 dollars they've already beaten your 06:55 current salary so this is about 06:57 negotiation leverage that will get you 06:59 set up for your next grow the sixth tip 07:01 I have for you is that when you're at 07:03 that exit interview don't say a word or 07:06 keep a play and keep it professional 07:08 I think exit interviews are kind of 07:11 silly like imagine that you got dumped 07:13 by somebody and then they said well hey 07:15 now that the relationships over why 07:17 don't you just let loose and just tell 07:18 them everything that you didn't like 07:19 about them it's like why would you even 07:22 waste your time doing that you're trying 07:23 to get the next portion of your life 07:24 started and now you want to just 07:26 badmouth each other and let loose for 07:28 what gain what's the point you're gone 07:31 it's not even your problem anymore 07:32 and if they really cared maybe they 07:34 should have asked you when the 07:35 relationship was still working out so 07:38 what I'm trying to say here is that 07:39 number one don't burn your bridges keep 07:42 things professional and number two what 07:44 do you have to gain by giving any of 07:46 this advice to your former employer 07:48 right oftentimes you're going to be 07:50 talking to HR it's not even the 07:52 engineering manager or the team who is 07:54 doing the exit interview for you do you 07:57 think that people actually take your 07:59 feedback and use it to improve the 08:02 company I don't know I'm not part of HR 08:06 but I wouldn't be entirely surprised if 08:09 they just took that filed it away and 08:11 put it in your personal records and just 08:13 use that as leverage against you as your 08:15 own personal history record I don't know 08:16 if they actually integrate that into any 08:18 of their internal feedback processes or 08:20 to improve the company at all I don't 08:23 know if they do but keep in mind that 08:25 this isn't a family farewell party you 08:27 don't have to be Terry either pardon you 08:29 don't owe these people any explanation 08:31 it's simply a business deal that has 08:32 closed out and now both parties are 08:34 moving on to future opportunities it's 08:36 as simple as that the seventh and final 08:39 tip for you is just about health 08:40 insurance make sure you're quitting 08:42 after say like the first of the month 08:43 usually health insurance plans they'll 08:45 continue your coverage through the end 08:47 of the month in which you are employed 08:48 so if you quit on like the 30th then you 08:51 may be forced into buying Cobra health 08:52 insurance right away Cobra by the way 08:54 it's extremely expensive health 08:56 insurance it's essentially like the same 08:58 solid health insurance that companies 08:59 have but you just gotta pay for that out 09:01 of pocket individually it's just crazy 09:03 prices there so overall just keep in 09:06 mind that usually when you quit people 09:07 are going to be asking you to stay maybe 09:09 it will work on the extra month maybe an 09:11 extra two months just kind of delay the 09:13 process for you and you just need to 09:15 really prioritize yourself I will say 09:17 two weeks right that's about all you 09:19 really need and don't let anybody else 09:21 for you into thinking that you're more 09:23 important than they're telling you that 09:24 you're and you know you need to 09:26 prioritize yourself the company they're 09:28 gonna be doing just fine they're gonna 09:29 be great actually one more thing if you 09:32 enjoyed this video and you want to land 09:33 the job intact check out Tec interview 09:35 procom it's a new program created by 09:38 DOMA and AI DOMA is an ex Facebook 09:40 software engineer and he's landed 09:42 numerous internships and jobs at like 09:44 Microsoft LinkedIn and more we're going 09:46 to be giving you some of our top tips 09:48 about how you can land a job in tech how 09:50 you can pass the technical coding 09:52 interview it's gonna be a lot of fun and 09:54 it's going to fast-track your career if 09:56 you're looking to further improve your 09:57 skills I also highly recommend you check 09:59 out Skillshare Skillshare is an online 10:01 learning community you can explore 10:03 classes and everything from photography 10:05 and creative writing to marketing 10:07 productivity web development 10:08 entrepreneurship and more their website 10:11 is beautiful they've got tons of courses 10:12 that are going to get you set up 10:14 very reasonable pricing here Premium 10:16 Membership gives you unlimited access to 10:18 high-quality classes from experts 10:20 working in their fields to help you gain 10:22 new skills and live your best life one 10:24 high quality class they have here is the 10:26 JavaScript toolkit this one class will 10:28 teach you to become a JavaScript expert 10:30 with in-depth guides to new essential 10:32 tools and techniques every developer 10:34 should know because Skillshare 10:35 sponsoring this video you'll get a two 10:37 month free trial link in the description 10:39 below so they'll do it for me let me 10:41 know your best tips on how to leave a 10:43 job if you liked the video give it a 10:44 like and subscribe and we'll see you 10:45 next time bye

Sharing My Learnings After Leaving a Big Tech Company

Ex-Google TechLead explains differences between working at a tech startup and a large company, and their pros & cons. Check out Ting mobile service for a cheaper pay-per-use cellphone plan and get $25 off your bill: http://techlead.ting.com 👨‍💻 Join ex-Google/ex-Facebook engineers for my coding interview training here. http://techinterviewpro.com/ 👨‍💻 Watch 100+ programming interview problems explained: (20% off now, limited time) https://coderpro.com/ 👨‍💻 Sign up for my FREE daily coding interview practice: http://dailyinterviewpro.com/ 🎬 Learn how I built a $1,000,000+ business on YouTube and the behind-the-scenes strategies of running a successful YouTube channel: http://youtubebackstage.com/ 📈 Get your 2 FREE stocks on WeBull (valued up to $1,400): https://act.webull.com/k/S4oOH2yGOtHk... 🛒 My computer/camera gear: http://amazon.com/shop/techlead 💳 TechLead "ultra-thin" wallet gift: https://amzn.to/2WNhqEP ☕ TechLead custom coffee-maker gift: https://amzn.to/3dxwrzr 🎉 Party up: http://instagram.com/ techleadhd/ http://twitter.com/ techleadhd/ https://www.linkedin.com/in/patrickshyu/ Disclosure: Some links are affiliate links to products. I may receive a small commission for purchases made through these links. Video Transcript: Note: This transcript is auto-generated by YouTube and may not be entirely accurate. 00:00 hey tech leech here and welcome back to 00:01 another episode of the tech lead today 00:04 we're going to talk about a very 00:05 fascinating interesting topic startups 00:07 versus big tech companies it is coffee 00:10 time with the tech lead I am the tech 00:12 lead at Google tech lead by the way 00:14 let's have a sip here not bad not bad at 00:20 all now sunny cooler let me just clarify 00:24 something for you if you are working in 00:27 tech adult and I think that you're gonna 00:29 be doing great you're gonna be doing 00:30 good and no choice is really going to be 00:32 a bad choice and startup or big tech 00:34 company it's all good really now I have 00:36 worked in a combination of startups as 00:38 well as at Google as an X Google tech 00:41 lead and they're very different in some 00:44 ways but they're also very similar the 00:45 quality of life that you get your 00:47 overall standard of living it's about 00:49 the same really now we have a new 00:51 sponsor today and I would actually 00:52 highly recommend that you guys check 00:54 them out 00:54 ting mobile if you live in the US and 00:56 you're using cell phone service and 00:58 you're paying like 50 60 bucks a month 01:00 for this service it's a contract you're 01:02 locked into one or two year contracts 01:04 you know that's just really not the way 01:06 to go there are far better options ting 01:08 Mobile offers you paper use cell phone 01:10 service and the cost is very cheap you 01:12 can figure out how much it might cost 01:14 you I would say for an average person 01:15 it's probably gonna be 15 to 25 bucks or 01:18 something like that and one of the best 01:19 parts is that there's no contract you're 01:21 not locked into anything you know I 01:23 remember when I was trying to become a 01:24 world citizen travel all over the place 01:26 and embrace that mobile lifestyle one of 01:29 the things I was really locking me down 01:30 was my cell phone service it was just 01:32 tying me to the u.s. tied me down there 01:34 with that one or two-year cell phone 01:36 contract and that was one thing that 01:37 kept weighing on me so with t-mobile you 01:40 get a no contract cell phone plan you 01:41 get voice messaging data all comes at 01:44 the very reasonable standard rate and 01:46 the great thing is it's so simple to 01:48 setup there's no contract you just send 01:49 them a dollar they send you a SIM card 01:51 back you plug that into your cell phone 01:53 and then you're off and running and when 01:54 you're gonna save so much money check 01:56 them out ting Mobile there'll be a link 01:57 in the description below and you can 01:59 thank me later you know no matter 02:00 whether you're working at a startup or a 02:02 big tech company you're gonna be having 02:04 a pretty sweet comfy job you're gonna go 02:06 and you work at the computer you do some 02:08 typing do some code spend some time 02:10 surfing the net surfing reddit play some 02:12 ping pong you may 02:13 have to pay for your online tour you may 02:14 get some lunch catered and by the way 02:16 the food that these large tech companies 02:18 are not necessarily better there may 02:20 simply just be more variety but it's all 02:22 going to be buffet style food and often 02:24 is quite easy to beat any of the sweet 02:26 just go to any restaurant and the food 02:28 quality is already going to be beaten 02:29 supposedly they like to advertise that 02:31 they've got all-star chefs but in order 02:33 to feed thousands of people it's just 02:36 going to cost way too much they're gonna 02:38 end up using more basic ingredients trip 02:40 ingredients and then do it buffet style 02:42 and you're not going to want to eat too 02:43 much food anyway it's not gonna be 02:45 healthy for you just gonna get 02:46 overweight essentially most of the time 02:48 no matter where you are you're going to 02:49 be working at the computer doing some 02:51 code across startups and big tech 02:53 companies is going to be similar now 02:55 let's talk about the main differences 02:56 here one is going to be compensation 02:58 compensation at a tech company a public 03:01 tech company is going to be well-known 03:02 it's going to be fixed 03:03 you're gonna know exactly what you're 03:05 getting is a public company and when you 03:07 get stuck you're gonna know for sure 03:09 that that's going to be worth something 03:10 when you go into a start-up you don't 03:13 really know what the value of that stock 03:15 is going to be and oftentimes it's going 03:17 to be a complete mystery it's going to 03:18 be completely obfuscated for you and 03:20 startups have a bunch of different ways 03:22 to screw you over they can dilute the 03:24 stock they can kick you out fire you 03:25 before they IPO they can delay their IPO 03:28 intentionally and force you to stick 03:29 around and stay at the company and work 03:31 longer they can tell you that you have a 03:32 million shares but it really there could 03:34 be a hundred trillion shares outstanding 03:36 and many companies simply aren't going 03:38 to tell you what percentage of the 03:40 company you truly own and even if you 03:42 were to somehow find that out which you 03:44 probably won't be able to find out most 03:46 companies I've seen they never quite 03:47 tell you exactly what percentage you own 03:49 even if you do find out they're just 03:51 going to devalue that when you finally 03:53 leave the company when you quit 03:54 oftentimes they'll say that you have to 03:56 exercise these stock options within a 03:58 certain amount of time like saying you 04:00 got three months to use that up and when 04:02 you do exercise those options you're 04:04 going to have to pay tons of taxes on 04:05 this stuff if the company never IPOs and 04:08 it could take ten years before the 04:10 company actually IPOs you've just paid a 04:12 bunch of money on stock and you've taken 04:14 a big risk you don't really know what 04:16 you're getting sometimes this stuff all 04:18 pans out maybe you'll get some money but 04:20 oftentimes it's not necessarily going to 04:22 be life-changing money I'm known 04:24 scenarios where I've joined companies 04:26 actually in other 04:26 people join companies and then the 04:28 startup eventually gets acquired right 04:30 acquisition happens more commonly than 04:33 IPOs and in an acquisition everybody 04:35 gets some payment for their stock it's 04:37 not all that much it's not really 04:39 life-changing money you might be like 50 04:41 K right 60 K something like that 04:43 if you're lucky it could be more if 04:45 you're not lucky it could be less one 04:47 thing that a lot of engineers don't know 04:49 is that even if your engineer number one 04:51 at the company you could already be 04:53 getting less than say 1% of the company 04:55 you would be putting in as much work if 04:57 not more work than the founders and 04:59 still the founders would have like 99% 05:01 of the company you would have one 05:02 percent or even 0.1% by the time your 05:06 employee numbers say ten or twenty your 05:08 ownership would already be point zero 05:10 zero zero one percent or something like 05:11 that 05:12 it would be a minuscule amount and 05:13 that's just a culture of startups 05:15 personally I got so disgusted by all of 05:17 this one time I remember I had the 05:19 business partner a friend and we were 05:21 going to start a company together and 05:23 then he said that yeah we would be 50/50 05:26 partners except he wanted 50.1% and I 05:29 would get 49.9% I just thought why why 05:32 not just 5050 and he was so insistent on 05:35 this point that it smelled fishy to me 05:37 and I backed out of the whole deal and I 05:39 didn't start the business because I 05:41 figured that he could just say well 05:43 let's take a vote should I get kicked 05:44 out of the company after I feel 05:46 everything yeah let's take a vote he's 05:48 got 51% ownership oh yeah he wins I mean 05:50 he could just kick me out he can do 05:52 whatever he wants now it's just our 05:53 pretty tricky and I remember there were 05:55 even times in my life when I just sort 05:57 of said to myself I don't like startups 05:59 I don't want to work at them and if I 06:01 were gonna work I would rather work 06:03 either for a large tech company or I 06:05 would found the company on my own and 06:07 those would be the options I would be 06:08 going for now having said that let's 06:11 talk about some of the good things about 06:13 startups because I've worked out a few 06:15 of them and there's some good things 06:16 about them one is the challenges are 06:18 going to be very different between 06:20 start-up and large tech company large 06:22 tech company you often work in a large 06:24 code base a lot of the challenges are 06:25 going to be organizational you're going 06:27 to have to deal with a lot of people 06:28 cross-functional teams and there's going 06:31 to be a ton of code and people blocking 06:32 everything that you're trying to do and 06:34 in a small tech company in a start-up 06:36 you're going to have a lot more freedom 06:38 and anything you want to do 06:39 anything you want to try just not going 06:42 to be a lot of people standing away you 06:43 want to try something you have the 06:45 flexibility to try that and that goes 06:47 for rolls as well so if you don't really 06:49 want to be an engineer let's say you 06:51 want to be more of a product manager or 06:53 designer or prototype or in a large tech 06:56 company it would be an entire shift in 06:58 careers you would have to get the proper 07:00 approvals maybe even do an interview 07:02 just so that you could do some p.m. work 07:03 however in its small startup you're 07:06 gonna have a lot more freedoms to take 07:08 on any role that you want and in this 07:10 sense I would say that there may even be 07:12 better career mobility for example if 07:14 you wanted to get into management it may 07:16 take a lot of effort to get into say 07:18 senior management at Google right that 07:21 would require you proving yourself and 07:22 everything but if you were to go to a 07:24 start-up you could probably get a 07:26 management role quite easily because the 07:28 requirements just aren't as strict you 07:29 can start building up your experience 07:31 and over a number of years you would 07:33 have that experience and then you can 07:34 transfer into large tech company like 07:36 Google and do management there and you 07:38 would already have built up a lot of 07:39 that experience if that were your 07:41 interest and so if there were areas in 07:43 your career that you want to do develop 07:45 more into a startup may be a good path 07:47 for that and that's really what a 07:48 startup is good for I would say it's 07:50 learning so I would recommend this if 07:54 you are a junior engineer or even if 07:56 you're not and you want to get some more 07:58 experience and learn and build your 08:00 skills in a certain technology there may 08:02 be a field that you're interested in 08:03 getting more until you think it's cool 08:05 and you want to do that then the startup 08:07 is a great way to do that the worst 08:09 reason to join the startup is because 08:11 you think as a library ticket and it's 08:13 going to make you rich and you hate the 08:14 work and you're not trying to learn 08:15 anything but you're just doing that 08:17 currently for the money because in that 08:18 scenario I would say I startup there's a 08:21 little chance it's going to work out for 08:22 you if I you curveballs money the other 08:24 thing I might mention here is that I 08:25 don't think money is the proper 08:27 motivation number one if you're a junior 08:29 engineer say either way your pace look I 08:32 know it sounds like a lot for you now 08:34 but it's not going to make a difference 08:35 for you in a few years when you look 08:37 back on that salary range that you're at 08:39 just spend your time trying to learn and 08:41 guide your career in the direction that 08:43 you want it to go to but trying to argue 08:45 and optimize for a few thousand bucks 08:47 here and there it's just not really the 08:49 right time to be doing that because 08:50 you're really splitting pennies at 08:52 point the other great thing about 08:53 startups is they can be a little bit 08:55 more closed now I remember I worked in a 08:57 start-up with one of my professors and 08:59 during the company holiday party it was 09:02 just us with our spouses or girlfriends 09:04 or boyfriends or whatever and there just 09:06 felt more like a family the office was 09:08 like the professor's living room you 09:10 don't really get this sort of dynamic 09:11 when you're in a larger company in which 09:13 it's an open door right people are 09:15 coming and going all the time and 09:17 there's tons of people that you may be 09:18 interacting with you don't really get to 09:20 know anybody really that well sometimes 09:22 people just get fired to just disappear 09:25 randomly and that just seems to happen 09:27 sometimes 09:28 so overall let me put it this way I 09:30 think that if you can get into a large 09:31 tech company then you might as well try 09:33 and it's good to explore your options 09:35 and see what you can get 09:36 but startups are great too you can learn 09:39 a lot there develop your skills and 09:40 experience there are some good 09:42 connections get to know some people 09:43 there and overall it's probably going to 09:45 be a pretty good time working there 09:46 because it's not like going to a large 09:49 tech company like Google you're gonna 09:50 have a 10 times better experience there 09:53 it's not quite like that it's more like 09:54 it's just bigger it's not like the food 09:56 is 10 times better it's not like the 09:58 computers are 10 times more powerful 10:00 it's still essentially the same stuff 10:02 the same environment that you're working 10:03 in maybe for lunch instead of having a 10:06 single item on the menu you may have 10 10:08 different items on the menu but you 10:09 still just pick one thing to eat when 10:11 you interact with people and self 10:12 interacting with five people you may 10:14 have to interact with 50 people when you 10:17 work on a codebase it would just be a 10:18 larger codebase and the office overall 10:20 may be larger instead of having a single 10:22 building there may be 10 different 10:24 buildings that are interconnected but 10:26 you still end up going to a single 10:27 building your small little desk whenever 10:29 you're going to work in that sense the 10:31 work environment is similar and often in 10:33 many scenarios a startups work 10:35 environment the facilities the bathrooms 10:38 the kitchens that stuff can actually be 10:39 better and higher quality than what you 10:41 may find that large tech companies I 10:43 will say that for a lot of people it 10:44 might make sense at some point once 10:46 you've learned enough once you've 10:47 developed enough experience that you may 10:50 want to prioritize compensation maybe 10:52 make sure that you've got some real 10:53 money on the table that you can lock in 10:55 there maybe tackle some different types 10:57 of technical problems and challenges 10:59 those that have to do with larger code 11:01 bases dealing with many different types 11:03 of people you know that 11:04 interesting challenge in itself and also 11:06 just add some more options to your lunch 11:08 menu those are all things that larger 11:10 tech companies will be able to offer you 11:11 so it may not be a bad idea to consider 11:13 those two at some point I mean the way 11:15 you think about startups versus large 11:17 companies in the comments below if you 11:19 liked the video give a like and 11:20 subscribe and see you next time right

David Vs. Goliath: Startups and Big Tech, Which Trumps Which?

How I Got a Job at Google (as a Software Engineer)

Ex-Google Tech Lead talks about building a side-hustle and making $40K/month in your 20's. Preparing for Technical Interviews? Join me in my new coding interview training program: http://techinterviewpro.com/ Get extra whiteboard coding practice with 50+ video sessions at: https://www.coderpro.com Sign up for my FREE daily coding interview practice: http://dailyinterviewpro.com/ Learn how I built a $1,000,000+ business on YouTube and the behind-the-scenes strategies of running a successful YouTube channel: http://youtubebackstage.com/ Get your 2 FREE stocks on WeBull (valued up to $1,400): https://act.webull.com/k/S4oOH2yGOtHk... My computer/camera gear: http://amazon.com/shop/techlead TechLead "ultra-thin" wallet gift: https://amzn.to/2WNhqEP TechLead custom coffee-maker gift: https://amzn.to/3dxwrzr 🎉 Party up: http://instagram.com/techleadhd/ http://twitter.com/techleadhd/ https://www.linkedin.com/in/patrickshyu/ Disclosure: Some links are affiliate links to products. I may receive a small commission for purchases made through these links. Video Transcript ( Note : This transcript is auto-generated by YouTube and may not be 100% correct.) 00:00 alright hey tech elite here and welcome 00:02 back to another episode today we're 00:04 going to be talking about how to start 00:06 and grow a small business and we're 00:08 going to be talking to somebody somebody 00:10 in their 20s who has founded a 00:12 multi-million dollar business a company 00:14 and that person is going to help us get 00:17 all started and/or gentleman what are 00:20 you doing here I'm not talking about you 00:22 Gemma what do you mean well maybe you 00:26 should go to sleep then gather here go 00:28 to bed it's past your curfew time not 00:30 talking about you either and start a 00:32 multi-million dollar business yeah here 00:36 let me get over here climate climate hey 00:41 Clement now Clement here has started and 00:44 grown a very successful business in his 00:47 20s Clement is going to tell us all 00:49 about how he got this started what were 00:50 the logistics and how to practically get 00:53 a business going and why it is so useful 00:55 for young people to be starting small 00:57 businesses he's going to take us all 00:59 through the steps what was this business 01:00 that you started and tell us all about 01:02 it 01:02 our business is called Aldo expert algo 01:04 expert gallo it's basically targeted at 01:07 software engineers who like you and I 01:09 who want to prepare for their coding 01:11 interviews especially a big tech 01:13 companies big startups and we provide 01:15 curated questions like the ones you find 01:18 these coding interviews and we give 01:20 video explanations for those questions 01:22 of coding work space etc etc so you can 01:24 go to algo exper do a slash tech we'd if 01:27 you want to check it out that's right 01:29 you want to make sure you use code 01:30 technically get discount check them out 01:32 now start your business sounds cool and 01:34 we are here all the time well just our 01:36 business list our business I'm gonna 01:38 start business but how exactly do you 01:40 start a business what are the steps that 01:42 you have to go through what are the 01:44 challenges and how do you concretely get 01:46 this off the ground yeah so the first 01:49 step I think is coming up with the idea 01:50 and to be honest I think a lot of ideas 01:53 can work it's just about finding a 01:55 problem and then coming up with a 01:56 solution to that problem and building it 01:59 and executing it and so in my case I was 02:02 prepping for coding interviews and I was 02:05 using a bunch of resources textbooks 02:07 websites online YouTube Wikipedia and I 02:10 thought there's got to be a better way 02:11 that's how I came up with the idea 02:13 sounds simple enough do you do it by 02:15 yourself do you have a co-founder do you 02:17 set up like a LLC do you incorporate 02:20 start partnership you can do it alone 02:22 I think alone is a bit tougher I ended 02:25 up having a co-founders so I contacted 02:27 one of my best friends who happens to be 02:29 a software engineer as well I pitched 02:31 him the idea and he was on board and we 02:34 got it up and running so we ended up 02:35 going with an LLC the reason being is it 02:38 fit our needs the best we wanted from a 02:41 tax point of view to have things be 02:43 simple we want to only be taxed once 02:45 right so now we'll see was good for us 02:47 from that point of view as opposed to 02:49 corporation for instance but we also 02:52 wanted that limited liability that a 02:55 partnership a general partnership may 02:57 give you yeah that's right because as I 03:00 understand that you have a sole 03:01 proprietorship and that is where anyone 03:03 can actually start a business you just 03:05 start making money and that's a business 03:07 already you're a sole proprietorship now 03:09 is that beyond that you can actually 03:10 form a partnership say with multiple 03:13 people but that's still pretty much ax 03:15 very similar to like a sole 03:16 proprietorship the level above that is 03:18 you for my OLC which acts more like a 03:21 corporation where you can pay yourself a 03:23 salary you get limited liability such 03:25 that if anyone sees you they don't have 03:28 access to your personal assets is simply 03:31 the company standing alone on its own 03:33 and then the company has its own bank 03:34 account its own social security number 03:37 for tax purposes 03:38 everything is very separate and then 03:40 it's easier in a way to separate your 03:42 business and personal expenses now how 03:44 do you go about forming an LLC isn't it 03:47 very complicated aren't there all sorts 03:49 of paperwork that you have to go through 03:51 so it's a little bit complicated there 03:53 are a few services like stripe Atlas 03:55 Legal Zoom Rocket Lawyer that'll give 03:58 you like services to make the LLC for 04:00 you or help you along the way we ended 04:03 up is doing it ourselves it's sort of 04:05 like old-fashioned rent 04:06 oh wow so you just filed the audit 04:08 paperwork on your own yeah we went to 04:09 the State Department and did all that by 04:11 ourselves how complicated was that to do 04:13 on your own it's intimidating but not 04:16 actually that complicated okay 04:18 interesting now I have formed a few 04:20 LLC's myself as well and generally I 04:23 just use a service like lemon mint 04:25 and that's an arrow it's very simple and 04:27 easy to get this all set up you just 04:29 fill out an online web application press 04:31 submit button and don't get a LLC all 04:33 set up for you what are the fees 04:34 involved in it I'll see here so you have 04:37 an incorporation fee it's escaping me 04:39 right now but it's roughly two hundred 04:42 to a thousand dollars something like 04:44 that might vary from state to its eight 04:45 hundred dollars in California and as I 04:48 understand that you choose a state to 04:50 incorporate in and then you can actually 04:52 operate in any other state yep 04:55 which state did you choose we ended up 04:56 giving New York we just fit well for us 04:58 okay cool 05:00 generally I will actually register in 05:02 Delaware which is very well known for 05:05 its business friendly laws and then you 05:07 can operate as a foreign business in 05:09 other states yep not working now once 05:11 you have to say I'll see you all set up 05:13 how did you fund the company so we 05:15 didn't need too much money at the 05:16 beginning so we just put $2,500 each up 05:19 front me and my co-founder and that was 05:21 it the company has been self-sustaining 05:23 ever since did you ever have issues 05:24 choose iam co-founder I find that they 05:27 say co-founders are often almost like 05:29 having a marriage because you get to 05:31 work with the co-founder so closely and 05:33 you have to work out so many different 05:34 issues how did you know that you could 05:36 trust your co-founder what would happen 05:38 if your co-founders decided to just stop 05:40 working at some point this is where I 05:42 totally agree I think choosing the right 05:44 co-founder is probably the most 05:45 important thing you can do me and my 05:48 co-founder are lucky in that we're very 05:51 good friends and we just have that trust 05:53 on top of that we have very 05:56 complementary skill sets and we also 05:58 have different sort of like goals so we 06:00 don't overstep on each other and it just 06:02 works out really beautifully we're able 06:04 to work remotely pretty seamlessly with 06:06 no personal issues no work issues 06:09 fighting someone who has a complementary 06:13 skill set it's probably gonna be one of 06:15 the most important things because so 06:16 that you it's actually useful to have 06:18 multiple people and then probably just 06:21 making sure that you have open 06:22 communication if you have open 06:24 communication and trust you will be able 06:26 to work together and you can maybe even 06:28 be creative instead of things where you 06:30 have to work a certain amount of time or 06:32 produce a certain amount until you get 06:35 your equity in the business so is your 06:37 business purely online 06:38 do you have office space yeah so we're 06:41 purely online that means that we don't 06:43 have an office space we can work 06:45 remotely from wherever we are in a 06:47 coffee shop on a beach if we want that's 06:49 one thing that's really cool about the 06:52 era that we live in where we can build 06:53 fully online businesses and not have to 06:58 deal with the difficulties of having a 07:01 physical product having to have an 07:03 office space or a warehouse or hold 07:05 inventory of course not everyone has 07:07 luxury to do this not everyone has a 07:08 purely online business but you can't 07:11 have that these days yeah I think that's 07:13 one interesting thing when that was 07:15 running the online businesses it 07:17 actually allowed me to take time off 07:18 work between jobs there wouldn't be like 07:21 a huge resume gap because I could say 07:23 well I'm working on this business during 07:25 that time I can do some traveling during 07:27 that time as well and I just get more 07:29 flexibility and freedom in what I'm 07:31 doing well at the same time still being 07:33 productive and living how I might choose 07:36 to live I remember I would work from 07:38 Hawaii sometimes or work on cruise boats 07:40 now you're painting a really good 07:41 picture of running your own business 07:43 what are the cons of this what are the 07:45 challenges of running the business yeah 07:48 I think that there there are three big 07:50 challenges but in some sense they are 07:53 also positives if you like this if you 07:55 have that sort of entrepreneurial itch 07:57 the first one is there's a lot of work a 08:00 lot of the work is gonna be stuff that 08:01 you don't like 08:02 like for instance forming the LLC 08:04 marketing I'm not the biggest fan of 08:06 running ad campaigns and all that but I 08:09 have to do it challenge number two is 08:10 that sometimes you're putting in all 08:12 this work and you're not getting much in 08:14 return especially like in the earlier 08:16 months or earlier years of your business 08:18 you might not be making that much money 08:20 you you might be losing money right 08:22 that's a challenge to stay motivated and 08:24 number three this one is really critical 08:27 it is that everything that goes along in 08:30 the business is your fault everything 08:33 that goes wrong is your fault and even 08:36 beyond that if you do something wrong 08:39 and you break something in the business 08:41 there's no one on the other side that's 08:43 gonna be able to fix things when you're 08:45 at a normal job and something goes wrong 08:48 for instance in software engineers some 08:50 system breaks even if you don't know how 08:52 to fix it you have this sort of mental 08:54 piece that oh some other expert here is 08:57 gonna be able to fix it here that's not 09:00 the case it's only me and my co-founder 09:02 and maybe you know one other person no 09:04 one's gonna fix it for you you got to do 09:06 it that's right you have to really be 09:08 accountable and have a good work ethic 09:10 and understand that it doesn't matter 09:12 how much time you put in in the normal 09:14 job it's just about putting in the hours 09:15 and many times people would just go in 09:18 and work and they're not going to worry 09:19 about being terribly productive all the 09:21 time but when you're running your own 09:23 business 09:23 you really need to make sure that the 09:25 effort that you put in translates into 09:27 real impact into the bottom line and 09:29 oftentimes it's not going to be that's 09:31 something that you really enjoy doing 09:32 sometimes you're going to find out that 09:34 all you want to do is maybe code but it 09:36 turns out that you know that marketing 09:39 is going to be what your company really 09:40 needs at this point and then you have to 09:42 spend all your time studying about how 09:43 to do Facebook advertising or Instagram 09:46 advertising or something like that 09:47 that's a key thing like it especially as 09:50 software engineers we have this tendency 09:52 to want to code code code want to build 09:54 sometimes you got to stop building and 09:56 you got to start maintaining and don't 10:01 sneak up on me like that now I hope 10:02 you've enjoyed part one of two of this 10:05 interview for the stunning and epic 10:07 conclusion to this interview head on 10:09 over to Clements channel is going to be 10:11 great link in the description below and 10:13 I'll see you over there English (auto-generated)

How to Make $40K Per Month in Your 20's: Building a Side-Business

Ex-Google Tech Lead shares his experience in growing a business from 0 to millions of users fast, and his top tips for you to get going too. All too often, we focus too much on the product we're building, without thinking about the marketing problem.  But it turns out that marketing is one of the larger (if not the largest) challenge in starting a business. What if, when considering a business opportunity, we were to focus more on the challenge of gaining customers, rather than the challenge of the product? A business may have hundreds of products, half of which will fail, and most of which will be discontinued within a few years.  For many businesses, it is not about the product, but about the brand marketing power that generates revenue allowing re-investment into improving a mediocre product over time until it becomes good.  Many excellent products fail, and many bad products succeed. Don't underestimate marketing, make it part of your business plan. Also check out the site we built for TechLead: Season 1 HD Complete at http://techleadpro.com Get 82% OFF for Web Hosting and FREE Domain included! Join ex-Google/ex-Facebook engineers for my coding interview training here: https://www.hostinger.com/techlead http://techinterviewpro.com/ Watch 100+ programming interview problems explained: (20% off now, limited time) https://coderpro.com/ Sign up for my FREE daily coding interview practice: http://dailyinterviewpro.com/ Learn how I built a $1,000,000+ business on YouTube and the behind-the-scenes strategies of running a successful YouTube channel: http://youtubebackstage.com/ Get your 2 FREE stocks on WeBull (valued up to $1,400): https://act.webull.com/k/S4oOH2yGOtHk... My computer/camera gear: http://amazon.com/shop/techlead TechLead "ultra-thin" wallet gift: https://amzn.to/2WNhqEP TechLead custom coffee-maker gift: https://amzn.to/3dxwrzr 🎉 Party up: http://instagram.com/techleadhd/ http://twitter.com/techleadhd/ https://www.linkedin.com/in/patrickshyu/ Disclosure: Some links are affiliate links to products. I may receive a small commission for purchases made through these links. Video Transcript ( Note: This transcript was auto-generated by YouTube and may not be 100% correct.) 00:00 hey template here and welcome to another 00:01 episode now what we're going to be 00:03 talking about today is how to grow your 00:05 next business into a million users now I 00:09 wanted to remind you guys that I am an 00:10 ex-googler 00:12 lead and I have built a number of 00:14 successful apps that have been able to 00:16 get to millions of users we can take a 00:19 look at the dashboard here you can see 00:21 here that this was one of my apps with 00:23 3.6 million users had another app pure 00:26 iPhone app 25 thousand users another one 00:28 with 15,000 users 40,000 users let's see 00:31 and this was another app with 500,000 00:33 users and I have grown all of these as 00:36 well as having worked for larger 00:38 companies in which there were apps with 00:39 many many more millions of users so I 00:42 would like to think that I know a thing 00:43 or two about how to grow a business from 00:45 zero to millions of users and I'm here 00:47 to give you my top 5 tips on how you too 00:50 can do that as well this video by the 00:52 way is sponsored by hosting er comm 00:54 slash tech lead for all of your website 00:56 and hosting domain needs for like 80 00:59 cents per month and this is a pretty 01:00 neat way to get a static website all set 01:03 up for yourself such that you can show 01:05 off your projects that you're doing I'll 01:06 just show you quickly how a hosting girl 01:08 works you come in here they have this 01:09 really nice control panel I've already 01:11 got this domain name that I'm trying to 01:13 use your tech lead procom you can see 01:15 that it's just going to a default 01:17 landing page but I'm going to begin the 01:18 all set up here they have a lot of 01:20 options like MySQL databases PHP myadmin 01:23 and what I'm really looking for here is 01:26 they have integration with WordPress 01:28 which is pretty neat WordPress powers 01:30 30% of the web by the way with and there 01:33 you go installation has been successful 01:35 I can access the site now what I'm going 01:38 to be doing is I'm going to be selling 01:40 my tech lead season when the HD complete 01:42 which you can purchase for 1995 by the 01:44 way and I want to create a really nice 01:46 beautiful landing page for that so you 01:49 know I think this looks really good come 01:51 here and choose what I would like to 01:52 insert I really like how they let you 01:54 just come in here and drop into HTML 01:57 yeah looking good there so now I'm using 01:59 some flexbox to get this great layout 02:01 here now what I'm going to have to do is 02:04 just add in some PayPal buttons alright 02:06 so there you go you can see my final web 02:08 page my land 02:09 page tech lead procom you can check it 02:12 out excellent device excellent videos 02:14 1995 by now through PayPal and you can 02:17 see here I was able to get this shout 02:18 friend all set up very quickly I have a 02:20 website people can visit it there's 02:22 images there's text I got YouTube videos 02:25 I got Pay Pal button I was able to do 02:27 this all without any coding using 02:28 Holsinger comm they'll get you over 80% 02:31 off on web hosting and domain names 02:32 check out my hosting ur comm slash tech 02:35 lead 15% off now one thing that really 02:37 changed my perspective was one time I 02:39 was building this dating website and I 02:41 started researching this and I realized 02:43 that dating websites are actually 02:46 extremely easy to build and they faced a 02:49 certain class of problem known as the 02:50 chicken and the egg problem in which the 02:53 success of a dating website depends 02:55 purely on how many people you can get on 02:57 there that's it it's a marketing problem 02:59 it's not a technical problem at all so 03:02 that made me realize that there are 03:03 certain classes of businesses that sound 03:06 great at a million users but that don't 03:09 really sound good at 10 users or 100 03:11 users right and so the first thing you 03:14 need to understand is that you need to 03:15 come up with a path that gets your 03:17 business from 0 users to 10 users to 100 03:20 users a thousand users and a million and 03:22 so if you think about like a dating 03:24 website it's really not much fun with 03:26 only 10 users or a hundred users or a 03:28 thousand users but once you can get like 03:31 10 million users on there it starts to 03:32 sound pretty fun and this is something 03:34 that anybody can do but it just costs 03:37 huge amounts of investments in marketing 03:39 and advertising to get that going and 03:41 the challenge the trick is how do you 03:44 grow it to that size and this is really 03:46 not a trivial thing so you have to have 03:48 a good marketing plan in place for your 03:50 product so that's the first thing is to 03:52 understand that marketing is a very 03:54 interesting problem and for some 03:55 businesses it is actually the core 03:57 problem for the business itself I 03:59 remember one time I had collaborated 04:01 with a team member to build this 04:03 framework you know when we were building 04:04 that I said well we got to make this 04:06 really cool landing page and sell it to 04:08 the developers and tried to get a lot of 04:10 people using this stuff and then that 04:12 other developer just didn't seem to care 04:13 and all he did was he put up like a 04:15 readme file like just a plain readme 04:17 text file and then he just launched it 04:19 and said oh an email 04:21 marketing campaign and guess how many 04:23 people actually adopted this product it 04:25 was like 1 or 2 almost nobody was 04:27 interested in using this framework and 04:29 essentially that just tanked the whole 04:31 project so even though this was simply a 04:34 piece of code oftentimes the impact of a 04:36 developer especially if you're working 04:38 and say infra is how many people are 04:40 actually using your code how many people 04:42 are adopting that piece of technology 04:44 that you wrote so in more places that 04:46 you may imagine and actually in all 04:48 aspects of life from say your dating 04:50 life to your personal branding to pieces 04:53 of code that you write to how you 04:54 negotiate and to the businesses that you 04:56 grow marketing has a huge impact on 04:59 anything that you do marketing is very 05:00 important and so you just have to make 05:02 that a priority I know we all just want 05:04 to start building the product and that's 05:06 the most interesting and fun part about 05:07 it but marketing is something that 05:09 cannot be ignored you have to take it 05:11 seriously 05:11 whenever I start on a new project 05:13 actually it is usually spurred by a new 05:16 marketing opportunity so if there's a 05:18 new app platform that opens up say 05:20 Facebook apps open up or iPhone apps 05:23 open up that is a brand new marketing 05:25 opportunity it's not so much the 05:27 technology the technology may be 05:29 interesting and cool too but it is that 05:31 distribution part that actually 05:32 motivates me to jump in and start 05:34 building something 05:35 I won't take on the project if I don't 05:37 have a clear idea about how I'm going to 05:39 get the first hundred users when I 05:41 started the panel apps which is my 05:43 time-lapse photography software 05:44 I had already pre identified a small 05:46 community of photographers who are very 05:49 interested in time-lapse tricks getting 05:51 sliders and motion and all of that stuff 05:53 so I knew right away that if I were to 05:55 build a piece of software I could 05:57 advertise straight to that community of 05:59 people and they would be interested so 06:01 you want to look for niches small sub 06:03 communities like subreddits Facebook 06:05 groups in which you'll be able to talk 06:06 and people will listen if you try to 06:09 talk to everybody you speak to nobody 06:11 now the second tip I have for you is to 06:13 write the current trends in distribution 06:16 and there's always a trend going on 06:17 somewhere these days is quite 06:19 interesting I would say that the trend 06:21 is in influencer marketing you can go 06:23 find youtubers Instagram influencers 06:25 people much like myself and you go as 06:28 them to promote your product so the key 06:31 difference here is that I would say we 06:33 are in an air 06:34 of influencers in the past technology 06:36 had largely been driven by platforms you 06:39 had platforms like Twitter Facebook 06:41 Google+ and essentially it would be 06:43 grassroots campaigns in which you would 06:45 brought has a post that post would be 06:47 shared by many friends and then that 06:48 post would eventually go viral it may go 06:51 Varro around hashtags on Twitter so in 06:54 the old days it was scattered friends 06:55 who would share news and then you would 06:57 say things like oh well you got to go to 06:58 Facebook or Twitter and you would talk 07:00 about these large platforms today the 07:03 difference is that we have gelled into 07:05 communities centered around influencers 07:07 and there's not so much the platform but 07:10 it is the influencer who you should be 07:12 talking to that is the person you 07:14 advertise with there used to be 07:16 something called bloggers and you would 07:18 go to these bloggers who ran their own 07:20 little independent websites and you ask 07:22 them to write about your stuff but 07:24 bloggers have kind of faded out these 07:26 days to be replaced by the influencers 07:28 that's who you need to go to that's the 07:30 trend these days and so overall I would 07:31 recommend you check out YouTube Twitter 07:33 Instagram maybe read it find out who the 07:35 influencers are in your specific niche 07:37 and go ask them to promote your stuff 07:40 maybe pay them a little money or 07:41 something like that get that all set up 07:43 for you not the third tip I have for you 07:45 about how you can grow your business is 07:46 to be genuine being genuine is trending 07:51 these days I would say you know in the 07:53 old days used to be all corporate speak 07:55 people hid behind this bill and 07:57 customers seem to appreciate that they 07:59 thought it sounded professional but 08:01 these days there's been sort of a 08:03 backlash against corporatism so this is 08:06 about building a natural relationship 08:08 with your customers your audience your 08:10 viewers how are you guys doing over 08:12 there say hi to your mom for me I want 08:15 to show you lose something that kind of 08:16 surprised me when I first saw this but 08:18 there's something called the style and 08:20 tone guide for large companies and we 08:24 take a look at what Google has here they 08:26 say that even for them officially they 08:28 want you to aim for a conversational 08:30 tone rather than a formal one be human 08:33 let your personality show be memorable 08:36 you can even be a little funny now in 08:38 then they say aim for a voice in tone as 08:40 conversational friendly and respectful a 08:43 voice that's casual and that 08:45 and approachable and you can see that 08:47 this is actually reflected in other 08:48 documentation as well if you check out 08:50 MailChimp at mail chip we've walked in 08:53 our customers shoes using offbeat humor 08:55 and the conversational voice we play 08:57 with language to bring joy to work we 08:59 don't take ourselves too seriously 09:01 we are plain spoken we are genuine so if 09:04 the way you are communicating with your 09:05 customer is very formal and you think 09:07 that's professional it's actually not 09:09 you're actually damaging your brand and 09:11 you are distancing yourself from your 09:13 customer and you're just being very 09:15 corporate faceless non-genuine entity 09:19 and you lose that chance to develop a 09:21 more human personal relationship with 09:23 your customer which your competitors 09:26 probably are doing so that's the current 09:28 trend these days if you're trying to act 09:30 out corporate and professional then just 09:31 stop that right now now my fourth tip 09:33 for you is the optimize your conversion 09:35 funnel so maybe you set up this 09:37 beautiful landing web page you want to 09:39 make sure that as people are entering 09:40 your website you aren't losing them and 09:42 this is something that you have to 09:43 really be mindful of about I want to 09:46 show you some interesting landing pages 09:47 here actually if you take a look at the 09:49 landing page for Amazon it's quite 09:51 interesting actually that when you get 09:53 towards the purchase flow you'll find 09:55 that nothing on the page becomes 09:56 clickable anymore except the continue 09:58 button in which you can continue to buy 10:00 stuff the Amazon logo that banner you 10:02 can't click on it they just remove that 10:04 so you don't keep going backwards 10:06 even this learn more button if you ever 10:08 tap on that it just opens a brand new 10:10 window in the pop-up but it doesn't 10:12 actually redirect me from this site once 10:14 I get into this portion it just follows 10:16 me straight into the portion where I 10:18 have to place an order you want to 10:20 minimize the number of clicks that your 10:22 user has to make if you check out my 10:23 website here I don't even have a cart I 10:25 just asked for your credit card number 10:27 and then there's a Buy Now button right 10:29 there which completes the whole 10:30 purchasing process for you it's one 10:32 click by essentially accessibility is 10:34 something that I think a lot of people 10:36 underestimate and what you want to make 10:38 sure that your site is easy and simple 10:41 to access for anybody and you want to be 10:43 thinking about people like your mom for 10:45 instance with someone like that be able 10:47 to navigate your app your business your 10:49 website and really understand it and go 10:52 through the whole flow for example if I 10:54 were to build a website many 10:55 so I would just use a standard button 10:57 I'm not going to try to customize it and 10:59 make it look all cool and shiny and 11:00 round it because then it doesn't really 11:02 look like a button anymore right and 11:04 people may not know that that's 11:05 clickable and that whole entry should be 11:08 fun simple clean and understandable now 11:10 the fifth point here is you want to 11:12 consider what people like to call the 11:14 viral loop right which is the flow in 11:17 which when the user gets into your app 11:19 or your business or whatever it is how 11:21 are they going to spread that through 11:22 word-of-mouth and you want to make it as 11:25 easy as possible for people to share 11:27 your stuff so don't underestimate 11:28 building out this referral process in 11:30 which you can give people some goodies 11:33 and bonuses in exchange for them sharing 11:36 your service with their friends their 11:37 family you know I have spent tens of 11:40 thousands of dollars on advertising a 11:42 lot of that stuff doesn't really work 11:44 like I'm not sure if I've ever gotten 11:46 any payoff that felt really tangible to 11:49 me for advertising whereas if a product 11:52 is really good then it will be able to 11:54 grow on its own and that is really how 11:56 you get massive amounts of growth right 11:58 if your goal is to get like say five 12:01 hundred thousand users you're not going 12:03 to get to that amount by paying for 12:04 every single user it's just going to 12:06 cost way too much so you have to make 12:08 sure that there's a way for your 12:09 business to grow in sort of a viral way 12:12 exponential way without you having to 12:14 pay for each single person so for a lot 12:16 of the apps and games I make I always 12:18 take into consideration the time to 12:20 build some sort of referral process in 12:22 which people can have a special link if 12:24 they were to share that they would get 12:25 some in-app goodies some virtual items 12:27 virtual goods something that would just 12:29 incentivize people to help grow that 12:31 product let me know what your top tips 12:33 are on growing a business if you like 12:35 the video give the like and subscribe 12:36 and I will see you next time bye

Secrets to Grow a Small Business Without Spending Money

Ex-Google TechLead explains the interview process at Facebook for staff software engineer.  (FYI, this video is a little more technical in nature.) Check out my new project CoderPro ( ) for 50+ coding video explanations to popular interview questions for software engineers. https://www.coderpro.com Join ex-Google/ex-Facebook engineers for my coding interview training: http://techinterviewpro.com/ Videos of 100+ programming interview problems explained: https://coderpro.com/ Sign up for my FREE daily coding interview practice: http://dailyinterviewpro.com/ Learn how I built a $1,000,000+ business on YouTube: http://youtubebackstage.com/ Get 2 FREE stocks on WeBull (valued up to $1,400): https://act.webull.com/k/S4oOH2yGOtHk... My computer/camera gear: http://amazon.com/shop/techlead The TechLead "ultra-thin" wallet https://amzn.to/2WNhqEP The TechLead custom coffee-maker: https://amzn.to/3dxwrzr Join my Discord: https://discord.gg/pFUBUtE 🎉 Party up: http://instagram.com/techleadhd/ http://twitter.com/techleadhd/ https://www.linkedin.com/in/patrickshyu/ Disclosure: Some links are affiliate links to products. I may receive a small commission for purchases made through these links. #techlead Video Transcript ( This transcript is auto-generated by YouTube and may not be 100% accurate.) Note: 00:00 hey welcome back to coffee time with 00:01 your host X Google X Facebook tech lead 00:03 and it occurred to me that I never 00:05 really explained how I got my job at 00:07 Facebook as a staff software engineer 00:09 making five hundred thousand dollars per 00:11 year 00:11 today I thought I would tell you about 00:13 how that interview process went I landed 00:15 this offer about one and a half years 00:17 ago when I was working over at Google as 00:19 a tech lead I might remind you before 00:22 all the drama about my wife leaving me 00:24 happened before I became unemployable 00:26 for bashing Facebook but this may be a 00:28 path that you would like to pursue as 00:30 well at some point in your future maybe 00:32 not now maybe not ever really I wanted 00:35 to explain why might even give you an to 00:37 survive if you know the information if 00:39 you know knowledge if you can pass these 00:40 interviews you should be qualified for 00:42 the job it would otherwise be like 00:44 saying students I say Harvard somehow 00:46 have some secret bit of information that 00:49 is non-public and then they only tell 00:50 that information to their friends and 00:52 then only those people are able to get 00:53 into Harvard and I feel that this 00:55 information disparity is not fair it's 00:57 not fair for people who don't have those 00:59 professional network connections who may 01:01 be from underprivileged communities so 01:03 that's my perspective about giving you 01:05 guys as much information as you can to 01:07 pass these coding interviews 01:08 all right so Facebook generally has 01:10 three different types of interviews you 01:12 can usually tell which one you may be at 01:13 they have coding systems design and 01:16 behavior so the coding focuses on just 01:19 your average sale each code the type of 01:21 questions and what you have to solve 01:22 some coding exercise and that's really 01:24 what's a I'll go pro which I talked 01:26 about it's going to help you get through 01:27 and a lot of junior engineers they 01:29 stumble on this portion or they just 01:31 miss out on a lot of these problems the 01:33 systems design interview is not so 01:35 focused on coding and in fact they'll 01:36 probably get a little bit mad if you 01:38 start coding too much they want you to 01:39 talk about how these pieces of code 01:41 interact with each other and that 01:43 overall architecture of it and then 01:45 there's the behavior portion in which 01:47 they tend to value your ability to 01:48 handle conflict build consensus lead 01:51 projects push impact and overall have 01:53 good collaboration and communication 01:54 skills because overall programming is a 01:57 team sport for myself since I was 01:59 interviewing for a senior role I had one 02:01 coding question two systems design 02:03 interviews and then one behavioral 02:05 portion and in each of these they 02:06 generally do continue to ask you some 02:08 coding questions so it's not like they 02:10 just ask you one let me tell you about 02:11 the coding questions that I had though 02:13 and there's a good thing I took notes on 02:15 these so I can tell you the exact 02:16 questions I was asked and you can think 02:18 about how you may solve some of these as 02:20 well you can just pause the video as we 02:22 go along here the first question is 02:24 given to duplicate binary trees so you 02:27 got tree a and three B and you're given 02:30 a node and tree a find that same 02:32 corresponding node in those B so you can 02:35 think about how you may solve this by 02:37 remember my approach was I would try to 02:39 traverse one tree find the note and then 02:41 traverse the second tree and see if I 02:43 can find that same note but then I 02:45 realized that there was no good way to 02:47 compare the two nodes the interviewer 02:49 kind of stopped me at that point I had 02:51 to step back and think about it and the 02:53 ultimate approach which I think is the 02:55 right one is to just reverse both at the 02:56 same time and when you reach the node in 02:59 a then you know you've reached that same 03:00 node in the second binary tree as well 03:03 but the main trick here is that even 03:05 though most people may have been taught 03:06 to traverse one binary tree at a time 03:08 doing both treat reversals at the same 03:11 time sort of test your mastery of this 03:13 area now the funny thing is for a 03:15 standard interview I think this would be 03:16 the only question but I actually ended 03:18 up solving like three questions in the 03:20 single session so the second question 03:22 they asked was given an array like one 03:25 zero zero two five zero move all of the 03:27 zeros to the right to the end of the 03:29 array and again this isn't necessarily 03:32 so difficult but the challenge is to do 03:34 it in like a single pass linear time 03:36 algorithm make it very efficient and 03:38 come up with the proper time space 03:40 analysis and one brute force technique 03:42 is you can go through the array find the 03:45 first zero and move it to the end go 03:46 through the array find the next zero 03:47 move it to the end and you just keep 03:49 moving these values and that's probably 03:51 going to take quadratic time n square 03:53 time because you got to go through n 03:55 iterations and for each iteration you 03:57 may have to shift and more elements the 03:59 more optimal solution can be done in 04:01 linear time and constant space you keep 04:03 in the index to the last item in the 04:05 array and anytime you find the zero you 04:07 just swap that element with the last 04:09 item and then you move that last index 04:11 one left and you just keep going like 04:13 that and then you can process through 04:15 the whole range it's a pretty ridiculous 04:17 question but you just got to play that 04:18 game 04:19 the next question is check of a string 04:21 of parentheses valid a very common 04:23 question you always get asked this type 04:25 of thing you can either solve that using 04:27 like a 04:27 Hunter but if there are multiple 04:29 different types of parentheses then you 04:30 can use like a stack and when you 04:32 encounter and open the in parentheses 04:34 you push that on to the stack we 04:35 encounter a closing parenthesis you pop 04:37 that off of the stack and you check that 04:39 they match and then there's a follow-up 04:41 question which was to remove all 04:42 unbalanced parentheses another question 04:45 was you're given two binary strings and 04:47 you need to add them manually 04:48 essentially just do a duration using a 04:50 carryover variable that can be done in 04:52 linear time constant space and we go 04:54 over a question similar to this over an 04:56 algo Pro except that they're linked 04:58 lists instead so it's a little bit 04:59 trickier that way and then the last 05:01 question is you are given an array of 05:03 objects small medium and large and that 05:05 you have to sort them in place and you 05:08 know this was a mix of using the proper 05:10 data structures because they weren't 05:11 numbers there's like small medium and 05:13 large objects in there and then coming 05:15 up with the algorithm to sort this 05:17 efficiently the optimal algorithm would 05:19 use no space and it would be linear time 05:21 just do the entire sort in one iteration 05:24 one past I remember the original 05:26 approach I did was first I had a bucket 05:28 of small items and then medium and large 05:30 items combined and I would first go 05:32 through in one pass and move all the 05:34 small items to the beginning and then 05:36 we'll go through a second pass I move 05:37 all the large items to the end and just 05:39 sort the medium and large items so this 05:41 is actually a two pass algorithm so that 05:43 covers the coding and all software 05:45 engineers jr. through senior needs a 05:47 known coding you're gonna be smoked on 05:48 this no matter what level you're at 05:50 which is why it's important to keep your 05:52 skill sharp with algo procom now the two 05:55 systems design questions I got were both 05:57 pretty similar and it's totally going to 05:59 depend on the area that you're in right 06:01 for me I'm an iOS mobile developer so it 06:04 was about building an iOS app 06:05 specifically it was number one design a 06:08 flight booking app and number two design 06:10 a simple version of Instagram so both of 06:12 these questions are about having 06:14 multiple pages or surfaces in an app 06:16 there could be dozens of teams working 06:18 on these and then architecting the app 06:20 structure in the way that multiple 06:21 people can be working on this and then 06:23 handling things like caching offline 06:25 usage event navigation scroll 06:27 performance layout removing inter 06:29 dependencies between different pages for 06:31 the flight booking application the idea 06:33 is that you first search for a set of 06:34 flights you see a list you choose a 06:36 flight and then you can buy the flight 06:37 similarly for the Instagram one is like 06:40 you 06:41 have a bunch of photos then you can 06:42 click on the photo you see the details 06:44 and it's like a two-page app you can 06:47 really go in any direction that you want 06:48 in these systems design interviews is 06:50 super open for me the areas I drove into 06:53 talking more about we're handling 06:54 offline usage scenarios how do you catch 06:57 that stuff 06:58 separating dependencies between surfaces 07:00 so for example the flight booking app 07:02 you may have a payments team that is 07:04 handling the payment view for buying the 07:06 airplane ticket but then you have 07:08 another team that's handling search and 07:10 then another team that handles 07:11 displaying the list of flights and it's 07:14 like how do you structure the 07:15 application in a way such that all of 07:17 these can be independent of one another 07:19 and yet they're able to function 07:20 together and here I will talk about 07:22 having different event handlers 07:24 separating modules out such that they're 07:26 not dependent upon one another and 07:28 coming up with that module dependency 07:29 graph and I had to sort of back step 07:31 they're taking their feedback and during 07:33 the interview I actually realized an 07:35 even better architectural solution that 07:37 we hadn't figured out over at Google 07:38 that Facebook had been implementing and 07:40 they probably just appreciated that I 07:43 was able to collaborate with them to 07:44 solve that right there and then there 07:46 are also questions about holistically 07:48 structuring the app in a way that could 07:50 be suitable for both offline and online 07:52 use and then making the right 07:53 abstractions that say the network layer 07:55 and then I also talked about the UI as 07:57 well so that covers what a mobile 07:59 systems design interview may look like 08:01 for a web it will probably be very 08:02 different for example they'll probably 08:04 be about load balancers databases 08:06 master-slave replication sharding CD ins 08:09 and all of that I think what really 08:11 helped me though was really being more 08:12 interested in other parts of the code 08:14 base rather than whatever I have been 08:16 assigned right like usually people are 08:18 saying to work on one small feature and 08:19 they never take a step back and look at 08:21 how their feature interacts with 08:23 everything else and get an overview of 08:25 the entire code base that they're 08:26 working on if you can take a step back 08:29 and take a look at that that could 08:30 prepare you well for any systems design 08:32 interview that may be coming your way at 08:34 some point maybe now or in the future 08:36 and then lots of other the behavior 08:39 questions which we cover in far more 08:40 depth over in our other program Tech 08:43 interview program where we covered the 08:44 entire interview process start to finish 08:47 but the behavioral questions they really 08:49 dig and they don't accept your first 08:52 answer in fact they're trained not to so 08:54 if they ask you like what 08:55 the most challenging part about this and 08:56 you give some shallow answer like oh 08:58 yeah working with this person and then 09:00 it overcame this challenge they know 09:02 that that first answer 09:03 it's probably like a BS answer that you 09:05 have prepared so they really dig deep 09:06 and this is where it helps to really 09:09 have good examples 09:10 I prepared a number of stories myself 09:11 about the only with conflict tough 09:13 situations at work and I think that for 09:15 this area it also helps you just have 09:16 some good concrete examples which is 09:19 another reason that in whatever role 09:21 you're in it still helps to be pushing 09:23 yourself challenging yourself to do more 09:25 such that it can be something you can 09:26 talk about as you're interviewing for 09:28 your future roles so there you have it I 09:30 remember leaving the interview feeling 09:31 quite positive about it and then two 09:33 weeks later I would receive the offer 09:34 five hundred thousand dollar salary and 09:36 there was still kind of a hard decision 09:38 for me to leave Google to take up that 09:40 offer because I was quite comfortable 09:42 over at Google in fact I felt I was 09:44 probably getting a little bit too 09:45 comfortable just sitting back the idea 09:47 of learning a whole new codebase new 09:49 technologies it just seemed really 09:51 exciting to me at the time so I made 09:52 that switch turned out later to be one 09:55 of the biggest mistakes of my life but 09:57 that's another story 09:58 so that good for me it was a little bit 10:01 more of a technical video but I gotta 10:03 keep my street cred up as the tech lead 10:04 if you liked the video give it a like 10:06 and subscribe and I'll see you next time 10:08 Thanks bye

'How I got a $500K job at Facebook (as a software engineer)' - TechLead

Few months ago Canada's Federal Court issued the country's first pirate 'site' blocking order. The order was requested by Bell, Rogers, and Groupe TVA, who recently asked the court to amend the order to ban additional domains that provide access the pirate IPTV service GoldTV. This request was granted. Despite attempts from the rightsholders to keep the update quiet, the new domains have been revealed as well. Last November Canada’s Federal Court approved the first in the country. piracy blockade Following a complaint from major media companies Rogers, Bell and TVA, the Court ordered several major ISPs to block access to domains and IP-addresses of the pirate IPTV service GoldTV. A few days after the order was issued the first blockades were active. These prevented GoldTV customers from accessing the IPTV portal directly, as intended, but it didn’t take long before several popped up. alternative domains These new domains are managed by GoldTV or its resellers and point to the access portal, allowing subscribers an unblocked route to access the IPTV service. This wasn’t entirely unexpected. While IPTV blockades are relatively rare, we have seen similar ‘proxy’ workarounds in the past when traditional pirate sites were blocked in other counties. Having learned from this experience, the Canadian court order specifically allowed Bell and the other companies to expand the blocklist. Specifically, they can amend the original blocklist with any “domain, subdomain or IP address that has as its sole or predominant purpose to enable or facilitate access to the Target Websites,” provided that the IP-address is “not associated with any other active domain.” Such an update was requested early last month and two weeks later the Canadian Federal Court approved it. An overview of the new blocking requirements was published this week by Andy Kaplan-Myrth, TekSavvy’s vice-president of regulatory affairs. This shows that, after some IP-addresses and a domain name were previously removed, several new ones were added with the latest order. The newly added addresses include gold.myiptvplanet.com, live4k.online, and several pctvhd.net and beex.me subdomains. When we checked these, all indeed redirected to the GoldTV access portal. According to reports we received, the new domains have been added to the blocklist of several Canadian ISPs, as expected. Avvidavids reveal that the new domains were tracked down by posing as a customer or reseller of the GoldTV service. Interestingly, the rightsholders asked to keep the names of the new domains secret until the order was granted. The Wire Report that they sent a to the ISP asking them to “refrain from publicizing” the new domains until the Court made a decision. notes letter (pdf) Keeping possible updates out of the public eye is in the interest of the copyright holders, as it prevents GoldTV from anticipating new blocks. However, it raises concerns among some legal experts who believe that information in a public case should be out in the open. If not, that should be up to a court to decide. That said, the Canadian procedure is much more transparent than in other countries such as the UK, where new blocklist updates aren’t published at all, making it impossible for the public to check for potential overblocking. While the expanded blocks are certainly frustrating for GoldTV customers, there will likely be new domains to replace them, continuing the whack-a-mole. The downside for the copyright holders is that there’s a significant delay in the process. Bell and the others first have to file for an amended order, which then has to be approved by the court. After that, it can take up to two weeks before ISPs implement the blockade. This whole process can take more than a month. In this timeframe, new domain names may have already been put into use. While website blocks are far from perfect, the continued frustration of switching to new domains may be enough for some pirates to throw in the towel. Or they may switch to more permanent circumvention alternatives, such as VPNs. Meanwhile, the bigger blocking battle continues as well. Internet provider TekSavvy has and hopes to have it overturned. It clearly violates network neutrality and undermines the open Internet, the ISP previously said. appealed the blocking order Originally published as “ Canadian Pirate Site Blockade Expands With New Domains ” with the Attribution-NonCommercial 3.0 Unported (CC BY-NC 3.0) license

Canadian Pirate Site Blockade Expands With New Domains

To understand this article, you need to know the basics of variables in programming, preferably C since that is what I will be using. While attending my first programming course at university, there was a fear among us students about what was to come. The pointer. The pointer had a rumor for being hard to learn and unnecessary since modern languages handle them for you. But understanding how pointers work, is essential for a programmer since they will use them all the time without even thinking about it. What is a pointer? A pointer is a kind of datatype that keeps tracks of wherein the computer’s memory a specific value is stored. Think of the pointer as a handle for a variable and without this handle, the computer would lose track of it. The difference between pointers and a normal data type such as is that a pointer can only hold a memory address while an holds an actual value. This might sound weird, but follow along and I'll make it more clear. int int When and why are pointers used? Pointers are often used when working with bigger sets of data that need to be manipulated or when memory management is very important. Pointers will reduce the amount of memory required to do certain things such as working with recursive functions or when passing big data around. As you might know, when sending a variable to a function it creates a local copy of the variable in that which could result in big memory waste further down the road. So instead of passing around bigger variable/struct that could be ex. 100 Bytes, we can instead pass around a pointer that contains a reference to the variable/structs memory location. Since a pointer is 8 bytes, this is often beneficial because they use a lot less memory. function instance How to create a pointer? To kickstart your understanding, I will jump straight into the code and explain afterward what is happening. { Luke = ; * Henry; Henry = &Luke; ( , Henry); ;
} int main () // Declaring and initializing the variable Luke int 22 // Declaring the pointer Henry int // Initializing the pointer Henry printf "The pointer to the variable Luke is: %p" return 0 For demonstration purposes we will use: and to understand the concept more easily. Luke the variable Henry the pointer At first, I created a normal named Luke and assigned the value 22 to it, just as one would normally do. int I then created another but with an immediately after. This signals the computer that the int variable that we just created named Henry, is a pointer that will point at a specific int value in the computer's memory. This could be done with any data type: int * (asterisk) { * name; * age; * radius;
} # include <stdio.h> int main () char int double When declared, we never gave any directives about where to point, so right now, Henry is pointing in a random direction. At this point, Henry is whats called a . To give Henry somewhere to point, we can assign him the memory location of Luke the variable, by typing . Henry the pointer wild pointer Henry = &Luke When telling Henry where to point, you might have realized that I used a before Luke the variable. The ampersand is used in front of a variable to get its address in memory.  When this step is done, we have successfully created a pointer to the memory address where the value 22 is stored. & (Ampersand) The output of the function above would have been something like: The pointer to the variable Liks is: 00B3F98C This example was made using an int, however, the same technique applies for floats, chars, structs, and so on. How does a pointer work? Now that we know how to create a pointer, let's try to more deeply understand how they actually work, else there would be no point ;) { Luke = ; * Henry; ;
} # include <stdio.h> int main () int 22 int return 0 The image & code above are equivalent. We declared and initialized the variable Luke and declared the pointer Henry. Henry is now a wild pointer and to make him point at the same memory address as Luke, we simply set Henry = &Luke as before. By doing this we have successfully made Henry aware of where in the memory Luke stores his value. How to use a pointer? Until now you have learned how to declare and initialize a pointer but not how to use it really. Let's say that we want to print the value that Henry is pointing at, how would we do such a thing? Take a look below: { Luke = ; * Henry = &Luke; ( , *Henry); ;
} # include <stdio.h> int main () int 22 int printf "The value at the memory location that Henry points at is : %d" return 0 As you might has noticed I used the in front of the pointer Henry when printing him. This is how we "dereference" a pointer, with other words, actually looking at the value the pointer is pointing at. In this case, we would print the value 22 since that is what Henry is pointing at. * If you are struggling to understand why Henry is pointing at the value 22, I would recommend you to take another look at the images & code snippets above. Pointers in functions A pointer can be sent as a function parameter and then be manipulated inside the function and stay that way without having to return the value afterward. Below I will show the difference in working with/without pointers. Without pointer: { Luke = ;
	Luke = changeValue(Luke);
} {
	value = ; value;
} # include <stdio.h> int main () int 22 int changeValue ( value) int 31 return With pointer: { Luke = ;
	changeValue(&Luke); ( , Luke);
} {
	*value = ;
} int main () int 22 printf "%d" void changeValue ( * value) int 31 In the example with using a pointer, we sent the memory address of Luke to the function and then manipulated the value at the memory location by dereferencing the pointer and setting the value. By doing this, Luke's value is now changed without having to return the value. changeValue() Makes it possible to return more values By using pointers, it's possible to return more than one value from a function. Since we can change the value of a variable by manipulating its memory, we could can do stuff like this: Summary: Pointers is a data type that holds memory addresses to values in memory, often other variables or structs. Pointers are used to reduce memory usage and speed up the execution time in applications, especially when working with bigger sets of data. To create a pointer you will have to put an after the data type declaration, ex . This is how we tell the computer that we are creating a pointer and not a variable. The same operator is used when dereferencing a pointer to get the actual value that the pointer is pointing at. * int* age; When getting the memory address of a variable/struct we use the operator before the variable name, ex . & &age Pointers are very useful when working with bigger sets of data or applications that rely on recursive functions. This is because pointers can increase the execution speed of those programs. Final words I hope that this increased your knowledge about pointers and why they are used. The reason for writing this is because I see people struggling with pointers a lot and thought I should try to pedagogically teach how they work. Programming is not impossible to learn, it is all about time and dedication. Everyone can code, all other statements are wrong. Thanks for me, I'm Eric, a computer science student at Mälardalens Högskola, Sweden.

How To Use Pointers in C

As much as want to take credit for this post this was mostly written by . It was real good and helped me a lot and I wanted it to be shared with the world. John Pipkin Click here for his full article So testing generators it’s best to think of them as loops that execute when you tell them to. Step 1 it(‘should return 6’, () => {// we’ve set up the generator, but we haven’t called next yet so we’re not at a yieldconst gen = count() expect(gen.next().value).toEqual(call(addNumber, number, 1)) expect(gen.next(1).value).toEqual(call(addNumber, number, 2)) expect(gen.next(3).value).toEqual(call(addNumber, number, 3)) expect(gen.next(6).value).toEqual(put(something(6)))}) function *count() {-> // We haven’t told the generator to exicute anything yet so we’re not at a yieldlet number = 0 number = yield call(addNumber, number, 1)number = yield call(addNumber, number, 2) //3number = yield call(addNumber, number, 3) //6yield.put(something(number))} In this step we haven’t told the generator to do anything yet, so we don’t have anything to test. Step 2 it(‘should return 6’, () => {const gen = count() // This next is called, we’re seeing what the yield will beexpect(gen.next().value).toEqual(call(addNumber, number, 1)) expect(gen.next(1).value).toEqual(call(addNumber, number,2)) expect(gen.next(3).value).toEqual(call(addNumber, number, 3)) expect(gen.next(6).value).toEqual(put(something(6)))}) function *count() {let number = 0 // Generator is paused here, waiting. The yield call(addNumber, number, 1) hasn’t executed-> number = yield call(addNumber, number, 1)number = yield call(addNumber, number, 2) //3number = yield call(addNumber, number, 3) //6yield.put(something(number))} Here we’ve executed . We’ve told the generator to go the yield statement and wait. So now we’re paused at the , but we haven’t actually ran the code. gen.next() -> When we get here we’re just getting what the yield WILL do. gen.next().value Step 3 it(‘should return 6’, () => {const gen = count() expect(gen.next().value).toEqual(call(addNumber, number, 1)) // called next here, this evaluated the previous line. We pass in the return value from the last lineexpect(gen.next(1).value).toEqual(call(addNumber, number, 2)) expect(gen.next(3).value).toEqual(call(addNumber, number, 3)) expect(gen.next(6).value).toEqual(put(something(6)))}) function *count() {let number = 0 number = yield call(addNumber, number, 1)// We evaluated the previous line, now were waiting at the this yield-> number = yield call(addNumber, number, 2)number = yield call(addNumber, number, 3) //6yield.put(something(number))} Here we’ve called again. The generator sees that command and executes the yield that it was paused at and continues the next `yield` statement. It will pause here . tells the yield statement it was at to execute, we can pass what we want returned from that into the callWe were paused at , we wanted that to return so we pass that in when we actually execute that line. gen.next() -> gen.next() yield call(addNumber, number, 1) 1 Step 4 it(‘should return 6’, () => {const gen = count() expect(gen.next().value).toEqual(call(addNumber, number,1)) expect(gen.next(1).value).toEqual(call(addNumber, number, 2)) // Called next again, we evaluated the call to (number, 2) and specifiy its return value in this nextexpect(gen.next(3).value).toEqual(call(addNumber, number, 3)) expect(gen.next(6).value).toEqual(put(something(6)))}) function *count() {let number = 0 number = yield call(addNumber, number, 1)number = yield call(addNumber, number, 2) //3-> number = yield call(addNumber, number,3) //6yield.put(something(number))} This one is just like the previous step, just to illustrate what I’m talking about. The yield to should return so we pass that in to the call to because we’ve told the generator to execute that line and we want it to return . call(addNumber, number, 2) 3 gen.next(3) 3 Step 5 it(‘should return 6’, () => {const gen = count() expect(gen.next().value).toEqual(call(addNumber, number, 1)) expect(gen.next(1).value).toEqual(call(addNumber, number, 2)) expect(gen.next(3).value).toEqual(call(addNumber, number, 3)) // Called next again, we evaluated the call to (number, 3) and specifiy its return value in this next.// I’ve intentionally returned the wrong value from the call to (addNumber, number, 3) to illustrate how the return in next worksexpect(gen.next(8).value).toEqual(put(something(8)))}) function *count() {let number = 0 number = yield call(addNumber, number, 1)number = yield call(addNumber, number, 2) //3number = yield call(addNumber, number, 3) //6-> yield.put(something(number))} We’ve called again so now we’re waiting at the yield to put. In this example you can see I intentionally returned the wrong value `8` in . This is to illustrate that next takes in the return value of the previous execution. Essentailly mock data in this case. Now we see that the yield we’re paused at is the . Since in this case is (because that’s what we told to return, that’s what we’re looking for. gen.next() gen.next() put(number) number 8 call(addNumber, number, 3) Step 6 it(‘should return 6’, () => {const gen = count() expect(gen.next().value).toEqual(call(addNumber, number, 1)) expect(gen.next(1).value).toEqual(call(addNumber, number, 2)) expect(gen.next(3).value).toEqual(call(addNumber, number, 3)) expect(gen.next(8).value).toEqual(put(something(8))) // Finally call next again to see there are no more yieldsexpect(gen.next().done).toBeTruthy()}) function *count() {let number = 0 number = yield call(addNumber, number, 1)number = yield call(addNumber, number, 2) //3number = yield call(addNumber, number, 3) //6yield.put(something(number))->} Finally, we call again. Since there are no more yields to wait for we can see the saga is done. gen.next()

Testing Redux Sagas

One woman’s experience with the power and backlash of speaking up. I achieved in the middle of a Facebook usability study. rock bottom in confidence Things had been rough at work for a while. I kept clashing with a couple colleagues — it felt like when about the things I felt were important, . I tried to speak up it was taken as a challenge of their authority I tried getting smaller and quieter for a couple months to temper their response. Instead of making things easier, I felt like the negative intensity of those relationships increased. My productivity dropped. I felt less confident in not just speaking out for the user, but also less confident in my work in general. When body starts to hunch, the head pulls your neck and spine down an additional 10 lbs for every extra inch you bow it. That tension tightens up your back, locking down your muscles, curling your shoulders further forward. The movements are all protective, the instinct is understandable. But pretty soon you aren’t able to straighten up fully anymore. When I collided with rock bottom, I had just finished day one of a two-day usability study in Facebook’s Menlo Park offices. I was the moderator, sitting with the participants, facing 5 cameras, a panel of one-way glass, and my colleagues on the other side in an observation room. I was sweating in front of the glass, uncomfortably on guard and fumbling through each interview. After each session I headed into the observation room and had a terrible conversation with the colleagues I was having issues with. At some point I stopped talking. I just finished the day. I went home and a couple beers. I put on Enya. Lord knows why. And then I gave myself the worst haircut in the whole fucking world. We’re talking a kinda haircut. “bathroom sink,” “no compliments, just apologetic glances,” “high fives from the punk teen on Caltrain” It was terrible. We’re talking the kind of terrible where “design peers inquire quietly, just in case it was a hot mullet trend from the Netherlands they should already know”. I woke up, pulled on a t-shirt, and I with its fluorescent lights and one-way-glass.   All I remember thinking was — this is it. There is no hair to hide behind anymore. marched that haircut right back into the usability lab Boom motherfuckers. Now you will see the real thing. Shortly after the world’s worst haircut, I also tried to dye it blue. And then popped a tire commuting in a storm. The color melted out. When it rains… The Infallible Logic of Terrible Hair That auto-haircut was the best thing that could have happened to me. Terrible hair means you’re already feeling exposed. People are already looking at you like you’re an alien interloper. . You stop flinching when someone raises an eyebrow I found my confidence returned immediately. If I had relevant data or an opinion to add, I spoke up about it. Big meeting, small meeting, it didn’t matter. If half the room was already looking at the hair, why not add some data? Even better, the bad-hair made me impervious to anything but logic. the team shouldn’t trust my suggestions or opinions without testing them — . But I felt confident surfacing my research, questions and concerns because those are things we should be working on together. Of course just look at this hair Speaking up for data, for the user, for the team — or beneficial for the company. a healthy workplace empowers people to speak up for things they think are important You don’t need to give yourself the world’s worst haircut to gain confidence speaking up at work. You just have to to do the right thing. believe in the quality of your work, and your responsibility to your user and your team What’s Worth Speaking Up For? Companies aren’t people. Teams don’t think empathetically like humans. Organizations aren’t necessarily looking for compounding issues like concept or usability problems. Sometimes things look fine in the numbers, but something is deeply wrong with the experience. Your value at a company is your mind — as well as your work. Adding your voice where it matters is part of your responsibility. Of course, if you’re always on a soapbox shouting about something, your voice will lose its urgency and weight. It is helpful to have an internal read on things that are important enough to invest your social capitol in. Here are a few things that I generally find important enough to speak up for: — I view my job on the team as an advocate for the user — advising the design, checking impact with data, and helping the user achieve their goals. User needs — sometimes engineering goals conflict with improvements to user experience or usability. I make sure to share information about the impact of these issues and relative benefit of addressing. Project Prioritization — I spend time identifying and calling out good work and rigorous decision making among colleagues. I try to reference people’s ideas, research, designs or data, and assign credit where I can. Especially for women, this is an important part of career advancement, and one that you can help with easily if you already feel confident speaking up. Credit and excellence among colleagues Invite People In, Don’t Just Shop Theories When you speak up in a meeting, your goal should be to . voice concern or opinion, present data, and encourage action Too often work conversations can devolve into people presenting their ‘side’, and then others on the team treating it as an argument instead of an exploration. “Voice concern. Present data. Encourage action.” Seek to invite people into your process of figuring things out. It is much easier to approach a skeptic with data and a question than a opinion and a request. — It is much easier to approach a skeptic with data and a question than a opinion and a request. Your solution will likely be more swift and elegant with more minds onboard. Invite people into the process — instead of jumping for immediate action (ex. a vote, a spot in a sprint), do your groundwork first. Float the issue, build understanding, collect support from interested stakeholders, and then call for action. Treat issues like campaigns — by the time your team is sitting down with decision makers to figure out what launches, everyone should be on the same page. Information should have been shared, coffee drunk, and trip-up questions asked before decision-making meetings. Otherwise you run the risk of incompletely informed decisions and ruffled feathers among teammates. Agree before the decision is made Don’t Take it Personally A loudly voiced opinion is like a dog whistle for some types of people. Even on great teams, there will occasionally be people who react to your personality and style rather than the substance of your point. . That kind of feedback is stupid, and it hurts, but it shouldn’t stop you from speaking up. Especially among women, being outspoken or forward with your opinion can be read as “aggressive” or “combative” Here’s a pretty spicy Facebook performance review from a colleague who couldn’t separate my style from my results. I’m guessing from the subjective nature of this feedback, guy might not have liked me personally. But this kind of feedback doesn’t stop products from shipping — after this performance review, I was given a promotion, a raise, more stock, and a transfer to a different team. I share this to show you that and company. even negative feedback won’t sink your ship as long as you’re speaking up from a place of respect, data, and concern for the user Here are a few ways to temper subjective, negative reactions you might encounter. — Meet people on your team and invest in getting to know them a bit personally. If people know where you’re coming from and trust your intentions, they’re less likely to react negatively. A large, group meeting is not the place to both introduce yourself and your controversial opinions on the product. Invest in personal relationships — If someone shuts you down when you voice your a concern or opinion, make damn sure they used logic and data to cancel out your point. Otherwise, speak up again to say your point still holds water. Speak up for yourself — If you’re pointing out a big flaw or concern, helps to jump into the emergency response. As a researcher I try to collect a list of supporting information that can help the team start to figure out first steps, and coordinate follow-up research to gauge the size/cause of the problem. Don’t just lob bombs, help catch them Speak Up! What are your tips for advocating on a team, and diffusing tense situations? Please add your wisdom to the comments!

Stories, News & Mentions about BEEX

Beex’s Stories on HackerNoon