The benefits of being transparent with your users or customers, but also some best practices on sharing software issues with them.

A bunch of advices I give to people starting in tech or looking for a new job.

P.S.: Don't look at mine, it's a case of do what I say not what I do 🤣

Knowledge is power, employee leaving, new employee joining...

I've created dozens of slides and would love to share some of the tips I gather based on my experience speaking at conferences when it comes slides.

I already wrote an article on public speaking itself.

Yeah, you read right :)

Tricks to help the change from one technology focus to another one or change role completely.

Example: you are doing frontend, you want to move to machine learning engineer roles

Exemple: from a talk I gave at a conference, I'll record it so now I have a video. I will also write an article about the key points and embed the video and slides. I will promote all these on social media. I will also reuse the talk, and give it to more conferences or meetups.

Tips & tricks on my experience building open source software-related communities.

Some of the red flags when looking for a job. Would be useful for people new in tech, and let's be honest, probably everyone. We don't have all the same red flags, but there are some we can all agree on.

Some people within HR are, but sorry, I'll make some enemies, the title of this issue was proved right to me time and time again.

How to start contributing to open source and not be scared.

I mostly want to share my opinion of what I find toxic in the startup culture, and the tech industry overall.

It is often underestimated to have great goodies, like stickers or t-shirts, so I want to highlight the benefits of great swag. I also want to share some good ideas and maybe vendors I used.

You spent a lot of money to sponsor the conference or have a booth, you should have a great booth so people want to come to talk to you.

Tips based on me writing dozens of those over the years and getting accepted or not.

In a world where they is no end of things you can do at work, and in your personal life, let me share some tips on how to prioritize your shit.

Some folks are hiring a developer advocate for the first time, and are not sure what to ask them in interviews to be sure they are the right candidate for the new role. Thought I would share the usual things I want to know when hiring someone on my team.

I had to do this often, and outside of paid services, it's not as straightforward as we thought.

There are a lot of articles out there, but I also want to share why I use it, and how it's beneficial for me as a ADHD person.

The role of a developer advocate, or the developer relations specialty comes with some not so cool things based on my experience. The idea here is to give some transparency to newcomers in devrel.

Having a reference of the https://github.com/fharper/coffeechat/ repository on my blog, but also continuing the promotion of this directory so more people add themselves offering free coffee chats, but also people finding those lovely folks to discuss with and ask questions.

I'm not a legal expert, but I've changed jobs often that I had to validate many contracts, and forgot things which bite me in the ass later. This will also be a useful list for me for the next time!

I never thought it could be interesting, but it's often a question I get asked, so why not a little biography of my journey :)

Tips & tricks on how and where you can start to do public speaking with the benefits of doing so.

A pet-peeve of mine, some best practices on Slack 😅

Some food for thought...

First, you don't pay them and most of the time they have a lot of expenses to speak at your event. It doesn't matter if it's their company paying for it, it still cost them money. Yeah, there are benefits to speak at your event, but it takes a lot of time creating a educating and interesting talks with submitting the talks to events and creating the abstract slides, demos, code, dry run... There is a minimal chance that your audience went to all the same events as the speaker, and seen that talk yet, even for keynotes. When you pay your speaker, it's another story.

Seems obvious for most of us, but it's related the toxic culture we have in tech.

The importance of Developer Relations within an organization.

Some tips to find your first (or not) job as a software developer or engineering role.

There is a misconception that only technical talks are worth submitting at CFP for developers' conferences. Soft skills talks are super popular, and since they are different from all the other submissions, get a higher acceptation rate than others in my experience. I want to share more about that.

Are you in a sect or cult Fred?

I wrote 2-3 articles on that when I was new to this role, but now that it's been more than 10 years, I have a fresher, more complete view on what the role is, the benefits, and the "day-to-day".

I don't manage people anymore, but I still have managers. I've made mistakes, I've had good and bad managers, so I have some stuff to share here.

As a side note, it's also a talk I would like to create out of it, and submit to conferences as a non-technical talk.

Learning to say no: why, how, and examples.

An article on meditation, what it is, and the benefits. I'm giving workshops on meditation now, so that would be a bit self-promotional in addition to being useful for anyone wanting to start taking care of themselves with meditation as one tool for being happier.

How to land your first developer advocate job.

Developer relations is everyone's job, even if it's the responsibility of developer advocates. Quite often it is misunderstood and has sales or traditional marketing expectations. I would like to share how to sell the idea of devrel internally and to stakeholders.

I published a book a couple of years ago with Apress, and sometimes folks who want to write a book with an editor, and not by themselves, asked me about my experience, which I would like to share.

Tips like opening your calendar for informal one-time mentorship sessions or just meeting new people in tech and F.A.Q. people have.

The importance of networking and building your network.

Sharing about ADHD and my story to help folks understand more this neurodevelopmental disorders.

They could even be a series.

The positive impact & ROI of other tasks, goals, and approaches with some examples.

The importance of volunteering and why you should.

How to easily come up with new ideas, how to define your article structure and write it. It's easier than you think

Tips on how to make the speaker's life better like having a speaker room, time to test their equipment within the room... but also things not to do.

Here are some ideas I already shared on Twitter:

• Respectful of my time
• Straight & upfront about the salary ballpark or range right from the start
• Tell me in a video call or on the phone if I didn't get the job after doing the interviews
• Not making a first call to make me repeat what they've seen on my LinkedIn/resume
• Not trying to recruit me for a job that is way under my experience (except AWS recruiters who contact everyone in a city when there is a new role)
• Send you documentation, and useful links about the company and the role to help you prepare
• Told you exactly the interview process and even what is expected and how to prepare when it's complicated.

Maybe I'm naive but I would expect that multiple of those things to be the minimum.

Share a little bit about the persistent depressive disorder and being a functioning depressed "successful" person based on my experience from when I was.

It will be a fun thing to write, and will bring a lot of haters, but I'm tired to repeat myself on that, and it's coming up often 🤣

How to maximize conferences CFPs chances of your talk being accepted based on my experience of public speaking for all these years.

There is a reason developer relations exists, let me share some tips about communicating with developers properly.