I don't have that reading at all. The phrasing even seems (carefully?) chosen to avoid this interpretation: it's "Examples are many of the administrators [...]", not "Examples are the administrators [...]".
GitHub (still) allows you to edit files directly in the browser without using AI.
I know how to review code without looking at the corresponding assembly and have high confidence in the behavior of the final binary. I can't quite say the same for a prompt without looking at the generated code, even…
I also do this. Random flags added to core tools are done with aliases, which do not affect the launched processes, not by shadowing them in ~/bin. Shadowing in ~/bin are for cases where a newer (compared to the…
I like it. IIFEs always make me nervous because they look like they beg to be removed if you don't know why they are used. Using an explicit function such as `run` looks much more intentional, and provide a single…
You can send arbitrary commands, but they will be rejected unless you provide valid credentials first.
Not GP but I read "I'm fine with allocation failures" as "I'm OK with my program terminating if it can't allocate (but not for other errors)".
Not GP but bump allocation (OCaml's GC uses a bump allocator into the young heap) mitigates this somewhat, list nodes tend to be allocated near each other. It is worse than the guaranteed contiguous access patterns of a…
You can give honest, unbiased feedback without insulting either people or their work. Software engineering is a collaborative process, not an adversarial one.
You should have a drop-down for selecting a tool profile next to the drop-down for model selection. Select "Minimal" for no tools. "New text thread" should also have no tools I believe.…
I can think of plenty situations where you really want to use the dependency's types though. For instance the dependency provides some sort of data structure and you have one library that produces said data structure…
Alternative answer: both versions will be picked up. It's not always the correct solution, but sometimes it is. If I have a dependency that uses libUtil 2.0 and another that uses libUtil 3.0 but neither exposes types…
It's not "all the transitive dependencies". It's only the transitive dependencies you need to explicitly specify a version for because the one that was specified by your direct dependency is not appropriate for X reason.
Sure, I'm happy with locking the parts I need to lock. Why would I lock the parts I don't need to lock?
What if libinsecure 0.2.1 is the version that introduces the vulnerability, do you still want your application to pick up the update? I think the better model is that your package manager let you do exactly what you…
The article starts with this description of 2FA: > an electronic authentication method in which a user is granted access to a website or application only after successfully presenting two or more distinct types of…
If people need "`expect` scripting and a few open source packages [to] automate it to be 1 factor", it is effectively 2 factor for 99.9% of the population. Also, if someone uses a password manager to store both the…
Some people can't install arbitrary software on their employer's hardware.
> It's not actually how code reviews are done by the people who wrote it. What do you mean by that? Even if you do review by emailing patchsets those are still managed locally using branches, to my knowledge.
> This is excruciating in git if you ever need to make a fix to an earlier PR because you have to manually rebase every subsequent change. Spreading the word about `git rebase --update-refs` that will automatically…
"Parse, don't validate" is a catchy way of saying "Instead of mixing data validation and data processing, ensure clean separation by first parsing 'input data' into 'valid data', and then only process 'valid data'". It…
> You need an email_or_error and a name_or_error, etc. You don't need that. A practical solution is a generic `error` type that you return (with a special value for "no error") and `name` or `email` output arguments…
> E.g., requiring that a file have the correct MIME type, not be too large, and contain no EXIF metadata. "Parse, don't validate" doesn't mean that you must encode everything in the type system -- in fact I'd argue you…
> The problem with convention is that no ten people do it the same way "Stuff that starts with one underscore is an internal implementation detail, use at your own risk" in Python is as close to a universal convention…
Maybe the project is a commentary on a post-truth world masquerading as a button.
I don't have that reading at all. The phrasing even seems (carefully?) chosen to avoid this interpretation: it's "Examples are many of the administrators [...]", not "Examples are the administrators [...]".
GitHub (still) allows you to edit files directly in the browser without using AI.
I know how to review code without looking at the corresponding assembly and have high confidence in the behavior of the final binary. I can't quite say the same for a prompt without looking at the generated code, even…
I also do this. Random flags added to core tools are done with aliases, which do not affect the launched processes, not by shadowing them in ~/bin. Shadowing in ~/bin are for cases where a newer (compared to the…
I like it. IIFEs always make me nervous because they look like they beg to be removed if you don't know why they are used. Using an explicit function such as `run` looks much more intentional, and provide a single…
You can send arbitrary commands, but they will be rejected unless you provide valid credentials first.
Not GP but I read "I'm fine with allocation failures" as "I'm OK with my program terminating if it can't allocate (but not for other errors)".
Not GP but bump allocation (OCaml's GC uses a bump allocator into the young heap) mitigates this somewhat, list nodes tend to be allocated near each other. It is worse than the guaranteed contiguous access patterns of a…
You can give honest, unbiased feedback without insulting either people or their work. Software engineering is a collaborative process, not an adversarial one.
You should have a drop-down for selecting a tool profile next to the drop-down for model selection. Select "Minimal" for no tools. "New text thread" should also have no tools I believe.…
I can think of plenty situations where you really want to use the dependency's types though. For instance the dependency provides some sort of data structure and you have one library that produces said data structure…
Alternative answer: both versions will be picked up. It's not always the correct solution, but sometimes it is. If I have a dependency that uses libUtil 2.0 and another that uses libUtil 3.0 but neither exposes types…
It's not "all the transitive dependencies". It's only the transitive dependencies you need to explicitly specify a version for because the one that was specified by your direct dependency is not appropriate for X reason.
Sure, I'm happy with locking the parts I need to lock. Why would I lock the parts I don't need to lock?
What if libinsecure 0.2.1 is the version that introduces the vulnerability, do you still want your application to pick up the update? I think the better model is that your package manager let you do exactly what you…
The article starts with this description of 2FA: > an electronic authentication method in which a user is granted access to a website or application only after successfully presenting two or more distinct types of…
If people need "`expect` scripting and a few open source packages [to] automate it to be 1 factor", it is effectively 2 factor for 99.9% of the population. Also, if someone uses a password manager to store both the…
Some people can't install arbitrary software on their employer's hardware.
> It's not actually how code reviews are done by the people who wrote it. What do you mean by that? Even if you do review by emailing patchsets those are still managed locally using branches, to my knowledge.
> This is excruciating in git if you ever need to make a fix to an earlier PR because you have to manually rebase every subsequent change. Spreading the word about `git rebase --update-refs` that will automatically…
"Parse, don't validate" is a catchy way of saying "Instead of mixing data validation and data processing, ensure clean separation by first parsing 'input data' into 'valid data', and then only process 'valid data'". It…
> You need an email_or_error and a name_or_error, etc. You don't need that. A practical solution is a generic `error` type that you return (with a special value for "no error") and `name` or `email` output arguments…
> E.g., requiring that a file have the correct MIME type, not be too large, and contain no EXIF metadata. "Parse, don't validate" doesn't mean that you must encode everything in the type system -- in fact I'd argue you…
> The problem with convention is that no ten people do it the same way "Stuff that starts with one underscore is an internal implementation detail, use at your own risk" in Python is as close to a universal convention…
Maybe the project is a commentary on a post-truth world masquerading as a button.