Greetings, fellow nerds 🤓!
It's been a tough week in the tech world, with layoffs happening left and right. But don't despair! Remember, a layoff is just a temporary setback, not a permanent defeat. Just think of it as a bug in your code: it can be fixed.
So, take a deep breath, dust yourself off, and keep calm. And check out my tips:
Keep your skills up to date: Regularly update your skills by learning new technologies and programming languages. This will make you more valuable to potential employers and increase your chances of finding a new job quickly.
Network: Attend meetups and industry events, and connect with other professionals in your field. Building a strong network of contacts can open doors to new job opportunities and provide valuable support during difficult times.
Create a strong online presence: Maintain a professional online presence through sites like LinkedIn, GitHub, and Stack Overflow. This will help potential employers find you and see your skills and experience.
Be open to different opportunities: A layoff can be a good opportunity to explore different career paths or industries. Don't limit yourself to just one type of job or company, be open to opportunities that may not be exactly what you want but may lead you to something better.
Stay positive and keep a good attitude: A positive attitude can help you stay motivated during a difficult time. Remember that layoffs are a part of the tech industry and it's not personal, keep your head high and stay focused on the future.
Keep up the good work and let's keep coding together!
tl;dr: "There are so many brilliant posts on GPT-3, demonstrating what it can do, pondering its consequences, visualizing how it works. With all these out there, it still took a crawl through several papers and blogs before I was confident that I had grasped the architecture. So the goal for this page is humble, but simple: help others build an as detailed as possible understanding of the GPT-3 architecture."
Via: The GPT-3 Architecture, On A Napkin -Â Daniel Dugas
tl;dr: Julia discusses the attitude and approach to take when debugging, explaining the following:
1) Inspect, don’t squash.
2) Being stuck is temporary.
3) Trust nobody and nothing.
4) It’s probably your code.
5) Don’t go it alone.
6) There’s always a reason.
7) Build your toolkit.
8) It can be an adventure.
Via: A Debugging Manifesto -Â Julia Evans
tl;dr: "I’ve read a lot of comparisons of these two protocols and wanted to write one that is comprehensive and impartial... I was inspired by the release of connect-web (a TypeScript gRPC client that can be used in the browser) and a popular HN post entitled GraphQL kinda sucks." Loren writes a thorough comparison.
Via: When To Use gRPC vs GraphQL - Loren Sands-Ramshaw
tl;dr: "In this post, I decided to write down my definition of what a good OKR looks like. My thinking has evolved from what I first learned long ago in half-remembered talks, blog posts, and books, and is now based on my experience using them to set team goals over the past ten or so years."
Via: OKRs Are Hard -Â Camille Fournier