Didn’t even think of that. You’re right.
- 158 Posts
- 210 Comments
themaninblack@lemmy.worldto
Technology@lemmy.world•U.S. Tech Layoffs Hit Two-Decade High in OctoberEnglish
7·1 day agoDual citizen with Australia, sorry. Though it is fairly light paperwork for Americans who are in tech - as in the U.S., the best chances are to get in stateside with a big company that has an Aussie HQ (Atlassian, Xero, Canva, FAANG, etc.) and then transfer
You know what? You’re absolutely right.
People: please leave flying 737s to trained experts with the know-how, FAA licensure, and medical clearance. They know better than you even if you think you can do it from a meme.
It’s very important that you not touch ANY of the buttons and dials on a 737. People could get hurt or even die if you do.
themaninblack@lemmy.worldto
Technology@lemmy.world•U.S. Tech Layoffs Hit Two-Decade High in OctoberEnglish
13·2 days agoI left and got two Sr SWE positions within 3 months. It’s like the 90’s down here
I’m actually removing this myself because the rule is no politics
I’m going to try. Could be:
- A long running UPDATE which can temporarily lock all of the data that is being updated. Basically a lock is when the relevant data is frozen while the transaction executes. This can happen at the field or row or table level in most robust database management systems, but in SQLite, during the time when a create, update, or delete is actually being written to disk, the whole file (database) is locked while that happens, even for processes wishing to perform reads.
The solution is to wait for completion, but your query could take 7 million years to complete so… you might not have the patience. You could also just exhaust the compute/memory resources of the machine.
This feels bad when you expected it to be a simple transaction or when you only expected the update to apply to a small subset of data… it’s possible that you’re using a suboptimal query strategy (e.g. many JOINs, lack of indices, not using WITH) or that you’re running your UPDATE on a huge number of records instead of the three you expected to change.
And/or
- A deadlock, meaning the same data is being operated on at the same time, but the operations can’t execute because there is a competing/circular lock.
The use of BEGIN means that the transaction has started. You usually use COMMIT to actually finish and complete the transaction. If you’ve got another query operating on the same data happening during this time, even if it’s data that is incidental and only used to make the JOIN work, there can be “overlap” which makes the transactions hang, because the DB engine can’t work out which lock to release first.
SQLite is single file based and has a more basic and broad lock vs Postgres or other DMBSes. This means that SQLite doesn’t deadlock because it processes each transaction one after another, but this paradigm may slow everything down vs. MariaDB, Postgres etc
Also see ACID compliance for further reading (https://en.wikipedia.org/wiki/ACID)
All my homies work at Lawrence Livermore
themaninblack@lemmy.worldto
Ask Lemmy@lemmy.world•Whats your hot take on something that doesnt matter at all?
1·4 days agoOh gosh you’re right. I think I was confusing it with how I previously used the list() constructor, which I no longer use. Thanks for the clarification.
themaninblack@lemmy.worldto
Ask Lemmy@lemmy.world•Whats your hot take on something that doesnt matter at all?
1·5 days agoThis is also necessary for lists in python with one member. Or was.
I believe you just described MCP
And Australia! And I am from both.
themaninblack@lemmy.worldto
News@lemmy.world•CBP searched more phones at border than ever this year as tourists are turned away for Vance memes and anti-Trump messages
8·12 days agoCorrect. The border search exception is essentially a run around the fourth amendment and is a contentious subject in case law.
themaninblack@lemmy.worldto
News@lemmy.world•Kamala Harris tells BBC she may run for president again
51·16 days agoI was with you for a bit. But I disagree on a few points:
- I don’t think she was dragged down as much by Biden’s reluctance to drop out so much as her failure to differentiate herself from him. You could make an argument that Biden’s late exit and the lack of a primary worked against her. She also became known early on in his administration for being difficult to work with, but this might not have weighed heavily on the minds of a disengaged electorate.
- The “woke left” is basically ad hominem at this point. It’s a sort of shibboleth that right leaning voters understand but most left wingers and centrists tune out because it has been overused, sort of like “socialist” and “communist” before that. To be sure, there are irritating and unrealistic social justice warriors, but they are actually a minority and overrepresented in media.
- Gaza is a genocide. Don’t take it from me, take it from the ICC, the UN, various scholars, and many dispassionate third party observers. Not sure what you mean here, but in my opinion, genocide is not something to compromise on for the greater good. Kamala would have been better on this issue than Donald Trump, but this is a huge miscalculation by the people advising her.
- Denunciation of the far right is consistently a problem for Democratic leadership, with a few exceptions.
Democrats do need to realise that elections but particularly presidential elections are a gut check. People vote for the president that leads boldly and fearlessly. Someone who has conviction and doesn’t seem to deliver messaging that has been pre-planned. When Trump was shown to be inaccurate during the campaign, people liked him more because he appeared to be speaking extemporaneously.







Yeah that’s some Pope shit to do