471–480 of 580 posts
Earlier quoted context omitted.
Last year I tried C on a real Amiga 1200 (using DICE, Matt Dillon’s compiler / runtime). I didn’t get very far, lack of memory protection makes things really hard. This year the Amiga has an 060 upgrade with an MMU, so perhaps I can figure out how to use that and have another go.
Heh. Yeah, a memfault tanking the machine is not conducive to iterative programming :o)
Earlier quoted context omitted.
Being stuck with no idea why or what to do is what gets you exploring and figuring things out. That's the whole point...
That all well and good until you hit a brick wall you cannot pass. At this point a helping hand and/or the answer is the only way forward or to learn.
This is his entire point: getting to this brick wall is _where_ the real learning happens. When you start scrambling, reading old stackoverflow posts, and breaking out the calculus text book you're pushing the boundaries of what is possible for you.
Body builders don't grow by watching other people lift weights.
Earlier quoted context omitted.
It ate my life for a few years in a row, I even managed to finish on Christmas eve twice. Now I don't even look, it turns from fun to stress rather quickly.
I re-read the intro and the fact it mentions leetcode and the like was enough for me to decide that it's an ultimately pointless endeavour for me. I have no interest at all in competitive programming or maths; I spend 40+ hours a week doing programming for work, I want games and challenges that pull me away from that so I continue to have a life outside of my job.
If you have never tried it you should definitely give it a go. It’s quite enjoyable at a moderate dosage.
Earlier quoted context omitted.
this comment actually prompted me to finally download and install the factorio demo, been hearing so many things about how it takes over lives! :)
So, you want it to take over your life?
Earlier quoted context omitted.
C# allows for terser and very functional-y implementations thanks to differences between LINQ and Java’s Streams.
I guess, but it's not really a fundamentally different programming paradigm, which is what I was getting at.
It does do: higher order functions and functional composition, monads and monadic comprehensions, records, list comprehensions and iterators.
You are correct that it's not going to "push" you into that direction aside from APIs that are already popular, but it's unfortunate it keeps getting bundled together with Java. C# and Java are languages with differing priorities, paradigm support and target scenarios. There is great overlap, but the differences are significant.
Earlier quoted context omitted.
That all well and good until you hit a brick wall you cannot pass. At this point a helping hand and/or the answer is the only way forward or to learn.
> you cannot pass This is his entire point: getting to this brick wall is _where_ the real learning happens. When you start scrambling, reading old stackoverflow posts, and breaking out the calculus text book you're pushing the boundaries of what is possible for you. Body builders don't grow by watching other people lift weights.
Don't see any difference with finding the answers on SO, or in textbooks, and having an AI provide the same.
And at the start, novice body builders will of course watch other body builders to learn how it's done.
Unless you're exceptional you're not teaching yourself anything unless it's by learning from others. Few are the pioneers in any field.
If LLMs are really as good at writing code as some people say, they should write a script that fetches each challenge, as soon as it's released, and feeds it to an LLM, to produce a solution. Then run this code and submit the answer it outputs.
Earlier quoted context omitted.
Last year I tried C on a real Amiga 1200 (using DICE, Matt Dillon’s compiler / runtime). I didn’t get very far, lack of memory protection makes things really hard. This year the Amiga has an 060 upgrade with an MMU, so perhaps I can figure out how to use that and have another go.
Heh. Yeah, a memfault tanking the machine is not conducive to iterative programming :o)
I say it in jest but that's actually how I used to program a few years ago when I was working on large industrial pieces of software with long compilation time. You just have to be careful and check what you wrote before sending it to the machine.
I think "iterative" programming has made people really complacent when it comes to silly errors. Slowing down can often do wonder.