Notes / career
- Musing about the future of my profession With the rise of LLMs (and even mandatory AI), I’ve been thinking about what could be done, to lay my own path for the future. By “my own path”, I mean “not the path decided by the current zeitgeist” which is “learn to prompt or be left behind”. For me, the bottom line with vibe coding (coding with AI) is: When LLMs are wrong, they are a pain in the back to work with. When LLMs are right, they steal the joy of learning and challenging myself. I’d rather be a 1X engineer and fucking enjoy solving everyday problems, that
- Enough mentoring Here’s a list of things I’m learning while helping people, during 1-1 technical meetings. Start by expliciting interaction rules At the beginning of the session, ask the person how they would like to interact: should you let them search for a while and only be there when they have a question? should you give a few pointers and let them figure out? should you give them the answers then help them work backward? There’s not one valid way of delivering information to someone. The mentor has an obligation to adapt to the mentee. Modalities > Generalities. When defining how you
- The one with the recruiting gimmicks I’ve been receiving an increasing number of work opportunities over the past twelve months. I always try to reply, even if I know a message was sent through a script scraping Github or Linkedin for developers’ profile. But let’s face it, whether the people reaching out are from HR or CTOs, their messages sometimes feel odd. I’ve compiled a list of gimmicks, ranging from awkward to plain rude, that I’ve encountered lately. I’ll try to be as factual as possible. This is an ongoing list. The one with the young team. The average age is 27. We’re a vibrant, young