Sync is even worse at scale. I had the pleasure of attending standups in a 20-person team. It was a nightmare where I said two sentences and then wasted the next two hours of my life listening to things I either know or are unrelevant to me.
>you’re punishing everyone with having to back-read
Great, because skipping three pages of unimportant conversation is faster than skipping 30 minutes of banter between two extrovert UI developers as a backend specialist.
>structural strategy to keep everyone accountable
Sounds exactly like something mid level managers say to themselves. Structural synergy? Keeping people accountable? I just want to work, damnit.
The problem with all processes is that people aren’t interested in sticking with them.
Why is your team 20 people if the majority don’t do anything you’re remotely close to? Someone should have split the team or at least the standup.
Why doesn’t your lead enforce a time limit and script?
It can happen the other way round as well. My team is small but only I ever stick to the script. Every one else talks in detail for 2-3 minutes. Their updates could have been 20sec.
You wouldn’t be complaining if someone actually did something about it.
Same manager with right-sized stand-ups wouldn't cost anymore money, unless that manager is making many multiples over what any of their team makes. It seems more like a kneejerk reaction to not "waste" the manager's time at the expense of the actually-more-important-but-hierarchically-less-important employees.
I must be very clumsy with my phone, because it takes me a painfully long time to make a move on my phone (i estimate it to be a bit under a second), while with a mouse I can click at the speed of thought.
It may also be age? I use mouse all my life, while touchscreens are relatively new.
I never tip because it's not a custom in my country, but out of your two contradicting stories I believe the other one more. Does the driver even know the tip amount before rating the passenger? It works make sense if they didn't.
If he does it's indeed a bit weird (in a country where tipping is almost mandatory).
Tipping isn’t “almost mandatory”. People were happily driving Ubers before they even introduced the tipping feature in-app. My rating is based on taking hundreds of rides while living for years on both coasts, in CA and NJ. Out of all those rides only one driver (a horrible one, who took like three wrong turns in twenty minutes, with navigation) ever asked for a tip. I maintain my rating by being clean, polite, and punctual.
I have seen it posed as 'This site has bot protection. Confirm that you are not a bot by clicking yes', trying to mimic the modern Cloudflare / Google captchas.
1. create a working (moderately complex) ghidra script without hallucinating.
Granted I was trying to do this 6 months ago, but maybe a miracle has happened. But I'm the past I had very bad experience with using LLMs for niche things (i.e. things that were never mentioned on stackoverflow)
The first one doesn't seem to actually give me the script, so I can't test it.
The second one didn't work for me without some code modification (specifically, the "count code blocks" didn't work), but the results were... not impressive.
It starts by ignoring every function that begins with "FUN_" on the basis that it's "# Skip compiler-generated functions (optional)". Sorry, but those functions aren't compiler-generated functions, they're functions that lack any symbol names, which in ghidra terms, is pretty damn common if you're reverse engineering unsymbolized code. If anything, it's the opposite of what you would want, because the named functions are the ones I've already looked at and thus give less of a guideline for interesting ones to look into next.
Looking at the results at a project I had open, it's supposed to be skipping external functions, but virtually all the top xrefs are external functions.
Finally, as a "moderately complex" script... it's not a good example. The only thing that approaches that complexity is trying to count basic blocks in a function--something that actually engages with the code model of Ghidra--but that part is broken, and I don't know Ghidra well enough to fix it. Something that would be more along the lines of "moderately complex" to me would be (to use a use case I actually have right now) for example turning the constant into a reference to that offset in the assumed data segment. Or finding all the switch statements that ghidra failed to decompile!
You are getting downvoted but it made me wonder (I visited CERN a few years ago). I guess there are two aspects in play. One, the pile is massive, which naturally inspires awe, especially in person. Two, I know that what I'm looking at is actually a unique super advanced piece of technology, which took countless hours to produce, and that influences how one sees it.
You link says the opposite - the change was very annoying for people that use non-english languages (like me), and:
>By default, qvm-copy and similar tools will use this less restrictive service (qubes.Filecopy +allow-all-names) whenever they detect any files that would be have been blocked by the more restrictive service
Also it looks like this is just for filenames? I can't imagine filtering text like this, that would render the system useless for me.
The defense of the host (dom0) from the websites comes from not showing the UTF-8 window titles (https://www.qubes-os.org/doc/config-files/#gui-and-audio-con...). Since all you see inside VMs is isolated, you can show any text inside them safely for dom0.
It gets a bit harder with transferring files between VMs as my original link shows, but you can be protected from that too at some cost.
Sync is even worse at scale. I had the pleasure of attending standups in a 20-person team. It was a nightmare where I said two sentences and then wasted the next two hours of my life listening to things I either know or are unrelevant to me.
>you’re punishing everyone with having to back-read
Great, because skipping three pages of unimportant conversation is faster than skipping 30 minutes of banter between two extrovert UI developers as a backend specialist.
>structural strategy to keep everyone accountable
Sounds exactly like something mid level managers say to themselves. Structural synergy? Keeping people accountable? I just want to work, damnit.