You could clock out, but I don't think the top performers ever stop thinking about work. Everything you've written here has to be wrong.

If any of you ever wanted to learn to daytrade stocks, use this to practice before risking any money first.

Comments URL: https://news.ycombinator.com/item?id=48417078

Points: 2

# Comments: 0

One thing that I understand at my age of nearly 39 now is that success comes pretty hard, and luck plays a large role in it. As programmers all we can do is build and develop our skills, even if the world doesn't validate our efforts.

You're asking yourself what you are doing wrong, but you should be asking yourself what your goal is and focus on that. Is it really to just work for other people?

What can you do for yourself?

Opus has been amazingly useful at answering various statistics question that I had for it, and my current idea is a nested auction market theory inspired model. My biggest discovery is that replacing time with volume on the x axis (on a chart) and putting the bar duration on the bottom panel instead of volume normalizes the price movements and makes some of the profitable setups I've seen described in tape reading/price ladder trading courses actually visible on naked charts. A great insight I've gleamed is that variance should be proportional to volume instead of time or trade count. When plotted, it has the effect of expanding high volume areas, and compressing low volatility ones, which exposes trending price action much more readily. It honestly amazing, it's making me think that I could actually win at the trading game.

Lol, who doesn't hate that?

He was a problem gambler, but I think if we looked at top poker players of today, they'd all have some love the gamble in them. Jesse had godly tape reading skills that allowed him to beat the bucket shops at the start of his career.

After being kicked out of the bucket shops, he should have just become a floor trader and in all likelihood, he'd have had lower highs but would have fared a lot better overall. A lot of the trading cliches like cutting trading losses quickly, letting profits run, averaging up rather than down originate from this book. There is a reason people still talk about it 100 years after its publication. It's a good contender for the best trading book of all time.

> Competitive Advantage: The winners in AI won’t be those with the cleverest algorithms, but those who can effectively harness the most compute power.

> Career Focus: As AI engineers, our value lies not in crafting perfect algorithms but in building systems that can effectively leverage massive computational resources. That is a fundamental shift in mental models of how to build software.

I think the author has a fundamental misconception what making best use of computational resources requires. It's algorithms. His recommendation boils down to not do the one thing that would allow us to make the best use of computational resources.

His assumptions would only be correct if all the best algorithms were already known, which is clearly not the case at present.

Rich Sutton said something similar, but when he said it, he was thinking of old engineering intensive approaches, so it made sense in the context in which he said it and for the audience he directed it at. It was hardly groundbreaking either, the people whom he wrote the article for all thought the same thing already.

People like the author of this article don't understand the context and are taking his words as gospel. There is no reason not to think that there won't be different machine learning methods to supplant the current ones, and it's certain they won't be found by people who are convinced that algorithmic development is useless.

Underneath it all, there is some hope that an innovation might come about to keep the wave going, and indeed, a new branch of ML being discovered could revolutionize AI and actually be worthy of the hype that LLMs have now, but that has nothing to do with the LLM craze.

It's cool that we have them, and I also appreciate what Stable Diffusion has brought to the world, but in terms of how much LLMs influenced me, they only shorted the time it takes for me to read the documentation.

I don't think that machines cannot be more intelligent than humans. I don't think that the fact that they use linear algebra and mathematical functions makes the computers inferior to humans. I just think that the current algorithms suck. I want better algos so we can have actual AI instead of this trash.

Comments URL: https://news.ycombinator.com/item?id=41545667

Points: 1

# Comments: 0

Some of the stuff in this playlist might be relevant to you, though it is mostly about programming GPUs in a functional language that compiles to Cuda. The author (me) sometimes works on the language during the video, either fixing bugs or adding new features.

Edit: Nwm, I saw you worked for 90 days without pay. Ack.

Staged Functional Programming In Spiral

I am doing a fully fused ML GPU library along with a poker game to run it on in my own programming language that I've worked on for many years. Currently, right at this very moment, I am trying to optimize compilation times along with register usage by doing more on the heap, so I am creating a reference counting Cuda backend for Spiral.

Both the ML library and the poker game are designed to run completely on GPU for the sake of getting large speedups.

Once I am done with this and have trained the agent, I'll test it out on play money sites, and if that doesn't get it eaten by the rake, with real money.

I am doing fairly sophisticated functional programming in the videos, the kind you could only do in the Spiral language. Many parts of the series involve me working and improving the language itself in F#.

However, in the Spiral series, I aim to go beyond just making an ML library for running NN models and break new ground.

Newer GPUs actually support dynamic memory allocation, recursion, and the GPU threads have their own stacks, so you could in fact treat them as sequential devices and write games and simulators directly on them. I think once I finish the NL Holdem game, I'll be able to get over 100x fold improvements by running the whole program on the GPU versus the old approach of writing the sequential part on a CPU and only using the GPU to accelerate a NN model powering the computer agents.

I am not sure if this is a good answer, but this is how GPU programming would be helpful to me. It all comes down to performance.

The problem with programming them is that the program you are trying to speed up needs to be specially structured, so it utilizes the full capacity of the device.

Even so, creating all the abstractions needed to implement even regular matrix multiplication in Spiral in a generic fashion took me two months, so I'd consider that good enough exercise.

You could do it a lot faster by specializing for specific matrix sizes, like in the Cuda examples repo by Nvidia, but then you'd miss the opportunity to do the tensor magic that I did in the playlist.

I spent 2 months implementing a matmult kernel in Spiral and optimizing it.

I find this a very questionable business decision.