Apprenticeship-Based Consultancy

After learning about the bare bones of a language used for developing software for the EVM (such as Solidity or Vyper), many an enthusiastic developer has fallen by the wayside after realising that despite knowing - for example - the difference between `calldata` and `memory`, how modifiers work, interfacing with existing contracts, they are not certain what to do next.

Common pieces of advice given to these newcomers typically falls into a few buckets, such as:

• "Go and fork Uniswap, play with some of the parameters",
• "Go and explore/solve the Ethernaut contracts",
• "Go attend a bootcamp or finishing school such as Secureum or Macro", or
• "Go and read a couple of audit reports from top-tier organisations"

We note that all of this advice is well-intended, the resources that they point to are incredibly informative and highly recommended, and this style of learning is particularly effective for a particular type of learner.

An education such as this often comes in the form of presenting completed contracts and either asking how you could break them, highlighting that "this is a way in which you could do such-and-such a thing", or pointing out post-facto issues with code along with their remedies. Heavy focus is often placed upon quickly acquiring a significant amount of academic knowledge through videos, articles or lectures. In some cases, students are encouraged to write projects themselves, but mostly in service of completing an exam.

We're of the related-but-parallel opinion that programming for blockchains is fundamentally something that is learned by doing.

You need to be shouting at your CLI. You need to be baffled by a revert that just will not go away. You need to accidentally brick everyone's testnet balances - at least twice.

Most importantly, you need guidance from someone that has gone through all of this before.

There is a lot of work that DAOs and private clients alike have on the backburner, primarily because their developers are stretched to capacity. They haven't got the time to pick up a junior developer and train them in the specific things that they need to be done, as it would often take them less time to just do it themselves. This is work that is useful today, stretches across multiple levels of complexity, and can be used to build up the confidence (and resume!) of those that work on it.

So: you're going to help them do that work. You're going to learn what's on the cutting-edge and get paid to do it. You're going to be part of an experiment in open-source education.

Interested?

We'll have more for you soon.