3,114 karma · joined October 20, 2007
https://x.com/TuckerCarlson/status/1780355490964283565
I know that TuckerCarlson is a polarizing character. My posting of this link is not any kind of statement for or against him or his politics. That being said, the interview really gives an interesting picture of Pavel Durov IMO. If you can ignore Carlson's annoying tangents into American politics, you get to hear a good bit of Durov's life story straight from his mouth in reasonable detail. I came away from it with a more positive picture of Durov and Telegram.
Keep a few significant problems in your mind...and also keep a few significant solutions / problem solving techniques in your mind. Then when you encounter new problems, check them against your set of solutions and see if any of them apply. Also, when you encounter new problem solving techniques, check them against your set of problems to see if they're applicable. Whenever you encounter a new problem or solution that seems unusually significant, add it to the list that you keep track of
https://annas-archive.org/search?q=against+intellectual+mono...
Your fundamental point about the power of basic shell tools is still completely valid. But if I could attempt to summarize OP's point, I think it would be that SQL is more powerful than ad-hoc jq incantations. And in this case, I tend to agree with OP. I've made substantial use of jq and yq over the course of years, as well as other tools for CSVs and other data formats. But every time I reach for them I have to spend a lot of time hunting the docs for just the right syntax to attack my specific problem. I know jq's paradigm draws from functional programming concepts and I have plenty of personal experience with functional programming, but the syntax and still feel very ad hoc and clunky.
Modern OLAP DB tools like duckdb, clickhouse, etc that provide really nice ways to get all kinds of data formats into and out of a SQL environment seem dramatically more powerful to me. Then when you add the power of all the basic shell tools on top of that, I think you get a much more powerful combination.
I like this example from the clickhouse-local documentation:
$ ps aux | tail -n +2 | awk '{ printf("%s\t%s\n", $1, $4) }' \
| clickhouse-local --structure "user String, mem Float64" \
--query "SELECT user, round(sum(mem), 2) as memTotal
FROM table GROUP BY user ORDER BY memTotal DESC FORMAT Pretty" clickhouse local -q "SELECT foo, sum(bar) FROM file('foobar.csv', CSV) GROUP BY foo FORMAT Pretty"
Way easier than opening in Excel and creating a pivot table which was my previous workflow.Here's a list of the different input and output formats that it supports.
I don't find it useful to force everything into a single file. Instead, I'll organize these text files somewhere inside a directory structure that I can recursively grep. Unlike the OP I do use mutable TODO lists to track high level lists of things that I want to continue to spend mental energy on, but I do like the chronological list of done things and I might think about adding something like that or maybe augmenting the chronological notes file I already have.
I do depart from the world of plain text for keeping track of larger amounts of information such as good papers I encounter, complete blog posts that I might want to refer back to, etc. For this I use the fantastic DEVONthink tool. It's got a large array of powerful features including automatic OCR and indexing of images and an excellent search feature, but the one that I use the most is its ability to make a "web archive" from a link. This downloads all of a web page's resources and stores them in the database locally, making it really easy to refer back to things that I've seen before regardless of whether I have internet access or not, whether the website is still around, etc.
Your good mood skill seems like the interpersonal version of that. It's always fun to see ideas from different areas form a coherent big picture.
But don't take it from me. This comment https://news.ycombinator.com/item?id=39200966 elsewhere in this thread agrees that you can move that amount of Bitcoin in a small number of weeks.
Every time a trade happens, someone is "coming in" and someone is "getting out". The more trades there are, the more opportunities there are for anyone (including the German government) to take the other side.
> after the recent lack of price action from the ETFs, it doesn't suggest the existing volume is legitimate.
This is by no means the only reasonable interpretation of the price action surrounding the ETF approval. It's totally plausible that the lack of price action just means that the amount of money "selling the news" of the final ETF approval is around the same as the amount of money "buying the rumor" of a big influx of cash.
So you absolutely could convert an amount like that into "real" assets. 11 days doesn't seem like an unreasonable amount of time to me, and we haven't even talked about OTC deals or other providers offering block trading services.
Another way to put it...the government is the only entity in society with a monopoly on the use of force. With great power there should also be a great degree of responsibility.
I think there are times when this works and there are times when it will be a huge waste of time. In general, I think it's often very hard to tell which approach will be more efficient for you. As some sibling comments have mentioned, I think the way each person's individual brain works is a significant factor, but I think there are other potentially unknowable factors that are significant as well.
The best thing I've come up with to deal with this is to use an iterative-deepening-like approach. There's a reason this algorithm (pre AlphaGo) was the most common approach for many game playing programs. The general idea is to go a ways down a particular path but always keep in mind some notion of the global suitability of this path and when it starts to look too hard, back up and investigate some other approaches to at least a shallow (but a little bit deeper than before) depth. This lets you avoid potentially costly dead-ends for relatively low overhead.
(These thoughts inspired from this nice talk: https://www.youtube.com/watch?v=Z8KcCU-p8QA)