hxchen's comments

Addiction.

I suffer from caffeine addiction: a cup of coffee in the morning just to make myself feel normal. I got terrible mental melt-down once I stopped coffee for a few days.

A great chance ahead is to solve the "I know it when I see it" kind of problems, with Programming-by-Example practice.

Say sorting. You don't need to learn any computer science to tell a list of number is sorted or not.

Problem with the specs. Yes it's irritating to give spec that covers all the cases. But it's a universal problem in software engineering "How do I know the code works"? which applies to programs written by either human or computers.

As far as I know the solution is to write a lot of test cases. By doing that you just created a lot of examples to train a program synthesizer. It doesn't really matter the codes that pass all your tests are written by the engineer you hired or the synthesizer.

Same here.

Another point is that many things are "anxious" because we are doing it for the first time. Like something you used to fear about few years ago, now turns out easy because you have done it tons of time.

Something we can do better is speed up this process intentionally, by deliberate practicing.

While fear-setting can help you get started on "anxious" tasks when you have to do, dedicate some time to exercise the same thing everyday will make "anxious" thing less anxious to you in the long run.

Ben Franklin method: https://medium.com/personal-growth/the-benjamin-franklin-met...

Or use calloc. It does the same thing as malloc, but init memory to zero automatically.

Reason: performance.

If you just do string manipulation, memncpy is faster.

If you need to convert data type, like int to string, then use snprintf.

Yeah a good point.

I think the issue here is order: solving which first. Algorithms motivate you, Handling interface demotivates. So start with the motivator.

You have to be really GOOD at your field to have this freedom. Good for you, dude.

I also like to abstract away the non-sense part of a problem, so that I can focus on the real intellectual puzzles.

As an academia in CS, I use two filters:

* top-tier peer-reviewed conference.

* paper abstract and introduction.

If I am not convinced that the problem is interesting by introduciton, I will skip it.

Dude I got you.

Two kinds of "work": work that gives you money, and work that gives you value. They are not necessarily the same one.

Most people have to work for money. The best we can do is to gather more "money" (or resources). So that you can dedicate more of your time to generate, as you said, "interesting outcomes".

I recommend the book "Your Money or Your Life" by Vicki Robin. I learnt a lot relevant ideas from it.

This should be on the top! Time savior.

I agree with you on that hybrid would be a more sustainable solution.

I want to highlight a technical perspective. That’s the scalability issue of Blockchain. Fully decentralization cannot afford scalability, just as we cannot afford referendum on every polical proposal.

In fact, many technical solutions to scale the Blockchain are using the same principle of your idea of federation.