If I were interviewing a junior dev who had no work experience, here’s what would impress me 👇🧵

Form a group with one or two others, and work to complete a side project together. Give your group a name. Decide on a high level idea. It doesn’t need to be extremely challenging, but it should be enough work to give each of you a handful or more of small tasks.
You don’t need anything other than GitHub issues to break down the work for each other. Create tickets to divide the work into individual contributions as best you can. Don’t over think this part, just do your best and get coding.
Start coding, and create PRs. Add continuous integration, and review each other’s PRs. Don’t approve PRs unless the tests are passing and you’ve critically reviewed code. For tooling Travis CI is free for open source projects. it may be annoying to set up but don’t skip this.
Set up deployment so you can see your project in the wild as you build. This is the fun part of coding. Vercel and Netlify are good options.
Keep at it until it’s done. This won’t be easy at all, but if you are able to complete you will have demonstrated: 1. You communicate and organize. 2. You deliver. 3. You accept feedback from others. 3. You have leadership and initiative to see something from nothing to success
You will have natural answers to common interview questions like: “tell me a time you had a disagreement with someone”. Or “tell me a time you overcame a setback”. You will basically have work experience, which is the easiest way to get an interview / hired.
The biggest takeaway is do not work alone. anyone can code alone. Coding professionally means you need to work with other humans.

More from All

https://t.co/6cRR2B3jBE
Viruses and other pathogens are often studied as stand-alone entities, despite that, in nature, they mostly live in multispecies associations called biofilms—both externally and within the host.

https://t.co/FBfXhUrH5d


Microorganisms in biofilms are enclosed by an extracellular matrix that confers protection and improves survival. Previous studies have shown that viruses can secondarily colonize preexisting biofilms, and viral biofilms have also been described.


...we raise the perspective that CoVs can persistently infect bats due to their association with biofilm structures. This phenomenon potentially provides an optimal environment for nonpathogenic & well-adapted viruses to interact with the host, as well as for viral recombination.


Biofilms can also enhance virion viability in extracellular environments, such as on fomites and in aquatic sediments, allowing viral persistence and dissemination.
How can we use language supervision to learn better visual representations for robotics?

Introducing Voltron: Language-Driven Representation Learning for Robotics!

Paper: https://t.co/gIsRPtSjKz
Models: https://t.co/NOB3cpATYG
Evaluation: https://t.co/aOzQu95J8z

🧵👇(1 / 12)


Videos of humans performing everyday tasks (Something-Something-v2, Ego4D) offer a rich and diverse resource for learning representations for robotic manipulation.

Yet, an underused part of these datasets are the rich, natural language annotations accompanying each video. (2/12)

The Voltron framework offers a simple way to use language supervision to shape representation learning, building off of prior work in representations for robotics like MVP (
https://t.co/Pb0mk9hb4i) and R3M (https://t.co/o2Fkc3fP0e).

The secret is *balance* (3/12)

Starting with a masked autoencoder over frames from these video clips, make a choice:

1) Condition on language and improve our ability to reconstruct the scene.

2) Generate language given the visual representation and improve our ability to describe what's happening. (4/12)

By trading off *conditioning* and *generation* we show that we can learn 1) better representations than prior methods, and 2) explicitly shape the balance of low and high-level features captured.

Why is the ability to shape this balance important? (5/12)
The best morning routine?

Starts the night before.

9 evening habits that make all the difference:

1. Write down tomorrow's 3:3:3 plan

• 3 hours on your most important project
• 3 shorter tasks
• 3 maintenance activities

Defining a "productive day" is crucial.

Or else you'll never be at peace (even with excellent output).

Learn more


2. End the workday with a shutdown ritual

Create a short shutdown ritual (hat-tip to Cal Newport). Close your laptop, plug in the charger, spend 2 minutes tidying your desk. Then say, "shutdown."

Separating your life and work is key.

3. Journal 1 beautiful life moment

Delicious tacos, presentation you crushed, a moment of inner peace. Write it down.

Gratitude programs a mindset of abundance.

4. Lay out clothes

Get exercise clothes ready for tomorrow. Upon waking up, jump rope for 2 mins. It will activate your mind + body.

You May Also Like