Live data from Hacker News

Neofetch developer archives all his repositories: "Have taken up farming"

github.com

11–20 of 309 posts

Re: Neofetch developer archives all his repositories: "Have taken up farming"

#12
I do hope they enjoy it.

I grew up in a farming community, and whist it can be rewarding, if you are trying to make money, or be self sufficient, its fucking hard work.

Is it harder than programming? thats a subjective call. Objectively its physically harder work, mentally its way more varied. You need to be a welder, plumber, vet, horticulturist, builder, metrologist, and if you're doing properly, crooked accountant as well.

Would I take up farming? probably not. Would rather become a water mill owner? hell yeah.

Re: Neofetch developer archives all his repositories: "Have taken up farming"

#14
I knew a few developers who went that route, and they were glad the did, so hope he enjoys his life.

If first few were in the late 80s, back then it the trend where I lived was Pizza Shops in areas that were growing fast. The ones I knew that jumped were happy they did.

edit: fixed typo to happy

Re: Neofetch developer archives all his repositories: "Have taken up farming"

#15
post #7

Twice in my life now I've thought about the effort I've been putting in to my various projects and the lack of satisfaction I've subsequently received, and generally thought about giving it all up and going back to my dad's goat farm (Note that a single goat can go for about €1000). Then I let loose for a week, touch grass, allow my mind to wander/wonder and - boom - a new coding project consumes me and I rekindle th…

You need ... surprise! ... breaks!

Unthinkable in the Silicon Valley hustle culture, but true.

Re: Neofetch developer archives all his repositories: "Have taken up farming"

#16
post #14

I knew a few developers who went that route, and they were glad the did, so hope he enjoys his life. If first few were in the late 80s, back then it the trend where I lived was Pizza Shops in areas that were growing fast. The ones I knew that jumped were happy they did. edit: fixed typo to happy

I remember back on box.sk network knowing a young guy who was extremely bright. He could pick up anything from programming to genetics. But I also remember him feeling burnt out in his early teens and taking a break from all things computer.

Really made you think about those brilliant minds out there and how they work.

Re: Neofetch developer archives all his repositories: "Have taken up farming"

#17

I do hope they enjoy it. I grew up in a farming community, and whist it can be rewarding, if you are trying to make money, or be self sufficient, its fucking hard work. Is it harder than programming? thats a subjective call. Objectively its physically harder work, mentally its way more varied. You need to be a welder, plumber, vet, horticulturist, builder, metrologist, and if you're doing properly, crooked accountant…

> You need to be a welder, plumber, vet, horticulturist, builder, metrologist

I love this about farmers. They are the polymaths of our age and folks dont get it. Farming YouTube is a trip because there's more tech in a tractor than in some startups.

> and if you're doing properly, crooked accountant as well.

Yea, most people dont get what a "future" is, and why corn and lumber have them (but not onions... thats a lesson too)... The farm has the support of a lot of high finance and hedging exists not just as an instrument but has a purpose.

Ask a farmer about a grain/pork "Marketing Plan" and who they are hiring as advisors and where that person got their degree...

It's a complicated world and there are some interesting intersections out there.

Re: Neofetch developer archives all his repositories: "Have taken up farming"

#20
To me the most interesting thing about this is that his github history shows he really gave up in 2021, with almost no commits since then.

I don't know enough of the context of these repos, their significance or ongoing use, but it feels weird to return just to archive en masse. I think it might actually be the least worst option - leaving it open as if you might return gives a false sense of the project, and passing to a successor is a lot of work.

We really put a lot on the heads of solitary people with the open source model.

Post reply on HN