Some feedback: calling out that some of us could use our learning budget for Taro was a really nice move. I have learning budget and never have anything to spend it on. Well done.
@@AdityaDhulipalaTrojan It's usually a fixed budget (let's say $1k/yr) which you can spend on any educational resource such as a course or Taro's membership which will help you grow in your career.
This video is good and has some great points about the benefits of being proactive and finding ways to use new technologies in your work. The one issue I take with this video is that it may encourage young engineers to try to do extra work outside of working hours, which can lead to burnout if overdone. Work outside of regular hours happen, and we can't avoid it sometimes, but I encourage engineers to try to get this extra work during the day (following his first tip of decluttering). Spending a weekend working on a new feature that nobody was asked for is a gamble where you wager your free time in exchange for maybe getting recognition. In short, loved the video, but caution young developers to not try to sacrifice too much free time for work.
This is what stuck out to me the most. Besides, if my significant other caught me working my 9-5 on a Sunday he'd drag me away from that laptop so fast lol There's a non-zero amount of successful engineers who sacrificed a lot of their own time to build something foundational in the space but their personal lives were in the trash, they'd have public breakdowns in a commit of their open source project, have deadly substance abuse problems, etc. It ain't worth it, it's just code.
"it may encourage young engineers to try to do extra work outside of working hours" There's no way around it, in particular in a field that pushes the limits of what we can do with technology. This is not a field for 9-5. This is not to say we should become workaholics, but there's no way to keep up to day with changing technologies by not doing work outside of working hours. In fact, I would not even call it "work" outside of working hours, but "investment" in one's skill sets. The important thing here is a need for balance. Sticking to 'working hours' is not balance, however. It's just a low-end extreme (compared to the high-end extreme of being a workaholic.)
@@SacredCASHcow Well, yeah, that's what you do if you want to invest in your skill set. If you don't want to invest in your skill set, then do it. But don't call it "toxic productivity" just because you don't do it. It's not like listening to podcasts is going to kill your free time. I spend 1 hour commuting every day, and I can choose to just listen to music, or a podcast. When I am eating lunch at work, I can spend the time idle, or listening to a podcast or reading a book or blog. Four hours on a pet project is about one hour four days in a week, or about 34 minutes every day in a week (about the same time one uses to watch a TV show.) It's all about priorities, and it is toxic to call it "toxic" just because someone sees self-learning differently from how you see it. Also, this is not unique to people in software. Doctors, veterinarians, nurses, knowledge workers, educators, etc. They all invest some time in updating skills. This is not to say that being a workaholic is good, but spending 4 hours in a pet project or listening to a podcast is somehow "toxic productivity." Don't hate priorities different from yours. Be at peace with your own priorities and choices. Then you'll find yourself not having a need to label others' priorities as "toxic."
@@SacredCASHcow "And now this is the new "bar" and the standard has been raised." That's how the bar has been forever. It was like that when I started in software in 95, and it was like that when I worked as an accountant before that. It was like that when I worked at Home Depot in my college years (studying for product line tests on my own time so that I could be better at work.) And so on and so on. This neither is new, nor unique to the USA. There are two types of people. Those that make the effort, and those that do not. And it is fine with either as long as the person makes peace with the choices they make or do not make. Do you thing. If you don't want to do the extra time, don't. You know your priorities better than anyone else, so I trust you will make the choices that work for you. Likewise, other people will do differently, and time will tell who gets what.
While I agree with the sentiment, if the shortcuts implementation really took as little work as you say and was just a testament to your bias for action, it sounds like low-hanging (but ripe) fruit that nobody but you knew to pick. While you did everything else right, I feel that in reality the problems that will get people to the next level require much larger and complex solutions. with that, a lot of other factors like prioritization and convincing come into play. In your case, why would they say no when you had the feature ready to ship? A prototype is also one thing but if productionalizing it takes significantly more effort (internationalization, scaling, etc.), then there is a lot more convincing and people skills you need to pick up. It's harder to convince PM/management that you should spend time on something else you think is a good idea when the effort to reward ratio is iffy. But otherwise I overall think this is good advice.
Thanks for sharing that story. I saw a similar thing happen when I was at LinkedIn where an engineer on their own time built a new feature behind a feature flag and then showed product. It was eventually folded into the product. One thing to be wary of is if the feature is so large that it takes a significant amount of time to develop, whether your manager has problems with that. I would hope no but something to consider.
My hackathon project has turned into my company’s flagship product. Wish I could say more, but our beta release is the end of Feb and I can’t go public until then 🤫
He explains what the immature mentality is at 0:30, which is to complain about not having enough opportunities to contribute, instead of redefining the scope and creating one's own opportunities.
I agree. The title is misleading. He explained the title topic confusingly a tiny bit. Most importantly, I’m not interested in listening finding and building your own scope. I clicked this video because I wanted to know the title topic.
Agree on the points made, but the scope also partially depends on luck. It is great that Android released that feature and you happened to be on the team that didn't have it. Most of the time it is not the case. Also an important point to make is that promotion is not one thing. It is not "one thing" that gets you promoted, it is constantly performing at that level once promoted. That means you have to constantly seeks projects like this Android feature, which unfortunately, not always readily available.
"Most of the time it is not the case. " It doesn't matter. There's always something at work that needs fixing or improving. A build system, a design document, a proposal for a bug fix. All of these might benefit from developing some sort of POC on the side. Heck, even humble things like a set of shell scripts to bootstrap a development environment can become tools for helping your organization and raising your level of recognition. And even if there's no recognition, it makes us better at what we do. Everything is a function of luck and timing. The question is whether we are engaged in self-learning to exploit opportunities when luck is there for us to take.
Completely agree with this! Seen quite a few cases of immature behavior my 25+ year career. An example case is when there is a presentation going on an interesting topic, and then somebody interupts and asks if the slides will be shared. Most people dont realize that slides alone does not help in anything and the most important task is to listen in and ask the right questions.
What happens when the manager is a scoundrel and skips your contribution on a stage and acknowledges someone else? How would you recommend handling a situation where you are targeted for raising this issue that your contribution hasn't been recognized. These are difficult questions which is important. Going above and beyond and then your manager recognizing it is a straight line which in reality, in life, most times isn't.
Instead of relying on your manager (sounds like your relationship with them is pretty unhealthy based on them being a "scoundrel" LOL), can you own the narrative through your own updates and big wins? - I've found that having a reliable stream of updates actually makes it easier for others to acknowledge your work. You're basically giving them a perma-link that they can reference in their updates. - Further, your own updates can be (should be) read by leadership, so they start to draw their own understanding of your work and what it is enabling.
Great video, I've been thinking about how people wait for builds to complete just to see how one line change didn't work and they need to rebuild everything to try another value for a long time. I also created small apps to test code faster, but some times it tedious(usually when you have a lot of interconnected dependencies) and I don't know what to do. It really burns me out. P.S. Could you please shoot 1080 in 30fps or 24fps and not 60? There's no fast action in the video for it to be 60 fps, but it downloads and buffers two times slower. Thank you!
Do you think it's possible to rise to a high management or IC position at a FAANG company without a college degree? Do you know anyone whose done this? And will I be looked down upon for not having a tradional degree or does only experience matter?
Yes it’s possible. I’ve worked at Salesforce, LinkedIn and have friends at FAANG+ companies who have gone to Senior, Staff Engineer, and Director level without CS degrees. It takes time and experience. Getting into your first job is often one of the hardest challenges. Once you’re in no one will care about where you went to school much after your hired. Of course, some teams and specializations might care about that more but if you can do the job & deliver, are good to work with that ways in a lot Not against degree, I think they’re useful, but some folks may not have the opportunity to do a traditional 4 year and opt to do a bootcamp to get started. Regardless of what path you take, get ready to be always learning new stuff
Hey Rahul! Quick question, do you think you'll expand Taro from being just SWE focuced to more jobs in tech field like UX Design, PM, UX Research, etc.?
We're starting with SWE and adjacent areas like data engineering, eng management just to make sure we can build a compelling product for them. But would love to expand eventually.
@@cats3xxx general idea is not that easy to transform to a specific list of action items. OP has limited mindset which is specific to engineers in prod team. Checkout his working exp. all in production teams within prod focused companies such as fb and pins
Idk, what he's saying seems pretty useful wherever on the stack you work at. Infra has plenty of trends to get ahead of and implement if they give your team a justifiable benefit.
Just leetcode my dudes ! Payoff is immense. I appreciate the advice but I feel it requires a lot of extra time investment to spot and prototype projects and the outcome is uncertain.
@@omarz5009 social engineerin bro. I believe citadel on your resume will matter more to your next job even if you are a rockstar candidate, sad but true.
THE GOSPEL Moreover, brethren, I declare unto you the gospel which I preached unto you, which also ye have received, and wherein ye stand; 2 By which also ye are saved, if ye keep in memory what I preached unto you, unless ye have believed in vain. 3 For I delivered unto you first of all that which I also received, how that Christ died for our sins according to the scriptures; 4 And that he was buried, and that he rose again the third day according to the scriptures: - 1 Corinthians 15: 1-4 KJV Greater love hath no man than this, that a man lay down his life for his friends. - John 15:13 KJV SAVALATION For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life. - John 3:16 KJV For God sent not his Son into the world to condemn the world; but that the world through him might be saved. John 3:17 Jesus saith unto him, I am the way, the truth, and the life: no man cometh unto the Father, but by me. - John 14:6 KJV Neither is there salvation in any other: for there is none other name under heaven given among men, whereby we must be saved. Acts 4:12 For if, when we were enemies, we were reconciled to God by the death of his Son, much more, being reconciled, we shall be saved by his life. Romans 5:10 But he was wounded for our transgressions, he was bruised for our iniquities: the chastisement of our peace was upon him; and with his stripes we are healed. - Isaiah 53:5 For by grace are ye saved through faith; and that not of yourselves: it is the gift of God: Not of works, lest any man should boast. Ephesians 2:8-9 And saying, The time is fulfilled, and the kingdom of God is at hand: repent ye, and believe the gospel. - Mark 1:15 KJV He that believeth on the Son hath everlasting life: and he that believeth not the Son shall not see life; but the wrath of God abideth on him. - John 3:36 KJV Who hath saved us, and called us with an holy calling, not according to our works, but according to his own purpose and grace, which was given us in Christ Jesus before the world began. 2 Timothy 1:9 For the Son of man is come to seek and to save that which was lost. Luke 19:10 The Lord is not slack concerning his promise, as some men count slackness; but is longsuffering to us-ward, not willing that any should perish, but that all should come to repentance. 2 Peter 3:9 He that believeth and is baptized shall be saved; but he that believeth not shall be damned. Mark 16:16 For as in Adam all die, even so in Christ shall all be made alive. 1 Corinthians 15:22 For scarcely for a righteous man will one die: yet peradventure for a good man some would even dare to die. But God commendeth his love toward us, in that, while we were yet sinners, Christ died for us. Romans 5:7-8 I am the door: by me if any man enter in, he shall be saved, and shall go in and out, and find pasture. John 10:9 That if thou shalt confess with thy mouth the Lord Jesus, and shalt believe in thine heart that God hath raised him from the dead, thou shalt be saved. 10 For with the heart man believeth unto righteousness; and with the mouth confession is made unto salvation. 11 For the scripture saith, Whosoever believeth on him shall not be ashamed. - Romans 10:9-11 KJV For whosoever shall call upon the name of the Lord shall be saved. - Romans 10:13 KJV For I am not ashamed of the gospel of Christ: for it is the power of God unto salvation to every one that believeth; to the Jew first, and also to the Greek. Romans 1:16
Some feedback: calling out that some of us could use our learning budget for Taro was a really nice move. I have learning budget and never have anything to spend it on. Well done.
What’s the “learning budget”? Is that part of the “continued education” benefit at these big tech companies?
@@AdityaDhulipalaTrojan It's usually a fixed budget (let's say $1k/yr) which you can spend on any educational resource such as a course or Taro's membership which will help you grow in your career.
This video is good and has some great points about the benefits of being proactive and finding ways to use new technologies in your work. The one issue I take with this video is that it may encourage young engineers to try to do extra work outside of working hours, which can lead to burnout if overdone. Work outside of regular hours happen, and we can't avoid it sometimes, but I encourage engineers to try to get this extra work during the day (following his first tip of decluttering). Spending a weekend working on a new feature that nobody was asked for is a gamble where you wager your free time in exchange for maybe getting recognition. In short, loved the video, but caution young developers to not try to sacrifice too much free time for work.
Good point
This is what stuck out to me the most. Besides, if my significant other caught me working my 9-5 on a Sunday he'd drag me away from that laptop so fast lol
There's a non-zero amount of successful engineers who sacrificed a lot of their own time to build something foundational in the space but their personal lives were in the trash, they'd have public breakdowns in a commit of their open source project, have deadly substance abuse problems, etc. It ain't worth it, it's just code.
"it may encourage young engineers to try to do extra work outside of working hours"
There's no way around it, in particular in a field that pushes the limits of what we can do with technology. This is not a field for 9-5.
This is not to say we should become workaholics, but there's no way to keep up to day with changing technologies by not doing work outside of working hours.
In fact, I would not even call it "work" outside of working hours, but "investment" in one's skill sets.
The important thing here is a need for balance. Sticking to 'working hours' is not balance, however. It's just a low-end extreme (compared to the high-end extreme of being a workaholic.)
@@SacredCASHcow Well, yeah, that's what you do if you want to invest in your skill set. If you don't want to invest in your skill set, then do it.
But don't call it "toxic productivity" just because you don't do it. It's not like listening to podcasts is going to kill your free time.
I spend 1 hour commuting every day, and I can choose to just listen to music, or a podcast.
When I am eating lunch at work, I can spend the time idle, or listening to a podcast or reading a book or blog.
Four hours on a pet project is about one hour four days in a week, or about 34 minutes every day in a week (about the same time one uses to watch a TV show.)
It's all about priorities, and it is toxic to call it "toxic" just because someone sees self-learning differently from how you see it.
Also, this is not unique to people in software. Doctors, veterinarians, nurses, knowledge workers, educators, etc. They all invest some time in updating skills.
This is not to say that being a workaholic is good, but spending 4 hours in a pet project or listening to a podcast is somehow "toxic productivity."
Don't hate priorities different from yours.
Be at peace with your own priorities and choices. Then you'll find yourself not having a need to label others' priorities as "toxic."
@@SacredCASHcow "And now this is the new "bar" and the standard has been raised."
That's how the bar has been forever. It was like that when I started in software in 95, and it was like that when I worked as an accountant before that. It was like that when I worked at Home Depot in my college years (studying for product line tests on my own time so that I could be better at work.)
And so on and so on.
This neither is new, nor unique to the USA. There are two types of people. Those that make the effort, and those that do not.
And it is fine with either as long as the person makes peace with the choices they make or do not make.
Do you thing. If you don't want to do the extra time, don't.
You know your priorities better than anyone else, so I trust you will make the choices that work for you.
Likewise, other people will do differently, and time will tell who gets what.
Thanks, that is great inspiration for an idea I've been chewing on!
Go for it!
Glad to know that my fragmented episode was helpful! Thanks for the tips 🙏🏿
It was really great, thank you Andrew!
While I agree with the sentiment, if the shortcuts implementation really took as little work as you say and was just a testament to your bias for action, it sounds like low-hanging (but ripe) fruit that nobody but you knew to pick. While you did everything else right, I feel that in reality the problems that will get people to the next level require much larger and complex solutions. with that, a lot of other factors like prioritization and convincing come into play. In your case, why would they say no when you had the feature ready to ship? A prototype is also one thing but if productionalizing it takes significantly more effort (internationalization, scaling, etc.), then there is a lot more convincing and people skills you need to pick up. It's harder to convince PM/management that you should spend time on something else you think is a good idea when the effort to reward ratio is iffy.
But otherwise I overall think this is good advice.
Thanks for sharing that story. I saw a similar thing happen when I was at LinkedIn where an engineer on their own time built a new feature behind a feature flag and then showed product. It was eventually folded into the product. One thing to be wary of is if the feature is so large that it takes a significant amount of time to develop, whether your manager has problems with that. I would hope no but something to consider.
My hackathon project has turned into my company’s flagship product. Wish I could say more, but our beta release is the end of Feb and I can’t go public until then 🤫
Thanks for such a short and very informative video.
Need more stuff like this
Hey! I have a $2k L&D budget I’m trying to spend before the end of the year too! Looks like you are gonna add another Taro user to the ranks! 👍
would love to have you :)
Love you Rahul sir ☺️
We will definitely meet one day 🙌
great content...
Great insights. Thank you for sharing.
Very inspiring!
"This Immature Mentality is Why You Aren't a Senior or Staff Engineer" the title is misleading
He explains what the immature mentality is at 0:30, which is to complain about not having enough opportunities to contribute, instead of redefining the scope and creating one's own opportunities.
I agree. The title is misleading. He explained the title topic confusingly a tiny bit. Most importantly, I’m not interested in listening finding and building your own scope. I clicked this video because I wanted to know the title topic.
That is why he didn't make it to distinguished engineer.
Agree on the points made, but the scope also partially depends on luck. It is great that Android released that feature and you happened to be on the team that didn't have it. Most of the time it is not the case. Also an important point to make is that promotion is not one thing. It is not "one thing" that gets you promoted, it is constantly performing at that level once promoted. That means you have to constantly seeks projects like this Android feature, which unfortunately, not always readily available.
Everything has luck involved. But we don't have control over it. We should atleast work on things that we have control over.
"Most of the time it is not the case. "
It doesn't matter. There's always something at work that needs fixing or improving.
A build system, a design document, a proposal for a bug fix. All of these might benefit from developing some sort of POC on the side. Heck, even humble things like a set of shell scripts to bootstrap a development environment can become tools for helping your organization and raising your level of recognition.
And even if there's no recognition, it makes us better at what we do.
Everything is a function of luck and timing. The question is whether we are engaged in self-learning to exploit opportunities when luck is there for us to take.
"Code speaks lauder than PRDs", I love it.
Completely agree with this! Seen quite a few cases of immature behavior my 25+ year career. An example case is when there is a presentation going on an interesting topic, and then somebody interupts and asks if the slides will be shared. Most people dont realize that slides alone does not help in anything and the most important task is to listen in and ask the right questions.
Very Informative!
@@DeT1ny ok fake Rahul!
Key takeaway is taking initistove for impact: find project, finding an appropriate scope
What happens when the manager is a scoundrel and skips your contribution on a stage and acknowledges someone else? How would you recommend handling a situation where you are targeted for raising this issue that your contribution hasn't been recognized. These are difficult questions which is important. Going above and beyond and then your manager recognizing it is a straight line which in reality, in life, most times isn't.
Instead of relying on your manager (sounds like your relationship with them is pretty unhealthy based on them being a "scoundrel" LOL), can you own the narrative through your own updates and big wins?
- I've found that having a reliable stream of updates actually makes it easier for others to acknowledge your work. You're basically giving them a perma-link that they can reference in their updates.
- Further, your own updates can be (should be) read by leadership, so they start to draw their own understanding of your work and what it is enabling.
@@RahulPandeyrkp only if I knew my manager is a scoundrel. 🙈 thanks, is helpful.
Thumbnail game on point💯
I think this is the first time I can't help but binge on a channel that is not entertainment!
Aww thanks Mehul!
Nice video and thoughts. 😊 Also can you put some more examples about backend engineering as well ?
I have a doubt when you built that feature did you build on the prod app or you made a look a like and showcased how shortcuts work?
I built it in the prod app
Man I love this content , I was looking for it I’m in a situation that I have to deliver a function can help me to get recognized in the company
🔥
I think a better title would be "Watching a Product through a Senior or Staff Engineer Lens"
i'm not a self starter 😢😢😢😢😢 so i don't do extra things.
Feedback: how about impact for cloud services? For products we leverage new api, but for services these don't happen often
why is one sleeve rolled up and the other one down? i'm just curious. isn't it uncomfortable?
Lolz I didn't think about it
Great video, I've been thinking about how people wait for builds to complete just to see how one line change didn't work and they need to rebuild everything to try another value for a long time. I also created small apps to test code faster, but some times it tedious(usually when you have a lot of interconnected dependencies) and I don't know what to do. It really burns me out.
P.S. Could you please shoot 1080 in 30fps or 24fps and not 60? There's no fast action in the video for it to be 60 fps, but it downloads and buffers two times slower. Thank you!
ooh thanks for the tip about the video framerate, I never thought about that
Love the content, as usual. Is Taro just for SWEs, or would an aspiring Eng Manager find useful stuff there too?
Yes I think so. We have a few eng managers and it's useful to see the questions from engineers.
Do you think it's possible to rise to a high management or IC position at a FAANG company without a college degree? Do you know anyone whose done this?
And will I be looked down upon for not having a tradional degree or does only experience matter?
Yes it’s possible. I’ve worked at Salesforce, LinkedIn and have friends at FAANG+ companies who have gone to Senior, Staff Engineer, and Director level without CS degrees. It takes time and experience. Getting into your first job is often one of the hardest challenges. Once you’re in no one will care about where you went to school much after your hired. Of course, some teams and specializations might care about that more but if you can do the job & deliver, are good to work with that ways in a lot
Not against degree, I think they’re useful, but some folks may not have the opportunity to do a traditional 4 year and opt to do a bootcamp to get started. Regardless of what path you take, get ready to be always learning new stuff
@@CliffordFajardo How do you suggest I connect with a FAANG recruiter?
Hey Rahul! Quick question, do you think you'll expand Taro from being just SWE focuced to more jobs in tech field like UX Design, PM, UX Research, etc.?
We're starting with SWE and adjacent areas like data engineering, eng management just to make sure we can build a compelling product for them. But would love to expand eventually.
"Finding and building your own scope" = quit your job and become a freelancer
Moving more towards clickbait titles :/ The content is still good though.
Pinterest is the most overrated underrated product. Thanks for the info though.
not sure I understood overrated underrated :P
This is useful to engineers who work on product team. But not that useful for people working in infra team.
Not true. The general idea is applicable to any engineer
@@cats3xxx general idea is not that easy to transform to a specific list of action items. OP has limited mindset which is specific to engineers in prod team. Checkout his working exp. all in production teams within prod focused companies such as fb and pins
Idk, what he's saying seems pretty useful wherever on the stack you work at. Infra has plenty of trends to get ahead of and implement if they give your team a justifiable benefit.
What's your MBTI type Rahul?
I think I took that assessment in college but I forgot what I am. I'm pretty weary of these personality judgements
Just leetcode my dudes ! Payoff is immense. I appreciate the advice but I feel it requires a lot of extra time investment to spot and prototype projects and the outcome is uncertain.
leetcode engineers are the worst type of engineers. Look at what happened at Uber two days ago.
@@omarz5009 social engineerin bro. I believe citadel on your resume will matter more to your next job even if you are a rockstar candidate, sad but true.
Clickbait, doesn't say anything in relation to the title.
THE GOSPEL
Moreover, brethren, I declare unto you the gospel which I preached unto you, which also
ye have received, and wherein ye stand; 2 By which also ye are saved, if ye keep in memory what I preached unto you, unless ye have believed in vain. 3 For I delivered unto you first of all that which I also received, how that Christ died for our sins according to the scriptures; 4 And that he was buried, and that he rose again the third day according to the scriptures:
- 1 Corinthians 15: 1-4 KJV
Greater love hath no man than this, that a man lay down his life for his friends. - John 15:13 KJV
SAVALATION
For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life.
- John 3:16 KJV
For God sent not his Son into the world to condemn the world; but that the world through him might be saved. John 3:17
Jesus saith unto him, I am the way, the truth, and the life: no man cometh unto the Father, but by me.
- John 14:6 KJV
Neither is there salvation in any other: for there is none other name under heaven given among men, whereby we must be saved. Acts 4:12
For if, when we were enemies, we were reconciled to God by the death of his Son, much more, being reconciled, we shall be saved by his life. Romans 5:10
But he was wounded for our transgressions, he was bruised for our iniquities: the chastisement of our peace was upon him; and with his stripes we are healed. - Isaiah 53:5
For by grace are ye saved through faith; and that not of yourselves: it is the gift of God: Not of works, lest any man should boast. Ephesians 2:8-9
And saying, The time is fulfilled, and the kingdom of God is at hand: repent ye, and believe the gospel.
- Mark 1:15 KJV
He that believeth on the Son hath everlasting life: and he that believeth not the Son shall not see life; but the wrath of God abideth on him.
- John 3:36 KJV
Who hath saved us, and called us with an holy calling, not according to our works, but according to his own purpose and grace, which was given us in Christ Jesus before the world began. 2 Timothy 1:9
For the Son of man is come to seek and to save that which was lost. Luke 19:10
The Lord is not slack concerning his promise, as some men count slackness; but is longsuffering to us-ward, not willing that any should perish, but that all should come to repentance. 2 Peter 3:9
He that believeth and is baptized shall be saved; but he that believeth not shall be damned. Mark 16:16
For as in Adam all die, even so in Christ shall all be made alive. 1 Corinthians 15:22
For scarcely for a righteous man will one die: yet peradventure for a good man some would even dare to die. But God commendeth his love toward us, in that, while we were yet sinners, Christ died for us. Romans 5:7-8
I am the door: by me if any man enter in, he shall be saved, and shall go in and out, and find pasture. John 10:9
That if thou shalt confess with thy mouth the Lord Jesus, and shalt believe in thine heart that God hath raised him from the dead, thou shalt be saved. 10 For with the heart man believeth unto righteousness; and with the mouth confession is made unto salvation. 11 For the scripture saith, Whosoever believeth on him shall not be ashamed.
- Romans 10:9-11 KJV
For whosoever shall call upon the name of the Lord shall be saved.
- Romans 10:13 KJV
For I am not ashamed of the gospel of Christ: for it is the power of God unto salvation to every one that believeth; to the Jew first, and also to the Greek. Romans 1:16
This is cool, but can you reverse a linked list?
Reasons not to have a high position at a company:
() Not knowing powerful people
() Not having a rich background
(X) Bring immature