falsedan

Thought about contracting/consulting?

Yeah.

> Thanks for leading a vanguard of anti-racism against deepfakes.

Buddy, I appreciate it. You know how hard it is when you’re surrounded by doofuses who can’t even read well enough to tell the difference between race and class and who don’t even understand how to read in good faith much less do it, and stomp all over themselves trying to epic own people with ‘facts’ that are just straw men created from their flawed understanding of existence outside of their bubble? It’s tough, not gonna lie.

Life model drawing, drawing what you see instead of what you thing it should look like

There no parasite that causes facial deformities, and mismatched emotional cues are a fundamental part of humour/acting. It makes as much sense to rationalise the unbidden disgust at unexpected facial structure with disease justifications as it does for the far more likely “person appears to have been damaged during youth/juvenile period by violent/poor nutrition & is of a low social class”.

> Try rebasing in Chromium's repository, it's simply not fast

The intent for a tool which could do this quickly is unclear. Rebasing millions of commits will be slow, also rebasing published history will also generate a lot of extra paperwork.

Writing a utility to sort a rebase todo by message and change the later commits with the same message to be fixups is trivial.

OK, I see your original comment, no need to be rude. If you're working on a computer that struggles with 'making a commit' and 'editing a text file', I feel like you're working in an environment that's going to be very frustrating when writing code.

Are you thinking about rebasing through an IDE? IDEs are uniformly terrible at git.

Why would you rebase an entire git history? No one is arguing for that.

The entire comment is:

> Nah, rebase is too slow on large histories and it might not be your own commit which complicates things.

I don't see any questions being asked. Rebase on the commits we're discussing (readme tweaks) are trivial: fixup fixup fixup

Is that mentioned in the readme? Is this readme worth reading if you don't already know what the project is about?

you can certianly trust it

> inputs/outputs have a Neural Type, that describes the semantics, the axis order, and the dimensions of the input/output tensor

Does that really answer any of my questions? What's 'Neural' about the type?

I think the point from the article is: women never get the choice. Once they're born, their whole career path is laid out and set in stone.

You might think about how that's not the case where you live/according to your background. Congratulations on being born in one of the places where it's easy to succeed!

Because real engineers enjoy making hard things boring.

edit: to be clear, I'm not claiming to be a 'real' engineer. I love writing whimsical, complicated stuff if it makes things easier for users, and make sure I'm writing maintainable code my colleagues are comfortable with with code reviews and removing as many flourishes as possible.

Every medium-sized org I’ve worked at has put a caching layer in front of their build dependencies, so builds aren’t blocked when GitHub/PyPI are unavailable. No build/release engineer would leave that trivial door open if they were responsible for the build

Sounds like the build pipeline was set up by a regular dev.

> A “Neural Module” is a block of code that computes a set of outputs from a set of inputs.

I struggle to find any clarity in this description. You can omit most of it:

> [...] code [...] computes [...] output [...] from [...] input [...]

Which is true, and trivial. This important points for understanding (what kind of input? what kind of output? why sets? what's 'Neural' about functions?) is all missing.

oh yeah, I see them. thanks for clearing that up

> a top speed of 8km/h "lumbering" is putting it midly

8kph is a gentle jog, hardly lumbering.

yeah I'm going to buy a quiche lorraine off amazon and serve it to my date

> Still wrong:

ah, ok, they eat them. thanks for clearing that up

There's a lot of woo in the press release, but the essense is: they claim to have found an exploit in the SIM Application Toolkit (specifically, in the S@T Browser [SIMalliance Toolbox Browser]), which can be triggered when the SIM processes a SMS which contains some attacker data as a payload, and results in the payload being executed by the SIM. The SIM can request some details from the phone (like Cell ID (rough location) and IMEI) and exfiltrate them (via another SMS).

The SIM Application Toolkit is fairly low-level, so has access to a few other functions, like making calls or opening applications or updating firmware. Whether these functions are permitted by the phone depends on the manufacturer, but they claim that the Cell ID & IMEI functions are widely-supported.

who the what now

my point is, vanishing landlord or no, the units remain

are these vanishing landlord eating their properties or just throwing them into the sea

Yeah, in the tiny town I grew up in we only had a single hospital and still had a (private) radiography clinic that was shared between the public hospital and private surgeries.

The test suite for the grody old IRC bot a few jobs ago was written in Expect. One intern season we set a project to, when announcing a new PR was published, to format the primary reviewer’s handle slightly. It ended up taking 3 days to update the tests, understanding expect, then writing a filter to strip out IRC color codes.

Can confirm it's still going; our first was an autumn baby and had his daytime naps by the open tenenment window. Sash and case barely keeps the cold out anyway when they're closed!

> (I can't comment on Scotland and NI but I very much doubt they have different systems)

I can comment for Scotland: it's almost exactly the same. The territorial boards greatly prefer midwife-lead care, so the only times we saw a docter were: months before delivery, saw the GP once to confirm the pregnancy test results; a pediatrician a few hours after delivery to count fingers and toes. Everything else was midwives, and handing over to the health visitors 2 weeks after delivery.

I think a large cause of impedance for engineers to understand the issue is: randomly-assigned ids don’t anonymise users, because you can still attribute an action uniquely to one user (even if you don’t know their name/personal details).

I think of it like the UID I get on a UNIX machine: it identifies me, and anyone with /etc/passed can get my name, and things that don’t have access to it can still see “oh uid 1099 is logging in again to play nethack”.

"Have access to" and "drive down at 35" are different things. Parks are public but you may not be able to enter one if there's some event and its massively over capacity.

Naming is hard because communicating is hard: you have to build a mental model in the mind of the future programmer that’s useful enough to allow them to work on the project and get stuff done reasonably quickly and not accidentally break something due to a misunderstanding.

I see a lot of people struggle with naming because they’re trying to materialise the ‘right’ name, when all you really need is one that’s good enough, unlikely to be misinterpreted, easy to find/look up docs, etc.