I used to be a more scheduled person, but I always dreaded following a schedule so I changed my lifestyle quite a bit over the past few years. Now my days are very free-form, and I focus on the 1-3 things that is most important to do that day. And I usually decide these things the night before or morning of.

So typically, my morning routine is that I wake up early and eat a small snack and then go workout. After that, I start my day and I focus on getting the 1-3 most important tasks that I want to get done that day. I am a morning person so I usually like to get my important work done before lunch, and then I take any necessary calls and other interactions after lunch.

I like most of my days to have long blocks of time to think, create and do. I usually just schedule all my in-person meeting on 1 or 2 days of the week, so that I can have the remaining days with more uninterrupted time.

It might seem like I am cranking 24/7, but I am not. In fact, I take very frequent brakes to stretch, go for a walk, eat a snack, day-dream, check what's happening on Twitter, etc. This is how I manage to not burn out -- by letting my mind rest in between short bursts periods of work.

I think this is a very personal answer of what I seek out in a developer:

• Ability to communicate effectively. This means the ability to communicate his/her ideas through code, ability to communicate his/her ideas to other team members, ability to work well with other team members, etc.

• Passion for learning and improving

• Passion for writing good, maintainable and scalable code

• Ability to learn fast

• Independent thinking

• Enjoys tackling problems that he/she has never come across

Honest answer is: I am not seeking "blockchain engineers". I am seeking engineers who are smart and eager to learn. I am seeking engineers who are passionate about coding and tackling tough but interesting problems. I truly believe the blockchain development skill can be learned on the job, as long as you're motivated and hungry to learn, and have demonstrated a passion for writing good quality code.

Simple:

• I workout everyday
• I eat good, nutritious food (I mostly cook at home and only eat out when I'm with friends)
• I get enough sleep

I personally LOVE criticism -- positive or negative. Why? Because I know I'm not perfect, not even close. None of us are, no matter how perfect we seem on the outside. When someone gives you criticism, it should excite you and motivate you. Think of it this way... they are giving you direct feedback on what you could do yo improve or be better. Why not use that to improve yourself? I think it's far worse if someone has some criticism but doesn't share it and keeps it to themselves. Because then you have no clue how you can be a better version of YOU, and they are doing a disservice by hiding it from you.

Think of criticism as an opportunity to become a better version of yourself -- and who doesn't want that? ;)

The secret to all power, all achievement and all possession? Your attitude.

0!

Q4! We'll be posting frequent updates and blog posts well before then, so keep a look out for those. Also, we'll soon be opening up community channels on Slack and Telegram, so it's a great way to get early access and potentially be part of the early beta user group.

I think ICOs are one source of funding, but I don't necessarily think they are the holy grail. I don't belive VCs will be completely eliminated... at least not the GOOD ones. I do still believe the good VCs add value.

While ICOs are a way to raise money, there certainly are a lot of tradeoffs you make. For example, you now have 1000s of investors that you have a fiduciary duty to vs. just a handful. You now have 1000s of investors you have to manage and communicate with frequently vs. just a handful. You now have to act like a public company at seed stage vs. being able to stay private until you are ready to be more public about financials, growth, etc.

They are still an experiment, and the experiment can fail.

Discipline.

This is a great question. And I know exactly what you are struggling with. Unfortunately, the only answer is "write production code". Meaning, work at some company, any company, where you actually need to ship code to real users. No matter how many toy problems you do, or algorithm puzzles you tackle, it'll never be the same as shipping code to real users.

Getting that first job is ALWAYS the hardest. For some people, it takes weeks. For others, it takes years. Just don't give up. Find some place that is willing to give you a chance -- even if it means contracting or working part-time to prove yourself.

Another great way to get similar experience is to contribute to open source. Go out there and find libraries that you can contribute to -- even if it means just updating / fixing documentation at first. Open-source is a GREAT way to get experience before you have real "Work experience".

careers@trustory.io