Hacker News Reader

malorton 3blue1brown YouTube Bitcoin video taken down as copyright violation

Including, unfortunately, this usage of "literally."

malorton Many software companies are a joke

> the author’s complaint that he doesn’t get to spend 100% of his workday coding/testing/documenting

The author's complaint was that he only gets to spend 12-25% of his time on these tasks on a good day.

Wishing he had chosen a path in life like most of his drone buddies who settled down, mated with a queen, had their genitals explode, and then died immediately after?

malorton Life advice from NYC chess hustlers

You can see a classic example here (around 2:20): https://www.youtube.com/watch?v=U5vnpOp0U_g

malorton Ask HN: How do you get started as independent consultant or contractor

Can you elaborate on "contracting through recruiters"? Did you respond to recruiters who were reaching out to you with full-time positions and say "no thanks, but what about a contract instead?" If so, do you have any particular strategies for getting to a "yes" with that approach?

Or did you mean that you reached out to recruiters and worked out a finder's fee arrangement if they brought you contracts? If so, how did you find recruiters to work with who weren't already engaged with clients and might therefore have a conflict of interest?

malorton The Spacing Effect

The first versions of Anki (ca 2006) were based on spaced repetition algorithms developed for a piece of software called SuperMemo, which came out 21 years earlier in 1985 [0].

Piotr Wozniak, the author of SuperMemo, writes a lot about spaced repetition and memory in general. What you're describing are basically items 1 and 2 of his "Twenty rules of formulating knowledge" [1]: "Do not learn if you don't understand," and "Learn before you memorize." It's an extremely useful article if you're a heavy Anki user.

0: https://supermemo.guru/wiki/SuperMemo_Algorithm:_30-year-lon...

1: https://www.supermemo.com/en/archives1990-2015/articles/20ru...

malorton Starting with microservices

This is exactly what Shopify does with their monolithic Rails app [1]. I worked at a company with ~200 engineers that used the same general architecture and I really enjoyed it. We got a lot of the benefits (clear interfaces, teams able to work on their system without having to understand the whole platform, build optimization, etc) without any of the operational headaches that come with microservices.

[1]: https://shopify.engineering/shopify-monolith