Work Hard (2007) • Hacker News Board

Re: Work Hard (2007)

#201

Post by P_I_Staker » Mon, Aug 30, 2021, 1:07 PM UTC

giantg2 wrote: post #25

It's probably good advice, and maybe my dissent is just due to my burn out, but... I'm tired of hearing "work hard". Very often, working hard does not lead to success. It sure as shit didn't work out that way for me. There are many people who do not work hard and make tons of money in things like NFT, crypto, securities, office politics, scams, etc. It seems like luck is the shared variable... of which I have none.

"Grind yourself to a pulp for someone else's profit or else you're lazy and a bad person"

- Everyone in the USA

Re: Work Hard (2007)

#202

Post by hycaria » Tue, Aug 31, 2021, 2:33 PM UTC

abhayhegde wrote: post #198

hycaria wrote: post #181

Earlier quoted context omitted.

He wrote eloquently about one of his failures in grad school iirc because he simply didn’t work enough nor seriously enough. Even though he is a genius there is quite a lot of work required.

Hey, are you talking about this article: https://www.ams.org/journals/notices/202007/rnoti-p1007.pdf ?

I remember another page formatting but the text looks similar enough to my recalling so I'd say yes!

Re: Work Hard (2007)

#203

Post by metafunctor » Wed, Sep 08, 2021, 12:24 PM UTC

Proziam wrote: post #171

metafunctor wrote: post #161

Earlier quoted context omitted.

What perverted sense of luxury is this? There is no shortage of software jobs. There are plenty of opportunities to work with a relatively clean codebase, capable and experiences colleagues, unencumbered by the VC runway bullshit.

Every company begins somewhere. If you want new companies to make it, allowing for there to continue to be 'plenty of opportunities' in the future, then accepting that there are times when repairing the ~sins~ necessities of the past is reasonable.

600 line bash scripts are not always necessary for new companies to make it. Sometimes, sure. Often, even, on the way to understand what is actually needed.

Many new companies spend too much time perfecting the wrong thing.

But messy code is NOT a requirement to make it.

Messy code, in and of itself, does not help.

Messy code might be a sort of inevitable step on the path to product/market fit. However, it is most certainly not a goal, and dealing with messy code is not a luxury. It is more likely a sign that the early tech people weren't very good.