I would say that much of my code starts out stupid and, hopefully, becomes better with refinement.
First do it, then do it right, then do it better.
Go ahead, write the “stupid” code
41–50 of 157 posts
Re: Go ahead, write the “stupid” code
#42Earlier quoted context omitted.
Luckily you can still pursue being a musician without all the pressure of having to be successful. On this road, one day you are free to declare your own success to yourself
Maybe if the internet and piracy hadn't fucked artists over, they could have made decent money as a musician selling their work without having to be a major-label superstar. Alas, we do not live in that timeline.
Ah, one of the luxuries of not having to support myself from music... I have no interest in making recordings. That audience means nothing to me.
Re: Go ahead, write the “stupid” code
#43>>> When I finished school in 2010 (yep, along time ago now), I wanted to go try and make it as a musician. I figured if punk bands could just learn on the job, I could too. But my mum insisted that I needed to do something, just in case. Amusing coincidence. I also wanted to be a rock star, or at least a successful working musician. My mom also talked me out of it. Her argument was: If there's no way to learn it in…
> Amusing coincidence. I also wanted to be a rock star, or at least a successful working musician.
> I still play music, but not full time, and with the comfort of supporting myself with a day job.
Some people say;
Pursue your dream or you will regret it.
Other people say;
Don't make your dream a job, because all it will
be is a job and no longer special.
I say;
Happiness is found in neither a dream chased nor a chosen
profession. It is instead a choice we make each day in
what we do, in how we view same, and if we allow
ourselves to possess it.
What constitutes each day is immaterial.
Re: Go ahead, write the “stupid” code
#44The Kernighan law says debugging code is twice as hard as creating it. Therefore, if you push yourself to the limit of your abilities to create the most clever code you can, you won't be able to debug it.
No, it just means you'll be spending extra time debugging it. The most clever code is often cleverness which isn't from you, but derived from the field over time.
Re: Go ahead, write the “stupid” code
#45>>> When I finished school in 2010 (yep, along time ago now), I wanted to go try and make it as a musician. I figured if punk bands could just learn on the job, I could too. But my mum insisted that I needed to do something, just in case. Amusing coincidence. I also wanted to be a rock star, or at least a successful working musician. My mom also talked me out of it. Her argument was: If there's no way to learn it in…
> Amusing coincidence. I also wanted to be a rock star, or at least a successful working musician. > I still play music, but not full time, and with the comfort of supporting myself with a day job. Some people say; Pursue your dream or you will regret it. This is said by people who regret their own choices. Other people say; Don't make your dream a job, because all it will be is a job and no longer special. This is s…
I say if you have money to do whatever you want everyday, there’s an overwhelming chance you’ll be happy.
The rest of those sayings are just for us plebs that have to rationalize working 40-60 hours a week.
Re: Go ahead, write the “stupid” code
#46Earlier quoted context omitted.
> Amusing coincidence. I also wanted to be a rock star, or at least a successful working musician. > I still play music, but not full time, and with the comfort of supporting myself with a day job. Some people say; Pursue your dream or you will regret it. This is said by people who regret their own choices. Other people say; Don't make your dream a job, because all it will be is a job and no longer special. This is s…
I say if you have money to do whatever you want everyday, there’s an overwhelming chance you’ll be happy. The rest of those sayings are just for us plebs that have to rationalize working 40-60 hours a week.
My key point is that happiness is a choice. I hope everyone can find a way to choose it.
Re: Go ahead, write the “stupid” code
#47Re: Go ahead, write the “stupid” code
#48Earlier quoted context omitted.
Luckily you can still pursue being a musician without all the pressure of having to be successful. On this road, one day you are free to declare your own success to yourself
Maybe if the internet and piracy hadn't fucked artists over, they could have made decent money as a musician selling their work without having to be a major-label superstar. Alas, we do not live in that timeline.
Did most artists (in whatever form) ever have a good living in and of itself?
Re: Go ahead, write the “stupid” code
#49>>> When I finished school in 2010 (yep, along time ago now), I wanted to go try and make it as a musician. I figured if punk bands could just learn on the job, I could too. But my mum insisted that I needed to do something, just in case. Amusing coincidence. I also wanted to be a rock star, or at least a successful working musician. My mom also talked me out of it. Her argument was: If there's no way to learn it in…
Really still kicking myself for not majoring in robotics in school. I wanted to program, so I studied computer engineering but hadn't really absorbed that much in classes. But I will likely never have access to all the robotics stuff my school had, nor the guided learnings. Never too late to try stuff out of course, but very little beats structured higher ed education in relatively small classes (think there was only…
On the other hand, the one robotics course I took involved getting access to computers at 3am and doing horrific matrix multiplications by hand that took hours. Of course, this was a long time ago.
Re: Go ahead, write the “stupid” code
#50For sure. I'd argue to write the "stupid" code to get started, get that momentum going. The sooner you are writing code, the sooner you are making your concept real, and finding the flaws in your mental model for what you're solving.
I used to try to think ahead, plan ahead and "architect", then I realized simply "getting something on paper" corrects many of the assumptions I had in my head. A colleague pushed me to "get something working" and iterate from there, and it completely changed how I build software. Even if that initial version is "stupid" and hack-ish!