Live data from Hacker News

The curse of knowing how, or; fixing everything

notashelf.dev

111–120 of 458 posts

Re: The curse of knowing how, or; fixing everything

#112

Hopefully the future me is able to relate to this, because I really feel like I'm in a rut when it comes to working on personal projects. I have many ideas that I want to build, but I'd have to learn new languages, yet I just can't sit and go through the documentation every day like I should. Still haven't finished the rust book. The other way is start building already, and if you come across a block, then learn abou…

My advice would be to build with what you know.

Even if you need to really shoehorn a component of the system in, just make a note about it and keep building. When you're done, you can go back and focus on replacing that one piece.

My view is that you learn a lot through the process of building this way.

Re: The curse of knowing how, or; fixing everything

#113
My most useful hobby project is the one i just "hack and find out".

I make a matrix led clock that can sync time through network, using Arduino and esp32. Due to time constraint, the coding standard is horrible(magic number, dynamic allocation, no abstraction between module, etc), but hey, it works, at least for 7 years now. The code took me 3 days to finish, and i would never write such code in production FW.

There is a bug that may makes it unable to connect network, but it can be fixed by turning off then on again, i never bother to debug or patch it.

Perfect is the enemy of good.

Re: The curse of knowing how, or; fixing everything

#114

I too suffer from this, but as I learned, Nature built an elegant solution to this. Have a family and kids. Your choice when you have time off of work will be reduced to hacking or playing with your child that you have been neglecting due to a crunch at work. You’re welcome.

Not everybody who is a great programmer is a great parent. :-( I, for example, would perhaps not be a bad parent, but very likely at least one who does not obey the social expectations of how to raise a child.

Same. Also I have absolutely no interest in having them.

Re: The curse of knowing how, or; fixing everything

#117

Hopefully the future me is able to relate to this, because I really feel like I'm in a rut when it comes to working on personal projects. I have many ideas that I want to build, but I'd have to learn new languages, yet I just can't sit and go through the documentation every day like I should. Still haven't finished the rust book. The other way is start building already, and if you come across a block, then learn abou…

This is why I tend to build a simple version of a complex tech just to feel what I am getting into - https://github.com/aperoc/toolkami (a minimal AI agent) as an example!

Re: The curse of knowing how, or; fixing everything

#118
post #89

Earlier quoted context omitted.

I like to say programming is about knowing which rabbit holes to plunge down and which to step over. There's too much to know to go depth-first down every rabbit hole. Go breadth first and accept gaps in your knowledge - everyone has them. If something never comes up and never causes an issue you need to look into, and the project gets done, it doesn't matter. There's always an improvement that could have been made,…

Thank you for your comment, especially for this > I've written a lot of Rust. I've read less than half of the Rust book. Just knowing that there's someone out there who has worked like this or has been in the same situation gives me enough confidence to go through it!(the just write code part) I've gone through so many resources (including the book) and I never managed to finish any of them. But I think now I need to…

That's awesome, best of luck to you.

Re: The curse of knowing how, or; fixing everything

#119

Hopefully the future me is able to relate to this, because I really feel like I'm in a rut when it comes to working on personal projects. I have many ideas that I want to build, but I'd have to learn new languages, yet I just can't sit and go through the documentation every day like I should. Still haven't finished the rust book. The other way is start building already, and if you come across a block, then learn abou…

Don't code, validate your ideas first (to first 1000 paying customers if monetization motivates) and 99% is not even worth to be started with, life is just too short for that.

With AI there's nothing to be ashamed of as it is "what you can dream of, you can get today". There's not much left in programming in most of the projects (that are just repeated code, output, what not over and over) after AI , tools are just too powerful today.

Post reply on HN