[-] FizzyOrange@programming.dev 3 points 1 week ago

But you'd still be crazy to use it for either of those purposes, given how safety critical they are. I expect it would be more likely used in robots like Spot, or manufacturing robots.

[-] FizzyOrange@programming.dev 3 points 2 weeks ago

Any from reputable manufacturers?

[-] FizzyOrange@programming.dev 3 points 2 months ago

It's an example to demonstrate that linters cannot reliably detect variable name typos - you need static types. None of the stuff you mentioned is relevant.

The typo in your example is also undetectable by linters. I think you're missing the point.

[-] FizzyOrange@programming.dev 3 points 2 months ago

What's awful about this example? The only thing I do is access an object member. Does your code not do that??

[-] FizzyOrange@programming.dev 3 points 2 months ago

This is the sort of thing you have to learn by experience, like how you can't really learn good coding taste from reading a list of rules (though some lists are helpful).

Anyway in my experience documentation is quite different in public (i.e. seen by customers) and private (inside your company). For internal stuff there's a much smaller incentive to document things because:

  1. documentation tends to be inconsistent (as you discovered), so people give up looking for it. Instead they just ask other people. This actually works fairly well inside a company because you can generally easily access whoever is responsible (as long as they haven't left).
  2. there aren't customers to keep happy and away from support.

I think the best thing to do is to accept that people aren't going to expect documentation internally. There's zero point writing guides to tools on your company wiki or whatever, because nobody will even try to look for it - they'll assume it doesn't exist.

Instead you should try to keep your documentation as close to the user as possible. That means, don't have a separate docs folder in your repo - put your docs as comments in the code.

Don't put deployment instructions on your wiki - add a ./deploy.sh script. It can just echo the instructions initially.

[-] FizzyOrange@programming.dev 3 points 3 months ago

I’d switch course to RISC-V

And give up their only advantage? That would be insane. RISC-V isn't quite mature enough to replace x86 anyway.

[-] FizzyOrange@programming.dev 3 points 3 months ago

He's right. It can give the correct answer but still be crazy incoherent code. Like

let sum = a + b + 2 * a + 3 - b + b - a - 3 - a;

Do you really want code like that in your project? IMO AI assistants definitely increase productivity, but you also definitely need to actually read and understand the code they output, otherwise you adding a ton of bugs and bad code.

[-] FizzyOrange@programming.dev 3 points 3 months ago

You seem to be giving a lot more leeway to interpretations of Peters’ words than my comparison. Odd.

It doesn't require any leeway. It's a totally mainstream opinion supported by actual research. It's only in woke CoC teams that comments like that are objectionable.

he’s also dismissing that it’s worthwhile to try and have an environment free from sexual harassment.

Complete misunderstanding of his comment. Read it again.

Gracefully accepting constructive criticism.

Lol the irony is overpowering.

[-] FizzyOrange@programming.dev 3 points 3 months ago

If you "made light of sexual harassment training" at your job like this you would be fired?

And I lost count of how many times an executive at a startup I’ve worked for was charged with sexual harassment. The outcome was always the same: nothing actually happened to them, but the entire company was sentenced to days of “sexual harassment prevention” training, as part of the deal the bigwig cut to get off easy. By now I must be one of the most highly trained people on Earth in that specialty :wink:.

Jesus you should leave now! That's not ok. (At least in countries with proper labour laws; I guess in America they can fire you for anything.)

I mean I wouldn't advise writing that on your company Slack, but nowhere I have ever worked would fire you for it.

In any case the Python community isn't a company & as far as I understand it Peters isn't getting paid.

[-] FizzyOrange@programming.dev 3 points 4 months ago

Neat, but I'd really like it to just handle memory properly without me having to tweak swap and OOM settings at all. Windows and Mac can do it. Why can't Linux? I have 32GB of RAM and some more zswap and it still regularly runs out of RAM and hard resets. Meanwhile my 16GB Windows machine from 2012 literally never has problems.

I wonder why there's such a big difference. I guess Windows doesn't have over-commit which probably helps apps like browsers know when to kick tabs out of memory (the biggest offender on Linux for me is having lots of tabs open in Firefox), and Windows doesn't ignore the existence of GUIs like Linux does so maybe it makes better decisions about which processes to move to swap... but it feels like there must be something more?

[-] FizzyOrange@programming.dev 3 points 7 months ago

They fired 50 people. What market is that going to flood exactly?

[-] FizzyOrange@programming.dev 3 points 7 months ago

Thanks, I'll watch some.

view more: ‹ prev next ›

FizzyOrange

joined 1 year ago