28 Nov 2024 #misc
That’s Leland Sklar’s strategy, a well-known bass guitar player and session musician. He’s appeared on over 2,000 albums, based on his Wikipedia profile.
While recording in a studio, if a director asked him to change the sound, he simply turned on or off a fake switch and continued playing.
This is what he said during an interview for Guitar World:
“If I’m on a session and the producer asks me to get a different sound, I make sure he sees me flip this switch and then I just change my hand position a bit. There are no wires or anything that go to this switch. It’s a placebo, but it’s saved me a lot of grief in the studio.”
That’s genius!
What would be a director’s switch for coders? A typo in a variable name, missing brackets on 1-line conditionals, misaligned elements on a screen, writing SELECT * instead of SELECT with a list of columns.
What would you add?
27 Nov 2024 #misc
Only send “Hello, how are you?” in Teams or Slack at work.
You’ll get ignored immediately. Especially if you’re working in a remote team with people all over the world. And especially if you’re reaching out to a busy manager or executive.
This is how that “Hello, how are you?” conversation will look:
- Hello, how are you?
- …
- Good, thanks. And you?
- …
- Good too, thanks.
- Hey, I just wanted…
But, what if your recipient is on the other side of the world? 24 hours could pass between each message. And for sure, you don’t want to wait 48 hours to start the real conversation.
While working remotely at a past job, I used nohello.net as my Slack status. That page shows a fake “hello, how are you?” conversation, getting ignored. And I still got “Hello, how are you?” messages. Arrrggg!
Would you send an email saying just “Hello, how are you” at work?
I know you wouldn’t. Then, why do the same on Slack or Teams at work?
Next time you want to reach out to someone at work:
Don’t send “Hello, how are you?” Say hi and in the same message, without waiting for an answer, say what you really want to say.
That should be “Remote Working 101” when onboarding new team members at any remote company.
26 Nov 2024 #career
That’s question I found on dev.to. Here’s my full answer:
I’ve had mentors. But, not formally and without the label.
I can pinpoint two or three people in my career that were like “mentors.”
At a past job, I had the chance to work next to my team architects and learned a lot from them. From the value of reading other people’s code to rejecting requests politely. Here are some of those lessons, by the way.
And at another job, one day I decided to reach out to my boss’ boss with genuine questions, not related to the job. He was open and kind enough to answer them. He liked reading books too and we connected on that. From that point, we started to have 1-1s outside the usual meetings. He recommended a long list of books to me.
If you’re looking for a mentor, don’t ask anyone to “be your mentor.” That would imply commitment from one side. Most of the time, for free.
Instead of asking someone “to be your mentor”:
-
Approach him with genuine questions: Bring your own challenges and how you’re trying to face them. Ask what he would do if he were in your shoes.
-
Show interest in him: Ask your “not-mentor” about his career progression and choices. People like talking about themselves.
-
Help him somehow too: When I found books my not-mentor would like, I also brought them to our conversations.
-
Show you’re taking action on the advice or input you’re given: I followed up with my not-mentor, sharing lessons I learned from the books he recommended to me.
With those four steps, you will be in a mentorship—without even realizing it.
But, don’t worry if you don’t have a mentor or can’t find one.
Mentors are everywhere. The good thing is you don’t have to meet them. 200-500 books are a good mentor. I learned that from James Altucher, a mentor I haven’t met.
25 Nov 2024 #misc
It took me two years to learn English.
And by “learning English” I mean, a traditional language school gave me a signed piece of paper that says I speak English. After two years, lots of repeat-after-me sessions and grammar exercises, someone finally said I was able to speak English.
I didn’t start learning English from scratch. We’re taking English classes in school since kindergarten, probably.
But if I had to start from almost scratch to learn a language for work, here’s what I’d do:
With AI
- Make a list of common situations at work: Daily meetings, 1-1s, or retrospectives.
- Ask ChatGPT or Copilot to generate short conversations or stories for those situations using the most common words. For example, a daily meeting where you report that you’re stuck with a task.
- Use elevenlabs or any other text-to-speech tool to turn those conversations into spoken words.
- Rinse and repeat.
With YouTube
- Take a beginner’s course on a subject you already know. In your target language, of course. The goal is not to learn that particular subject but to learn new vocabulary.
- Turn the course subtitles or script into phrases to assemble and interchange.
- Rinse and repeat.
Et voilà!
24 Nov 2024 #writing
There will only be writes and write-nots.
That’s Paul Graham’s prediction about the future of writing in the days of AI.
Here are my comments on Paul Graham’s post:
1. “To write well you have to think clearly, and thinking clearly is hard”
Clear thinking is the most important reason to write. You need to order your thoughts before putting them on paper or in a document.
If you know how to write and how to speak in public, you’re unstoppable. I heard that from Jordan Peterson somewhere on YouTube.
Write to think and don’t outsource your thinking.
2. “Writing pervades many jobs”
That’s true for us, coders and software engineers too. Writing is everywhere in our software projects. From README files to user stories to product announcements.
And, the higher up you go, it’s less about coding and more about communication. And except for meetings, you’ll spend more time writing than coding.
3. “Almost all pressure to write has dissipated”
Sure, AI can generate blog posts, sales pages, and any other form of writing.
But, by design, AI generates average writing. That’s its goal. We can tell it by looking at the opening line of any AI-generated text. “In the realm of…” or “In the world of…” Nothing screams AI more than that.
AI will bring more average content. We’re already seeing it. Try searching anything in Google these days.
The printing press didn’t kill books. Social networks didn’t kill bars. Instragram didn’t kill photography.
AI won’t kill writing. AI will only make writing more valuable than ever.