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

I've been doing this almost 40 years and have never had to pay for either.

Now, if you don't find gcc and neither of vi (and later vim) or emacs usable, well, let's not go there.

And the tools, they just keep getting better. Now I have both clang and gcc, and so many wayy-cool vim plugins to choose from.

I still pay for good hardware, but thanks to Linus and his ilk, I barely need to do that anymore.


Thank you for forcing me to clean my keyboard. </s>

:->


Site renders great for me, iOS Safari with blockers; text selection works fine.

Yeah, I know, karma hit coming, but the other comments are so counter to my experience (I quite like the page and content) that I could not not comment.


OK, so it's not hostile when a small subset of users with the carefully configured ad blockers and nerfing js settings can see it like it could be in the first place?

:)


Same for me (brave android). The blocking of text selection is annoying tho.

What if they are? Why should people attempting to browse securely be punished?

Just debugging the issue :-)

Looks pretty good, but would love to know this compares to bottom (btm), featurewise. Thanks!

Perfmon essentially allows you to define commands you use daily, defined them in a toml file and tab them, ie customizable. It could be docker or kubernetes commands and so on. This is different from btm.

Bottom(btm) gives just more graphical than top.


Ha, I've literally never heard of bottom, and haven't looked it up yet, but it's just kind of funny doing Linux/Unix forever and knowing almost exactly what it must be about, just given the name. I'll edit this if I was wrong, but I bet I won't be.

Especially when you drizzle them with balsamic vinegar!


Try caesar dressing


Fascinating. Anecdata, sample size 1. If it works for OP, fantastic.

Definitely does NOT work for me.

My recipe, such as it is:

1. Be gentle with myself every morning. I may wake vaguely human, but consciousness and acuity require coffee, word games, ablutions, and point 2.

2. Dog walking, aka DW, aka Diagnostic Wandering, allows me to breathe fresh air, let my mind wander or perhaps let it focus. Most of the best code I've written in the last 4 years has been DW code. All of the weird bug discoveries have been DW discoveries. Most - and almost all - of my discoveries about how ND I am and how I really work have been DW discoveries.

3. Recognize which brain I have today, and select issues/workload based on that...

4. ...unless I really, really must, MUST, work on something specific, in which case force it, knowing there is a cost.

5. Recover from such costs as quickly as possible, but as gently as possible (cf #1, #2).

6. When off-roading with my very good friend the CTO, do NOT talk about work...

7. ...unless we both agree something needs 30-90s, after which resume #6.

8. Watch football all day Saturday, if possible, preferably Liverpool, but not necessarily. Detach. (If Saturday is impossible, e.g., family obligations, substitute Sunday.)

9. Read in bed every night before turning off the light, regardless of how tired I am. Subject is irrelevant (current bedside stack: LotR (again), two books of category theory, Ulysses). One sentence, one paragraph, one page, or as many as need be, until I start to drift off. If my GF has to collect the book from chest and turn off the light, so much the better! :-> (She's a night owl, there is no cost and there is much joy to her in this.)

10. Endeavour to start the bedtime process between 2300 and 2330 as often as possible - but see #1 re gentleness. DO teeth. EVERY night. REGARDLESS.

11. Nap occasionally. Ah, my 60s.

12. Recognize when #11 is a MUST, not just a SHOULD.

Let the brain cook and stew and bubble and backburn whilst doing other things. As effective as DWs for things that are more "R" than "d".


Thanks for sharing, I love this :)

Yeah, so I only work "properly" for a few hours, and then I'd say I am gentle with myself the entire rest of the day. That's why I put all the "don't want to do, but need to get done" stuff in the first part. Then I'm chill for the rest of the day!

I got this idea from Brian Tracy's concept of "Eat That Frog" (and book of same title). "If you have to eat a live frog, it doesn't pay to sit around and look at it for very long."

I found the same principle applies in life in general. Once I've decided to do something I'm avoiding, I just have to jump into action right away, before the moment of hesitation can grow into a mountain of dread.


This is awesome. And wholesome. I feel like your recipe is the sort we’d all stand to benefit from if adopting even a part of it. Thanks for sharing,


This comment <s>, maybe?

I guess, then, that one of the big benefits of my daily is that we don't swing wildly between WFH and RTO with whatever trend/fashion/panic/wind/fart is in the zeitgeist/ether/air/media?

With the exceptions of the occasional client meeting that must be onsite, or the occasional conference, and our monthly team lunches, I've been 100% WFH since mid-2020, not pandemic related (I was mostly WFH for since sometime in 2019 (waves vaguely), and it was changing from consultant to senior wage slave that sealed the deal).

Just like the rest of my team. OK, sure, we're small, and OK, sure, perhaps we use the available communication channels more effectively than others seem to, and OK, sure, while some of us are friends, I don't think any of us make the category error of assuming that coworkers are supposed to double as our social life, but seriously, if people are effective working from home, and we are, then let them.

The world started WFH, we changed nothing. The world started RTO, we changed nothing. The world started complaining about gas prices, well, those of us who own trucks and/or off-road did too, but we changed nothing about how we work.

Triple the price of 1Gbps fibre to the home and we might get a bit more upset. </s>


Like I said to a friend, I know just enough category theory to know that I do not understand. Perhaps upon Nth reading.


My guess is that no one ever bothered to define hash(nan), which should, IMHO, be nan.

nan isn't anything. It's an early attempt at None when no/few (common) languages had that concept.

That python allows nan as an index is just so many kinds of buggy.


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

Search: