You probably heard of @LeilaHormozi already, who is currently pushing out a lot of content together with her husband Alex.
I wish I had that information when I started hiring developers.
4 pieces of Leila advice + how it would have kept me from not doing these mistakes.
/1 “Likeness blinds a person”. I met a developer from the baltic countries in 2021 and asked him to build a crawler for me.
I liked him. He was entrepreneurial, I felt understood.
He did his own thing, focused on what was fun, instead of what worked. I lost 1 month of work.
/2 “You cannot ignore red flags”.
Relatable: I kept working with someone who already spoke bad about his last employer and how he had no problems doing things on the side.
That guy logged hour without actually working. It took me weeks to fix the code after him.
/3 “Hire for potential”
Luckily I haven’t made this mistake much. Everytime I hire someone I try to see the person who this #dev will become, not necessarily who they are right now.
I failed a couple of times with people who didn’t advance as fast as they should, though.
/4 “Don’t hire from the same pool of people.”. I almost failed at that; almost hired all in one country.
My mentor stepped in and told me: “What if you find great a dev from India. What are you going to do? Better go all remote, all in English”.
That advice alone was gold.
Those are the most important points. I probably watch everything the Hormozis publish, but if you want the best video on hiring, check out this one:
What do YOU think? Did you step into any of these hiring failures?
Let me know in the comment. And if you like this kind of content, hop on to my email list on tillcarlos.com/updates/
• • •
Missing some Tweet in this thread? You can try to
force a refresh
My choice: "[web3] UX for elearning portal (full specs) [newcomers welcome]"
Following the AIDA framework:
- Attention: web3. Something new
- Interest: full specs (= easy job)
- Desire: Even a newbie can do it
- Action: click on it
Step 2: adding skills. We keep this simple
- Figma: because that’s what we use here (and how I make these images)
- User Flow: can be helpful
- Mockup: This is the end result we’ll need
- Wireframing: an alias for mockups
Correct me if I’m wrong on these. I’m using my intuition
We already said we'll use @_rareblocks . But even if not, we would use @tailwindcss . Advantages:
- It's very easy to make stuff that looks good.
- Just add CSS classes to divs. and there you go (at least that's what the #frontenddeveloper told me ;))
- just in time compilation
This frontend framework is truly simple and easy to learn: #stimulusjs.
We try to go with it and try not to add #ReactJS - but given the abundance of #web3 packages we might add react later.
A group of 6 friends went for it. Each picked 6 Habits.
4 hit most days. 2 didn't.
Insights below:
We based our challenge on this video:
- Every habit at least once every 2 days.
- Every day at least 4 habits out of 6
- no punishment if you fail a day
- If you miss tracking for 2 consecutive days you are out of the challenge
Results: 8 people started, 2 stopped tracking. We checked in via spreadsheet + whatsapp
Results for me:
- did 11 sessions of cardio (will stick to it)
- Prioritized sales for @Pairingdev - which was my primary goal
- Started Journaling every day
- Gained 3kg 😮, gym 10 sessions
Timing of job interviews. The other day I saw on hacker news: a post from tanayagrawal (.substack .com)
“Your interview success can depend on how you schedule your interviews. Here’s how”
👇
Main points made:
- Schedule the interviews in blocks, and try to not hit a time right before/after holidays and long breaks
- Especially this one “I recommend scheduling interviews between 9 AM — 1 PM.”
- The time of the day also plays a role: theguardian.com/law/2011/apr/1…
But does it really matter?
From my experience as a person on the other end, I’d say those factors don’t play big role.
Why?
You don't know where in the process you are. could be the first person in line (the forget you). Or the last: someone else took the job already.