Shawn mels

Day 100 of #100DaysOfCode. This has been an amazing journey, I have learned a lot and still continuing to learn. As I have completed my 100days, I will still continue with Ewomazino Akpareva's course of 100 days of JavaScript. Try out today's project: runningame3000.netlify.app

A Cheat Sheet for Designing Fault-Tolerant Systems.

The three Machine Learning approaches 1️⃣ Supervised learning 2️⃣ Unsupervised learning 3️⃣ Reinforcement learning 🧵 1/6

To come ahead on your next AI/ML interview: • Pick a problem • Build a model • Wrap it in a simple API • Host it • Build a small app that uses it • Set up monitoring • Write about all of this Do this, and you'll be ahead of 99.9% of every other candidate.

Solve more problems. Solving problems is the best way to learn Machine Learning, but most people don't know where to start. Here are 10 projects you can use to kick off your journey:

Machine Learning Crash Course 100% free. A self-study guide for aspiring machine learning practitioners. developers.google.com/machine-learni…

24h update after launching sql-translator.vercel.app yesterday: ◆ 5000 translations were generated ◆ 150 GitHub stars Just added a feature to translate from SQL to human language. No more confusing and complex queries! My best-performing side project so far!

@KhanAbbas201 This is insane my man well done happy new year 🎉🤗

2022 was my year 2023 is also my year Every year is my fooking year. Started new year writing some code and pushing.

JavaScript Tip: Since JavaScript does not have an inbuilt capitalize function, you can build a simple function to capitalize strings

The best way to use JavaScript in the frontend: Use as little as possible. Optimize like this: - Tree-shake unused code - Minify your code - Generate static pages where possible - Stay away from libraries too large - Always concentrate on user experience (page load speed)

@KhanAbbas201 @CodesUganda @CeloOrg @celo_insider Brisa is doing awesome work😌

@CodesUganda @CeloOrg @celo_insider Brisa doing great work @MelzShawn

prosperity for everyone @CeloOrg @celo_insider

If you really want to succeed in software development: It's all about practice. 1. Learn some theory 2. Practice 3. Practice 4. Practice 5. Revisit the theory 6. Practice more Software development is a lot about ”muscle memory.”

One crucial ability many software developers miss: Patience. - Try not to rush things - Think solutions through a second time - Don't worry about fast result - worry about good ones - Better talk to a few more peers and take your time Impatience has never lead to good results

What I would do if I had to learn to code all over again: - Pick a language like JavaScript or Python - Join a community - Find a mentor - Learn the hell out of all the fundamentals - Jump into frameworks and begin to specialize - Branch out later That's it.

@TreciaKS @strapijs This is amazing news this morning congratulations Trecia🎉🎉🎉 you are going to kill it

I GOT A JOB!!! I've joined @strapijs as a Developer Advocate Intern!!! 🥳🤯🥳

@MarisaBrantley Hello Marisa this is amazing and congratulations 👏🎉

Over 5,000 followers... I really can't thank you all enough! 🙏😊 About me: 🔹From the Los Angeles area 🔹Currently studying React 🔹Love sharing things I've learned & laughed at in my coding journey to help others! 🔹Getting out in nature daily is my way of decompressing. 💚

Whenever you have that feeling that you are not progressing at all although you put in the work every day: - Take a step back - Take a deep breath - Look behind you and see the massive mountain you have already climbed You're missing perspective, not progression.

@oliverjumpertz I have learned alot from this thread and always learning from my friend. This is really valuable especially for us still new to the software development world.

I've developed software for over 22 years now, which is way over half of my lifetime, both professionally and as a hobby. Here are some of the most valuable lessons I learned along the way:

Seven things that kill any software developer's career: 1. Not listening to feedback 2. Always going for the latest tech 3. Not testing code 4. Constantly knowing it best 5. Not caring for code readability 6. Lack of focus 7. Writing clever code

@kacieahmed Wow this is amazing 🤗 congratulations Kacie🤗🤗💜