HN user

wfriesen

132 karma

[ my public key: https://keybase.io/wfriesen; my proof: https://keybase.io/wfriesen/sigs/WtqgVUgYm61hNZymlqL6OxIprtQtzpjwCJ21z7lJIa8 ]

Posts2
Comments53
View on HN

In Australia it's $400 Google Store credit with the Pro, $250 with the regular. Pixel Watch 2 starts at $549.

Those prods have existed since phones, but it was previously about not having a ringtone blare out. Now the backlash is against people scrolling tiktok/whatever during a movie. I haven't been to a movie theatre in a while so I can't say if it's a phenomenon but that would be infuriating

I've always used this. Any rows returned means there are differences

  select * from (
    (
      select *
      from table1
      minus
      select *
      from table2
    )
    union all
    (
      select *
      from table2
      minus
      select *
      from table1
    )
  )

Yeah, compulsory voting is what makes it a viable way to detect fraud.

I was also mistaken somewhat when I said "paper ballots". There is certainly electronic voting in Australia, but the "authentication" aspect of just saying a name is still the same. It's essentially "trust but verify"

In Australia we do paper ballots, no voter ID, you just say your name and it's crossed off a list. Afterwards, if the same name was crossed off two lists, the amount of double votes are counted and if it is enough to change the result then the result of that electorate is invalidated. This has not ever happened.

Coming from an Oracle background, both application and data warehousing, I wholeheartedly agree with the articles first paragraph saying that application based dynamic SQL is horrible, but DBA (and I'll include data warehousing) dynamic SQL is great, but it's essentially about how complex the thing is.

A DBA is likely doing things like looping over metadata tables and running

  'grant select on ' || some_table || ' to ' || some_user
While an app developer with free reign will end up doing something much more complex, and much harder to reason about/tune

Joins are cheap when joining on indexed columns, but the trade off is extra time maintaining those indexes when writing. As always, it depends on the use case.

I worked in government where Accenture where brought in for projects. A lot of high level meetings and presentations, then sub-junior level devs. At the end there was a lot of legal wrangling over "we delivered what you asked for", while the customer got very little of what they wanted.

Other than doom I like some fuzzy raw black metal to drown out noise, like Paysage d'hiver. Thankfully they have quite a large discography.

Paperless-NGX 4 years ago

I just migrated my instance by repointing the webserver container image at the one in this repo. So far, so good.

Business/requirements/users will often tell you that no two users will have the same birthday/SSN/whatever, but so often that eventually proves incorrect. Just using an auto increment ID as the primary key can prevent a lot of pain down the road.

They contain very little metal, so will not set off any metal detectors. I have a similar sized implant, but not this one, and have no trouble at airports.