New io.Connect developer onboarding tips

When onboarding a new developer to work with io.Connect what are the most important things you’d point them to?
Is it:

  • Certain parts of the documentation (e.g. capabilities)
  • A repository on GitHub
  • Internal guides
  • A sample project
  • or would you suggest something else?

Firstly we often send them to the Interop docs to understand what the Desktop client is, have an understanding of how it works and then look at the capabilities it then offers. They are often quickly shown buisness setups so they can see how the end client is using the tools to then link knowledge with real world use

We decided to build a bootstrap application for our react and blazor based application so we send them there to read docs about how to then enable features inside interop without requiring much knowledge via the use of things like react hooks and fluxor effects in blazor

Developer then often just look at application code runninng already and work out how to use it from this

Past this, my team is then open to answer questions from developers to help when they want to know more

We find this tends to work very well, but interop documentation is the first port of call

2 Likes

Thanks for sharing, Steven!

That’s a very well-thought-out process.
When I was starting initially the documentation looked pretty straightforward, but after digging a little deeper especially in capabilities and the API it felt a little overwhelming.

I think this is a jem, since often there’s misalignment between developers and end users.

This one also sounds neat, as they can practice with something smaller first.