Beltalowda

Cheers; I've always difficulty mapping those pprof graphs to actual concrete code and I never managed to get anything more useful out of it.

This is the biggest take-away from this post to be honest; had no idea it could do anything like that. Sometimes it's the little things...

You can get something similar with the CLI using:

  go tool pprof -weblist='mypkgname' cpu.out     # Generate HTML and open
  go tool pprof -list='mypkgname' cpu.out        # Generate text to stdout

> got burnout and disgust at the modern tech hiring practice.

In my experience it's even worse outside of tech.

Because I really need a job I've just been applying to everything. Minimum wage: I don't care. In a way I'm actually looking forward to just show up, do my job, and go home, without stress.

But I get almost no response on those. And I actually spent MORE time for cover letters for those than the tech stuff. On tech I get a response (interview or rejection) for about 1 in 4. Outside of tech? About 1 in 30.

I guess "15 years CV as software dev, that guy is too smart for us" or something like that.

I keep reading about "labour shortages" for lots of low-skilled jobs... Hmkay...

Also not eligible for social security because I'm technically homeless (as in: renting "unofficially").

Might be properly homeless soon... No idea what I'll do.

I don't have a right to work in tech or a high salary, and fine, there's a downwards turn. No problem. But that I have no options beyond "burn all your savings and go homeless fuck you" has left me rather ... disappointed.

Anyway, what I'm trying to say is: it's not "tech hiring" that's the problem. It's just "hiring" or "companies" or whatever.

A good Belter never wastes anything.

I find myself wondering if my email is broken. Which is to say I get very little reply.

Compare this to a year ago when I got a reply to almost every application I sent out.

I'm kind of kicking myself for being so picky; I haven't had a job in a few years and running out of money (I was never that well-off, but coming from a working-class background I don't live an expensive life). I've had a few bad experiences and I wanted to find something I really liked (I actually had a very well paid "Silicon Valley type" job for a company most here will know last year which I quit after 3 months because they gave me fuck all to do and I felt their engineering ethos was horrible – it just didn't feel right accepting a huge salary and not working for it).

The conflation between "not a morning person" and "lazy" is completely ridiculous, and seems to prevail mostly in countries with a "protestant work ethic" background.

I've literally been fired from jobs where I was one of the better performers for the singular reason for struggling to be there at 8am every day, and where this didn't matter at all for the position if I started at 8am or 10am (for some positions it obviously does matter). That I often worked longer than many others didn't seem to matter; people take it as a marker and that's that.

5:30am is utterly ridiculous; that's just the middle of the night.

On punchcards having it as the highest character (with all holes punched) is the only way you can reliably do "delete" or "ignore" outside of having a special dedicated hole for it.

You can still use multiple windows, but it hasn't been the default for a long time.

Murdering one person is murder; murdering a substantial number of people in a region is genocide. Scale can definitely change the fundamental nature of something.

I wll strt mttng vwls frm my cmmnts t rduc nrgy cnsumptn. Svng th plnt n vwl t a tm!

That depends on the settings used for less; AFAIK the default for many distros is to display control characters.

> this type of policy changes on a whim

Ehh...

"I want to share another idea in this post to keep it open-source [..] Let me know what you guys think" is not a "policy change on a whim". It's an idea. It was not "walked back" on, because it was ... just an idea.

Your comment is a horrible misrepresentation of what's actually in the post.

The downside of that is that piping to less won't display colours any more either, so then you need "progname -color=always" or some such. Some programs solve that with a built-in "pipe to terminal" feature, but I always find that a bit annoying.

I don't know anything about terraform, but I've written some applications where I intentionally don't automatically change the output (which in my case is usually bold text, I don't use colours much) because I expect no one will ever use the output for scripting . That's not "poor programming", it's a choice because there is no perfect solution that fits 100% of the cases.

I suspect that may probably be the best choice for terraform as well, but I never used it.

There is no "50 years of technical debt". If anything, a significant amount of complexity has been removed compared to the 70s and 80s when everyone and their mother was making wildly incompatible terminals (actual terminals that is, not software terminal emulators).

You don't really need to know anything about shells to write a CLI app, other than basic shell conventions (- for flags, things like that). You don't even need to know all that much about terminals, just some bare basics if you want to do colours or whatnot. All of this can be summarized in a page or two.

If you want to write a ncurses-like library: that's a different story. But then it's no longer a CLI app.