AndreiCalazans

Too many damn people are meat proxy

It seems to me this is the same problem we previously had: how do we understand codebases we didn't write?

Creating while writing allowed us to build a mental context but in a unproductive way, it never scalled.

I believe we need to move onto a new way of reading codebases that go beyond reading line by line.

I know people have explored representing code in 3D spaces. I don't know the solution. But I believe that is the problem.

I was here looking for this comment = )

didn't Cloudflare just layoff a few hundred people? odd to see a acqui-hire take place right after that but ok. This is great for Evan You

Are you sure this is not a joke?

This amazing and great! I absolutely hate having to choose something to watch from an immensive infinite list, specially when I'm just trying to relax.

What's with people building open source finance managers? This is like the 1000th one I have seen.

Yea, it's a single conversation but with intervals. Up to a point, like a bit over half way through it, it kinda of lost its context window from the beginning and I had to remind it the curriculum that it was following. Other than that I just kept telling it to continue with the next topic once I was pleased with the current topic.

In my spare time I have been learning Rust. Its knowledge intersection with C, C++, and Haskell make it a fun language to learn.

The one thing that stood out during this process though has been my usage of ChatGPT to instruct me. Instead of reading a pre-published book I simply had ChatGPT write the book as I dove into each subject.

but why would you prefer a nvm like alternative when you could have a single tool manage most of your SDKs/runtime needs?

haha indeed, I am not sure what rtx means also

I think rtx nails the developer experience with managing runtime versions and you likely have not heard of it yet.

Unintentional by accident remote work shouldn’t be considered the baseline for such comparison. This research does at best find results at Microsoft, thus it could be titled “effects of remote work at Microsoft” to not induce the sense of generalist research.

For the negative results: remote work creates silos and reduces cross-network collaboration. These might easily be mitigated with strategies and tooling.

Nevertheless, I admire Microsoft for conducting such research - congratulations to whoever had the initiative.