Every time I read a blog post about "why we leave the cloud", I never see the actual reason. Most of the time they complain about costs, but never expose their current infrastructure or what is really costing them so much that building their own physical servers with a 24/7 support team makes sense. And my experience with the cloud is that most people doesn't care at all about costs until it becomes an issue, then they go nuclear and remove everything. I've been on AWS since 2017, and always took some time to care about what services I use and how much they cost. If a 200 to 300$ monthly bill is really what makes people moves out of the cloud, then I guess I have no idea how valuable that money is...
It is getting expensive for some organizations. In one of the Snowflake's earnings call they said some of their customers are asking for discounts as they got bills in millions for using their data warehouse.
Whenever I see blog posts about "why we left the cloud", I burst out laughing that they have seen the light. Some businesses especially in third world countries don't have the luxury of shelling out 200 to 300$ monthly bills on servers. I set up max $40/month beefy cloud servers even for applications which rake in millions of USD in revenue. I work with multiple companies, some in first world countries and others in third world countries and often smile at the expensive cloud bills for those companies in first world countries.
Hello I am gonna almost watch all ur videos to just find the answer to my question Which is can a person get an entry level job in the cloud industry without having any cs degree or bachelor's degree like my self I cant afford to buy more than one cert like aws practitioner would a real good 6 projects gets me hired ? Plz if u see this comment be detailed in ur answer so all of us can benefit
A degree is not mandatory, and nor are certifications. Those help in getting you through the doors for interviews, and can matter more or less depending on where you're from. But, they're certainly not mandatory. The main thing to focus on is proving your credibility at your chosen role, and you can do that in the best way via producing tangible, real-world evidence. If you do not yet have experience you need to make it yourself. Do not rely on "gatekeepers" (e.g. hiring managers etc) to "give you" experience. Get creative. Some ideas are to: contribute in open source, and build your own projects that closely resemble the job you're looking to land. Seek freelance experience if you can to build evidence of professional experience. If you're looking to get into a builder role (software engineer, cloud engineer, devops) that means PROVING you can do the job, so create as much proof as possible that you can do the job the employer is hiring for. What I'd suggest: 1. Try to find a role that you're interested in, matching to your existing skills and interests. 2. Build a learning plan (and be ruthless about what you'll NOT learn) 3. Pick 1-3 "projects" (e.g. real-world solutions that you will build) and start to build those out 4. Consider getting some "freelance" experience, e.g. complete some small gigs, or try to 5. Build a portfolio or use your GitHub profile as a portfolio to show off your skills 6. Then hustle to land interviews...get creative in out reach, use social media, linkedin, in person meetups If you really don't know where to start, you could just do: cloudresumechallenge.dev for 3-6 months as a way to get things moving. learntocloud.guide is also a good foundation to start to chew through. For careers stuff, I'd suggest to watch the following videos that were career sessions in a bootcamp I did recently: Picking a role: ua-cam.com/video/E0haz6mymxY/v-deo.html Understanding how to create your resume: ua-cam.com/video/S_89vwVHC9Y/v-deo.html The most important factor that will dictate your success is your dedication, persistence and ability to just sit down each and every day or hour that you have spare and commit to your chosen path. And only you can motivate yourself for that. Good luck !!!
I would also suggest to potentially condense that "6 projects" down into 1-2 that incorporate aspects of the others. Six feels like a lot and I'd imagine you wouldn't go as deep in them as you'd need. Think about how you could pull them all together. Put yourself in the employers shoes, what skills do they really want to see? How do you prove that you'll be effective from day one since you understand a lot about the technologies that they need you to understand. "More" is not necessarily better. Better is better. Pushing 1 or 2 projects to more and more depth is better than being shallow on many different areas.
@openupthecloud Thank u a lot u dont know how much u get it easier on me both answers were completely helpful. Any way I am ur fan from Lebanon 🇱🇧 keep inspiring others by ur videos
Hey folks ! Slightly different video format this time around - what do you say? Yay or nay?
Let me know !👇
Every time I read a blog post about "why we leave the cloud", I never see the actual reason. Most of the time they complain about costs, but never expose their current infrastructure or what is really costing them so much that building their own physical servers with a 24/7 support team makes sense.
And my experience with the cloud is that most people doesn't care at all about costs until it becomes an issue, then they go nuclear and remove everything. I've been on AWS since 2017, and always took some time to care about what services I use and how much they cost. If a 200 to 300$ monthly bill is really what makes people moves out of the cloud, then I guess I have no idea how valuable that money is...
It is getting expensive for some organizations. In one of the Snowflake's earnings call they said some of their customers are asking for discounts as they got bills in millions for using their data warehouse.
Whenever I see blog posts about "why we left the cloud", I burst out laughing that they have seen the light.
Some businesses especially in third world countries don't have the luxury of shelling out 200 to 300$ monthly bills on servers. I set up max $40/month beefy cloud servers even for applications which rake in millions of USD in revenue. I work with multiple companies, some in first world countries and others in third world countries and often smile at the expensive cloud bills for those companies in first world countries.
The world of computer science is really amazing. One day I will be of one its giants and give my shoulder to world.
Yesss ! Rooting for you Yussuf !
"Most models are wrong but somehow useful - representations of reality but short of entire details"
Zactly !
Hello
I am gonna almost watch all ur videos to just find the answer to my question
Which is can a person get an entry level job in the cloud industry without having any cs degree or bachelor's degree like my self I cant afford to buy more than one cert like aws practitioner would a real good 6 projects gets me hired ?
Plz if u see this comment be detailed in ur answer so all of us can benefit
A degree is not mandatory, and nor are certifications. Those help in getting you through the doors for interviews, and can matter more or less depending on where you're from. But, they're certainly not mandatory. The main thing to focus on is proving your credibility at your chosen role, and you can do that in the best way via producing tangible, real-world evidence. If you do not yet have experience you need to make it yourself. Do not rely on "gatekeepers" (e.g. hiring managers etc) to "give you" experience. Get creative. Some ideas are to: contribute in open source, and build your own projects that closely resemble the job you're looking to land. Seek freelance experience if you can to build evidence of professional experience. If you're looking to get into a builder role (software engineer, cloud engineer, devops) that means PROVING you can do the job, so create as much proof as possible that you can do the job the employer is hiring for.
What I'd suggest:
1. Try to find a role that you're interested in, matching to your existing skills and interests.
2. Build a learning plan (and be ruthless about what you'll NOT learn)
3. Pick 1-3 "projects" (e.g. real-world solutions that you will build) and start to build those out
4. Consider getting some "freelance" experience, e.g. complete some small gigs, or try to
5. Build a portfolio or use your GitHub profile as a portfolio to show off your skills
6. Then hustle to land interviews...get creative in out reach, use social media, linkedin, in person meetups
If you really don't know where to start, you could just do: cloudresumechallenge.dev for 3-6 months as a way to get things moving.
learntocloud.guide is also a good foundation to start to chew through.
For careers stuff, I'd suggest to watch the following videos that were career sessions in a bootcamp I did recently:
Picking a role: ua-cam.com/video/E0haz6mymxY/v-deo.html
Understanding how to create your resume: ua-cam.com/video/S_89vwVHC9Y/v-deo.html
The most important factor that will dictate your success is your dedication, persistence and ability to just sit down each and every day or hour that you have spare and commit to your chosen path. And only you can motivate yourself for that.
Good luck !!!
I would also suggest to potentially condense that "6 projects" down into 1-2 that incorporate aspects of the others. Six feels like a lot and I'd imagine you wouldn't go as deep in them as you'd need. Think about how you could pull them all together. Put yourself in the employers shoes, what skills do they really want to see? How do you prove that you'll be effective from day one since you understand a lot about the technologies that they need you to understand. "More" is not necessarily better. Better is better. Pushing 1 or 2 projects to more and more depth is better than being shallow on many different areas.
@openupthecloud Thank u a lot u dont know how much u get it easier on me both answers were completely helpful.
Any way I am ur fan from Lebanon 🇱🇧 keep inspiring others by ur videos