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

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

BEEX

beex.sg

-- employees

Since n.d.

COMPANY RANKING

BEEX

EVERGREEN INDEX #1870

Representing this company? Click here to claim and customize this page!

BeeX WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

BEEX

beex.sg

-- employees

Since n.d.

COMPANY RANKING

BEEX

EVERGREEN INDEX #1870

RELATED COMPANIESRANK

STORIES ABOUT BEEX

Representing this company? Click here to claim and customize this page!

BeeX WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!