We are happy to announce that Zichao Yuan has joined our team as a Software Engineer. Zichao joins us from Meta, where he spent the last five years specializing in full-stack development. We are continuing to build out our engineering team. You can learn more here: https://lnkd.in/gZr6eHT8
Freed’s Post
More Relevant Posts
-
There are so much opportunities to innovate both on hardware and software side of LLM. Of course, it eventually comes down to revenue. Meta is a profitable public large tech company. Building LLama is in its reach. It's a good strategical move for Meta. I am more excited on hardware innovation. Eventually, this is the driving force to improve producitivity, then eventually economics. Everyone will live better persuming British people had built good theory on macro economics.
To view or add a comment, sign in
-
Completed First Week Of Indroduction to Front-End Devlopment By Meta It is great learning from such a great devlopers of meta .Gives confidence for my career. #coursera #Metafrontenddevlopment #frontenddevelopment
To view or add a comment, sign in
-
Student at Kamaraj College of Engineering and Technology | Front-end | Data Visualization | Intern @ Litz Tech
I'm thrilled to announce that I've reached a major milestone by successfully completing the "Introduction to Front End Development" course by Meta! This journey has been incredibly rewarding, and I'm excited to apply what I've learned. #meta #frontenddevelopment #coursera
To view or add a comment, sign in
-
One problem tho. Code explains when, what, where and how but it never explains why (yes, even with comments). Optimized code isn't readable and readable code is not optimal. I do agree with relationships because the standard senior software engineer ego says "read the documentation" which is in v0.0.1 while the product goes to v3.14.15. Over the period of time, I am seeing less of that and that's a plus. I agree with the final statement as well. I genuinely feel that documentation and proper unit tests help the code soar. It should be built into the development process. Documentation is like legislation, code is executive and unit tests are like judiciary. It should be by the people, for the people and to the people.
At Meta, we had near 0 documentation about how the codebase works, mostly considering it a waste of time. Despite this, most new Meta engineers land code in their 1st or 2nd week. Here's why: 👉 Onboarding engineers are heavily encouraged to talk to their teammates about how the code works. This was far more effective than a static resource and builds up relationships too. 👉 Without the crutch of documentation, engineers were pushed to simply write better code that flowed intuitively and was very readable, even for newbies. 👉 Time spent writing useless docs is time spent not making the product better for the end-user and landing impact. That last point in particular snowballs. The faster you move, the harder it is to write docs explaining the codebase as it's even more of a moving target. All of this is why Meta has some of the highest engineering productivity in the industry with $500,000+ in profit per software engineer. That being said, we did write a ton of documentation at Meta, just not to baby engineers through the code. To learn when Meta engineers did that and what sort of documentation is worth writing in general, check out my in-depth explainer here: https://lnkd.in/gMgngbnF #techcareergrowth #productivity #onboarding #softwareengineering #growthtips
To view or add a comment, sign in
-
Excited to announce my journey into front-end development with Meta's program! Just completed week 1 of their Introduction to Front-End Development course. Sharing to document my progress and foster a supportive community. As someone who enjoys learning multiple skills and being a jack of all trades, this is another exciting chapter in my journey. Here's to continuous learning! 🚀 #FrontEndDevelopment #Meta #LearningJourney
To view or add a comment, sign in
-
-
At Meta, we had near 0 documentation about how the codebase works, mostly considering it a waste of time. Despite this, most new Meta engineers land code in their 1st or 2nd week. Here's why: 👉 Onboarding engineers are heavily encouraged to talk to their teammates about how the code works. This was far more effective than a static resource and builds up relationships too. 👉 Without the crutch of documentation, engineers were pushed to simply write better code that flowed intuitively and was very readable, even for newbies. 👉 Time spent writing useless docs is time spent not making the product better for the end-user and landing impact. That last point in particular snowballs. The faster you move, the harder it is to write docs explaining the codebase as it's even more of a moving target. All of this is why Meta has some of the highest engineering productivity in the industry with $500,000+ in profit per software engineer. That being said, we did write a ton of documentation at Meta, just not to baby engineers through the code. To learn when Meta engineers did that and what sort of documentation is worth writing in general, check out my in-depth explainer here: https://lnkd.in/gMgngbnF #techcareergrowth #productivity #onboarding #softwareengineering #growthtips
To view or add a comment, sign in
-
Just wrapped up the exclusive Gear Up For Meta University 2024 Event Series, and I couldn't be more pumped to share the excitement with you all! I had the honor of joining a stellar panel featuring incredible talents like Keiyana Arnold, MSOM, Vanessa Morais, Nichole Clarke, and Iván Morett. Here's what you need to know 🔑: Dive into Meta U: A world of immersive CS training awaits you in web development, iOS, or Android. Mentorship Magic: Connect with CodePath's expert instructors and mentors to build your tech skills. Learning Nirvana: Engage in small team projects and frequent manager interactions for an incredible learning experience. But wait, there's more 📝: Limitless Possibilities: Meta U is your canvas to paint your journey as an engineer and as an individual. Skill Showtime: Develop leadership, soft skills, and coding abilities that truly matter. This event series reignited my passion for tech and armed me with insights into the exciting world of Meta University. I can't wait to embark on this journey with all of you, equipped with new knowledge and skills. Together, we'll make this journey extraordinary! 🚀💡 #MetaUniversity2024 #LifeAtMeta #meta
To view or add a comment, sign in
-
-
Keeping the code's docs updated is key; they need to stay fresh, especially the big stuff like how it's built or the coding rules. The aim is to keep things light on paperwork, making the code clean and clear enough to speak for itself. And hey, those #to_do or #must_be_implemented tags scattered around without any follow-up? They're just red flags for messy code waiting to happen.
At Meta, we had near 0 documentation about how the codebase works, mostly considering it a waste of time. Despite this, most new Meta engineers land code in their 1st or 2nd week. Here's why: 👉 Onboarding engineers are heavily encouraged to talk to their teammates about how the code works. This was far more effective than a static resource and builds up relationships too. 👉 Without the crutch of documentation, engineers were pushed to simply write better code that flowed intuitively and was very readable, even for newbies. 👉 Time spent writing useless docs is time spent not making the product better for the end-user and landing impact. That last point in particular snowballs. The faster you move, the harder it is to write docs explaining the codebase as it's even more of a moving target. All of this is why Meta has some of the highest engineering productivity in the industry with $500,000+ in profit per software engineer. That being said, we did write a ton of documentation at Meta, just not to baby engineers through the code. To learn when Meta engineers did that and what sort of documentation is worth writing in general, check out my in-depth explainer here: https://lnkd.in/gMgngbnF #techcareergrowth #productivity #onboarding #softwareengineering #growthtips
To view or add a comment, sign in
-
Exciting news I start with Meta tomorrow! A new career & more progression. The goal is to utilise all my past experiences and skill set & become the VERY BEST at what I do! Meta for Business Meta
To view or add a comment, sign in
-
Career, College, and Education Professional specializing in counseling, teaching, resume writing, and LinkedIn profile optimization.
Learn more job search success strategies as a Pathrise fellow! Go to www.Pathrise.com/darren to apply, learn how it works, and to get started. You will receive an optimized job search that will lead to a better job, and with better pay! Yes, it’s FREE until you land a job.
Meta wants candidates to arrive prepared and communicate their experiences as effectively as possible. To level the playing field, Meta shares common questions to prepare. Read the full article to learn more. https://lnkd.in/gYicmxgq
To view or add a comment, sign in
-