#Freetip
Today's move is an example of this tweet. Save this chart for future ref. https://t.co/amUhSLrET3

A thread of images from a Japanese illustrated history of America from 1861.

Here is George Washington (with bow and arrow) pictured alongside the Goddess of America. 1/

Here is Christopher Columbus (seated at center) reporting his discovery of America to Queen Isabella of Spain.

So far, kinda normal, but wait for it.... 2/

Now it's the American Revolution. Here is George Washington defending his wife "Carol" from a British official named "Asura" (same characters as the Buddhist deity). 3/

And here is Washington's "second-in-command" John Adams battling an enormous snake. 4/

Here is Washington and his wife "Carol" meeting an extremely youthful Benjamin Franklin, who has an impressive squat. 5/

A thread on HN about bad code in legacy projects both makes me think how little we've learned as a discipline over the years and, honestly, how little credit we give ourselves for some pretty major

Fun going down this list and thinking: "Hmm, plausible at a well-run modern software shop", "Hmm, possible, but requires implausible tradeoffs", "Literally disallowed by languages", and "If you were to attempt doing that our test suite wouldn't let you merge."

I think we as an industry celebrate (not quite the right word) failure too much and don't celebrate success nearly enough. There is no DailyWTF for competent execution, word of which generally stays pretty local to the source while incompetence passes into legend.

Alrighty let me try to thread the needle on being the change I want to see in the world while not giving away anything that will get me in trouble:

Ruby has wonderful developer ergonomics. Typed languages are easier for machines to guarantee the correctness of. We built a type checker for Ruby (and I believe it is slated for OSS release sometime).

c.f.

1) Core attributes of a promising founder worth following:
- Progress/trajectory over time
- How well they lead a team &
- Make the vision happen
- Most impressed when someone is way ahead of where you thought they would be when you check up/see them a few months later.

2) Indie Makers have such a benefit of being small, fast, nimble workers in comparison to big companies.

We can easily pivot and vastly change a project of ours. We can change as we learn more about our users.

Big companies can take months/years for even the smallest of pivots.

3) Before you find a product market you can pivot your project as many times as necessary until you find something that works.

Then you only have one thing to do: scale, scale, scale.

4) Be obsessed with the little details.
- listen to every single person who uses your product
- reply to every single person who emails you about your product
- ask them what they like and do not like
- iterate your product, make changes, pivot if necessary

5) Paul Graham's (@paulg) name came up with a feeling of great admiration! Naturally! It was Paul who said:

In the early stages of a company just;
- write code
- talk/sell to customers to stress test your idea

Nothing else.

Some ofthe biggest breakouts occur after Volatility Contraction, the analogy is that more a spring is pressed, higher it jumps whenever it gets released.

There is a VCP Scanner on chartink (Not mine). This may also be used to find potential Breakouts.