back

Why Join a Coding Bootcamp?

Advice to Future Developers from Kyokan CEO

Computer with Why Join a Coding Bootcamp? written over it

Editor’s note: After finishing his contract with Kyokan, Michael is now working at the blockchain game company Double Jump.tokyo. We’ve got an interview with him coming soon! See how he started his career in decentralized apps.

We recently interviewed Dan Tsui, founder and CEO of the blockchain company Kyokan.

A former poker player and college drop-out, Dan also attended a coding bootcamp. Since our graduate Michael Arnold was working at Kyokan, it was a perfect time to sit down with Dan for a full-circle chat.

Why did you end up becoming a software engineer? I heard you started out as a professional poker player, then went to Hack Reactor?

"Yeah…I spent over 5 years as a professional poker player. I wanted to get better at coding so I could use computational simulations to solve poker simulations. Around that time (2012–4), I started coding a bit more seriously, and even cracked open textbooks from college that I used before dropping out to become a poker player. I didn’t realize that the program I went to was much more geared toward traditional software engineering and development."

So, in your opinion, what is the value of coding bootcamps?

"When starting a career you want employable skills to meet a minimum threshold.

So immersive programs like Code Chrysalis give you a high amount of certainty that if you try hard, and immerse yourself, you can leave it up to the instructors and program to get you to the point where you’re at a minimum employable. And you’ll also learn more than through self-teaching.

There’s an analogy: you’re paying a premium to go to the gym, and everything is there for you to get the balanced improvement to physical ability and physique. In the same way, at a coding bootcamp like Code Chrysalis, you get that benefit.

From the perspective of employers, you can see their projects, and you can be assured they met a minimum requirement."

What is your advice to people considering coding bootcamps, or who want to be developers and enter the field?

"Work really hard.

One of the things that helped me is that I did nothing but code for the entire program at Hack Reactor. The idea was to show up before everyone else and leave after everyone else.

You’re there for a reason, so make the best of it.

In any self-directed learning environment, or non-university models, there’s a lot of skepticism about whether the claims are valid. Are these people creating a pipe-dream about a shortcut? Which students get left behind?

I don’t have any resonance with students who clock in then clock out, and who — when it doesn’t work out — complain that someone wasn’t nice, or that they had health problems…No! If you take maximum ownership of this time, that’s as much control as you have over anything.

For people considering joining a program like this, it isn’t a silver bullet — you have to put in the work."

What is the mark of a good developer?

"Broadly speaking, there are two types of engineers: specialists and generalists. But overall you have to marry both of these skills — generalization and specialty.

If you think “I want to go to this bootcamp and get a job” you’re by definition a generalist. You have to move forward as best as you can in that way, and figure out what the right set of skills are, and how to present yourself.

On the other hand, the hard mode, so to speak, is if you already know exactly what you want to do. Crypto, machine-learning, or what have you. It’s just really hard to know a priori if that is what you want. If you go that route, you can potentially skip your “first job” and go straight into things.

So the advice tends to be, get good enough at the set of thing you learn at the bootcamp, then be okay with some degree of generalization during your job.

As a former bootcamp student who has gone on to become an employer, what is it like working with a recent graduate like Michael?

"Michael is somebody who is a textbook case for a very good fit for a program like Code Chrysalis.

Because he was an entrepreneur before joining the program, he joined with the explicit purpose of gaining technical skills, because he’d worked so much on the non-technical side of things. He understood firsthand what it was like to have responsibility over technical projects, but without being able to vet the quality of the work and quality of the code. So he took action to understand the technical side of things. And that’s so important.

I thought Michael was very fresh, very communicative, and it was clear he had this depth of product experience. It was clear that he had a variety of interests that were relevant to us. And he had a clear idea of what the high level information of the industry was.

The more we got to talking, it was clear that he had all these intangibles and that we could trust him with responsibility. We had a lot of room to place him somewhere.

Kyokan doesn’t tend to hire a lot of new college graduates, or right-out-of-a-bootcamp engineers, because people have to hit client projects running.

But we made an exception for him. And he’s been validating that decision."


Thank you to Dan Tsui for sitting down and having a talk with us! You can find him on LinkedIn here. We've attached a message from Kyokan below:

"Kyokan is always in search of engineers passionate about the values and degree of sweeping societal change that can be effected by the crypto-asset industry. Kyokan has put itself out there as a forum that wants to build the infrastructure and products to enable that change. We understand that this will take a long time, possibly decades. Humans who want to be part of that should learn more about our work, our projects, and reach out to us."

Share