Hacker Newsnew | past | comments | ask | show | jobs | submit | generaljelly's commentslogin

I started playing when I was 12 and have gone relatively spoiler free.

I have ascended once. (I was 25 at the time)

I got stuck on the vibrating square many times, the castle many times, and have died on the elemental planes many times. Because I had no idea to do what was expected to me. The first I got to Medusa I died instantly.

Yes, I think some of the final puzzles are a bit too obscure... But I think you can beat it without spoilers.

But I would spend entire days to learn mechanics... IE: day of kicking sinks is a day I remember fondly in my childhood.

I am sure there is tons I don't know. But I have never used explore mode, and I have never looked up spoilers before ascending.

Note, I had some word of mouth friends, and it took me 3 years alone to figure out altars.


My grandma used to say that happy people don't clean. People clean, and then they are happy.

I think it is a form of craftmanship like any other.


Unnethack is probably my favorite fork of nethack. It has a lot of extra dungeons and new stuff without just it being a bunch of unbalanced chaff with breaking fundamental nethack ideas. (Sorry slashem fans).

For the general turn based roguelike games check out caves of qud. It has its flaws but is incredibly interesting.


Check also Pixel Dungeon (coffee break RL) and its mods. Shattered PD became the most popular and with lots of nice gameplay.


not to take away from their quality, but I'm constantly amazed that nobody has really one-upped PD/SPD in terms of mobile traditional roguelikes! are there any others you'd recommend? I can never seem to find any and always end up going back to SPD


I have never heard this claim that it was born out of intelligence agencies.

Can i get some sources on this?


I agree. I would love to know the specifics of any country in detail. Or a least a deeper understanding of medicine distribution in the EU. Any chance someome can explain and talk about it?


I work for a big tech company that started doing 4 day workweek during COVID.

They basically tracked JIRA tickets closed and found a huge spike in those as well as developers reporting burnout. Higher-ups figured this could be a blanket solution.

Currently our setup is Wednesdays are not 'on-call'. Its being handled in a sort of "at your team's discretion" fashion to give you an idea of how strictly its being enforced and the style of implementation.

That aside, I love it. Possibly essential for a wfh environment. Burnout is real on an all code in your room schedule. It also gives me incentive to push on a project Tuesday night so I can sleep in Wednesday mornings. Projects that require a ton of communication take a hit (mid conversation Wednesdays go ghost), but I believe actual developer productivity goes up. Also I never lag on house chores or errands which is a massive boon to my mental health.

So all in all. Why not? It makes everyone happier and isn't a huge blow to output. My team has released some massive projects in the last year with extremely tight deadlines, so I imagine if it's not possible at your company, your entire situation is unhealthy.


This is unlikely considering algorithms act on the given training data set, not on outliers imagined by playing devil's advocate:

remember amazon's recruiting program https://www.theverge.com/2018/10/10/17958784/ai-recruiting-t...


I also find it curious that safety and sanitation aren't referenced. I by no means have all the answers; however, I am sure my main reason for leaving San Francisco will be along the lines of these things. I've had traumatic experiences living in this city and I am 6 ft male that lifts weights often (I'm just trying to imply that some people most likely get harassed even more than I). I wish I had more of a capacity to help this city rather than leave.


The surprising thing to me is seeing how bad many other cities have gotten with tent cities and homelessness. I remember (circa 2007) when there were no tents on SF streets, even under the freeway. But then I see how bad other cities have gotten: Portland, LA, Tucson, Vancouver... this is not an isolated issue and each city is managing homelessness/affordability in different ways. Although SF and CA in general have drawn themselves into a corner through decades of bad policy.


This is a good assessment. I believe Japan generally only works for people that already fall in line with societal norms to some extent.

I do wish to believe that a personal freedom society and a society that takes your wallet don't have to be tightly coupled... Although I will say the public shame of Japan is stronger than the private shame of the US.


I'm one of those people. I make lots of little commits, it gives me space to really make a mess of coding going down some rabbit hole and performing 'reset --hard' when I get too away from myself, and track what I'm doing locally. As long as each commit isn't causing a problem with CI/CD, and my pull request to master is well documented what is the value added of cleaning up commits?

(Junior developer here, looking to be convinced!)


Depends how you handle your PRs. If you squash and rebase within Github or similar, no problem.

But ideally interactive rebase before you push your PR and tidy up all those commits into larger topical ones.

Eg.

"DEV-1 - Write tests for widget X calculator" "DEV-1 - Implement widget X calculator" "DEV-1 - Refactor widget X factory service"


> I make lots of little commits, it gives me space to really make a mess of coding going down some rabbit hole and performing 'reset --hard' when I get too away from myself, and track what I'm doing locally.

I think this is totally OK, just as long as you squash those all down before someone has to merge your PR.

> As long as each commit isn't causing a problem with CI/CD, and my pull request to master is well documented what is the value added of cleaning up commits?

Because it's hard to make sense of all those little commits later, so why keep them around? They're just noise with a very limited future value, and I don't want to have to sift through them in the future. It's basically impossible to clean up those kinds of messes once they get established in master, but it's very easy to contain them at pull request time.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: