[-] FizzyOrange@programming.dev 15 points 1 month ago

Vibe port the Zig compiler to Rust? 😄

[-] FizzyOrange@programming.dev 15 points 6 months ago* (last edited 6 months ago)

They should be keeping them in something like kwallet. But in practice they don't because a) there isn't really a single standard for that on Linux (yeay, I have to support gnome-keyring too!), b) it's a lot more work than using a plain text file, c) the UX is considerably worse, and d) the security benefits are marginal at best (especially if you have full disk encryption).

Plain text is the most sensible option.

[-] FizzyOrange@programming.dev 15 points 10 months ago

One example is creating an interface for every goddamn class I make because of “loose coupling” when in reality none of these classes are ever going to have an alternative implementation.

Sounds like you've learned the answer!

Virtual all programming principles like that should never be applied blindly in all situations. You basically need to develop taste through experience... and caring about code quality (lots of people have experience but don't give a shit what they're excreting).

Stuff like DRY and SOLID are guidelines not rules.

[-] FizzyOrange@programming.dev 14 points 1 year ago

IMO this is not a helpful way to put it. They measure skill under stress. Stress may have a large effect on skill level for some people but highly unlikely that it's so large that performance is completely random.

[-] FizzyOrange@programming.dev 14 points 1 year ago

Did they ever explain the highly suss Chinese links? I've used this a bit and it worked well but I'm still not sure I fully trust it.

[-] FizzyOrange@programming.dev 14 points 1 year ago

Also what does it mean exactly? You didn't use copilot to write the game? I don't care about that. Too poorly defined. IMO it's better to explicitly state "this game does not contain AI generated content" or whatever.

[-] FizzyOrange@programming.dev 14 points 2 years ago

Not sure about freelance, but for a salary in my experience, answer some recruiter spam on LinkedIn. I always thought they'd be crap since they are spammy... But after using some I've totally changed my mind. At least in my industry (silicon verification):

  • Companies use them.
  • You get a foot in the door & can bypass all the HR crap.
  • They know all of the relevant companies. I learnt about my current company from the recruiter.
  • They give you some hints about the interview process.
  • They do all of the chasing up for you.

Also, they get a big payoff if you get a job, so their interests are more or less aligned with yours. The only slight difference is that they just want you to get any job, so they might push you to a job you don't really want. But it's minor.

Basically you get a lot of benefits for using them and you aren't paying the cost - the company is. They won't pay that cost to you if you don't use a recruiter and save them cash, so there's no real reason not to use a recruiter.

It may be very different for less niche sectors; I don't know.

[-] FizzyOrange@programming.dev 15 points 2 years ago

pointing and saying “this is shit. Look at this shit”

Yeah you only get to do that if you're Linus 😄

[-] FizzyOrange@programming.dev 14 points 2 years ago

TOML is not a very good format IMO. It's fine for very simple config structures, but as soon as you have any level of nesting at all it becomes an unobvious mess. Worse than YAML even.

What is this even?

[[fruits]]
name = "apple"

[fruits.physical]
color = "red"
shape = "round"

[[fruits.varieties]]
name = "red delicious"

[[fruits.varieties]]
name = "granny smith"

[[fruits]]
name = "banana"

[[fruits.varieties]]
name = "plantain"

That's an example from the docs, and I have literally no idea what structure it makes. Compare to the JSON which is far more obvious:

{
  "fruits": [
    {
      "name": "apple",
      "physical": {
        "color": "red",
        "shape": "round"
      },
      "varieties": [
        { "name": "red delicious" },
        { "name": "granny smith" }
      ]
    },
    {
      "name": "banana",
      "varieties": [
        { "name": "plantain" }
      ]
    }
  ]
}

The fact that they have to explain the structure by showing you the corresponding JSON says a lot.

JSON5 is much better IMO. Unfortunately it isn't as popular and doesn't have as much ecosystem support.

[-] FizzyOrange@programming.dev 14 points 2 years ago

uv is fantastic. I would highly recommend it. I've used it in a quite complex environment, with no issues (quite an achievement!) and it's about 10x faster than pip.

I mean... I guess it's not surprising given uv is written in Rust and pip is written in Python, but even so given pip is surely IO bound I was expecting something like 4x improvement. 10x is impressive.

[-] FizzyOrange@programming.dev 14 points 2 years ago

Yes. The fact that git is decentralised means you can still carry on working and making commits while GitHub is down. With SVN your basically have to down tools.

[-] FizzyOrange@programming.dev 15 points 2 years ago

Saving this for when people try to claim that naming things isn't important!

Also that is clearly a security issue. Anyone who tries to claim otherwise is forgetting that humans exist. Though I suspect they were just trying to avoid admitting fault and doing work. Disappointing either way.

view more: ‹ prev next ›

FizzyOrange

0 post score
0 comment score
joined 2 years ago