englebert

When 3D printing became accesible I joined the subreddit for inspiration of what use I could put it to and the opposite happened. Everyone was making plastic toys and ironic reaches like an “egg holster”. Every so often someone would be able to fabricate a replacement part for something which I thought was the coolest. But beyond that. There wasn’t too much to be motivated by. I never got into it.

Here I wonder the same thing. Not that everything joyful must be productive. But if there was a way to apply this to something that was neat in the real world I think I’d be far more motivated to learn the skill. And enjoy it more.

Can anyone recommend the best books on this topic? I’m not as interested in weight loss as I am the mental health effects and other physiological factors.

Yet another surprisingly fantastic reason to hate Equifax:

- no security - no competition - no privacy - no recourse - unsubscribable spam - terrible phone processes force having an online account… which has no security

And the other credit bureaus are just as bad (┛ಠ_ಠ)┛彡┻━┻

It seems like this would be really cool gamified. Such a thing must exist, if so I’d play, if not, I’d wonder why.

Can you talk more about the dynamics and timing here? Joining recently vs reinterviewing, and the factors that influence the underwater situation?

The are several insidious problems with trashing code are:

1. It becomes an impulse and ends up cropping up in places where code is not just perceived as shit, but also misunderstood. And once devs aren’t taking the time to fully understand code before judging it all is lost.

2. It takes mental resources to form the useless judgment and clouds the vision with its bias once it is made. Suddenly it’s more difficult to see the nuanced angles in the code since you’ve got a useless judgement taking up mental space and resources.

3. Again it’s habit forming and becomes a barrier to thinking freshly and creatively when faced with new code.

4. It’s negative.

5. As seen here in all the comments it is rediculously faulty.

6. ALL old code gets to be shit with varying degrees of speed. ALL code bases get old. If you want to work on an old codebase, it comes with the territory. You can be a grumpy old man about it, you can be a grumpy old man about anything, but the net effect is just making you a grumpier shittier developer.

In a similar way I have some coworkers who I know do not code as well because they don’t have the patience to be detail-oriented or pursue optimal solutions by any measure from code efficiency to maintainability. That’s about the worst thing I can think of to say about another programmer… and here’s the thing, they still occasionally write solutions borne of their own perspectives that I can learn from, their code still needs to be maintained, they sometimes do improve etc. If I let the author factor in I’m still going to miss things even if the prejudgment is right 90% of the time.

Finally, I think it is healthy to like people and find the good in them even if they are paddling against the boat, if you can’t lift them up or fire them it’s making the best of the situation. If you can understand that they are humans with their own things going on, that other humans could look at you exactly the same way, I think it lifts us all up.

This is my first HackerNews comment.

EDIT: Formatting. See previous line.