Live data from Hacker News

Go ahead, write the “stupid” code

spikepuppet.io

71–80 of 157 posts

Re: Go ahead, write the “stupid” code

#71
post #54

Earlier quoted context omitted.

I think PP's point was .. that even if you spend your whole life pressed into laboring to produce a surplus to satisfy the excessive consumption of the elites of your heretical society, in ways that create existential risk for future generations, and are at odds with your own inner values and moral compass.. you can still see the 'immateriality' of all that in the grand scheme of things and choose to be happy.

No, my point is happiness is a choice. There is no sociopolitical statement, no call-to-arms, no pontification as to the measure of one's life, no generational implications. There is an existential consideration, but not of the nature your post implies. Happiness is an individual choice, available to us all at any time. Full stop.

Yeah, no.

What you're promoting is a deeply narcissistic worldview, and I hope either the cure or the consequences reach you soon.

Though maybe those are going to present as the same thing.

Re: Go ahead, write the “stupid” code

#72

Earlier quoted context omitted.

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.

[deleted]

Re: Go ahead, write the “stupid” code

#73

Earlier quoted context omitted.

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.

That's wrong. Plenty of people have "found a way to choose happiness" already, and we've all seen what exactly they've wrought.

Re: Go ahead, write the “stupid” code

#74

>>> 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…

Please step right into this here experience machine, it won't hurt you one bit

Re: Go ahead, write the “stupid” code

#75
> It’s small, it’s dumb, and there were probably plenty of options out there.

Oh, this sort of "dumb" code. That is just exercise. It bothers me that in this field we don't think we should rehearse and exercise and instead use production projects for that.

Actual dumb code is one that disregards edge cases or bets on things being guaranteed when they're not.

Re: Go ahead, write the “stupid” code

#77

Earlier 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.

But that's a trap, the money you "need" is partly decided by how much you have available. Once you're used to the money from a 40 day job it's hard to do with less, but other people manage fine because they never got used to having a lot.

Re: Go ahead, write the “stupid” code

#78

Earlier quoted context omitted.

No, my point is happiness is a choice. There is no sociopolitical statement, no call-to-arms, no pontification as to the measure of one's life, no generational implications. There is an existential consideration, but not of the nature your post implies. Happiness is an individual choice, available to us all at any time. Full stop.

Yeah, no. What you're promoting is a deeply narcissistic worldview, and I hope either the cure or the consequences reach you soon. Though maybe those are going to present as the same thing.

I really don't see how your comment has to do with his at all. You're both talking about completely different things, I think.

Re: Go ahead, write the “stupid” code

#79
post #23

This reminds me of the (excellent!) book by Jamie Buck: https://pragprog.com/titles/jbmaze/mazes-for-programmers/ They write a maze algo in any new language they learn just to learn bits of the language.

A modern variant would be to do a year id Advent of Code in the new language.

Re: Go ahead, write the “stupid” code

#80

For 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…

Knowing hard requirements up front can be critical to building the right thing. It's scary how many "temporary" things get built in top of and stuck in production. Obviously loose coupling / clear interfaces can help a lot with this. But an easy example is "just build the single player version" (of an application) can be worse than just eating your vegetables. It can be very difficult to tack-on multiplayer, as oppos…

In many project it's impossible to know the requirements up front, or they are very vagues.

Business requirements != programming requirements/features.

Very often both the business requirements and programming requirements change a lot since unless you have already written this one thing, in the exact form that you are making it now, you will NEVER get it right the first time.

Post reply on HN