Exactly! It seems to understand enough about what the commands mean and is able to carry the context forward even if it isn't exactly executing them.
Sure someone must have posted online about ls and rm, but a jumbled combination of those where the model is able to keep track of files listed, created and deleted in the specific context of the chat? Mindblowing!
I don't recall correctly but there was this patent/paper discussing how Facebook (& perhaps a few others) use the EXIF data to confirm and expand your social graph. I guess processing the pictures already gives them everything they need to identify different people who were at the same place at around the same time. But all that meta data like timestamps, geolocation, camera make and model etc. must definitely provide them a great deal more info to be sure about that.
And if one company can do it, I don't see how others can't or won't do it in the future. And only God knows in what all other ways this information can be exploited.
I recommend everyone to clean up EXIF data before they send out files to friends and family or upload backups to the cloud.
I found the CLI tool at https://exiftool.org/ to be very useful. It helps remove EXIF data from a wide variety of file types and comes with tons of filters and features to observe and selectively manipulate & remove EXIF data.
ImageOptim seems like a proprietary SaaS, not something you want to trust your EXIF data with. mat2 is a locally installed tool so it doesn't have that problem (there is a web interface you can setup too).
This is what's so surprisingly scary about time value of money to me. Many "spectacular" investments that double or triple money over a decade or 2 are simply not all that great if you just calculate the annualized return and factor in the inflation.
Back home, I've had so many agents try to sell me inferior insurance and investment opportunities dressed up as insane deals hoping I wouldn't look too much into the details. I was really lucky to come across the folks at /r/indiainvestments who frequently warn about this. But I am sure there are many others who are not aware of these things and fall for them.
I guess doubling in 10 years corresponds to annual percentage of 7.2 percent, and 20 years, 3.6 percent. Adjusting for inflation, the rate will be lower.
BTW, you may be referring to Unit-linked insurance schemes. They are neither good as insurance, nor good as investments.
Sent in a SQL command deleting multiple million records (intended) wrapped in a single transaction (not intended). The replication queues could not keep up and failed, bringing down most of the replicas. Master server kept trying to recover and maxed out all connections - no DBA could log in to perform manual recovery. We had to hard reboot not knowing what state the system is in and how long it'll take to fully recover. Did I mention that this was a few hours before trading was going to begin?
TBH, my team was very gracious about it and the RCA focused purely on the events that occurred and how to never let if happen it again. No blame game at all.
> TBH, my team was very gracious about it and the RCA focused purely on the events that occurred and how to never let if happen it again. No blame game at all.
Which is how a PIR, PER or PCR should be. If you don't understand why someone makes a mistake, you can't avoid future mistakes.
Hmmm. I can't help but wonder if maybe the database engine should have caught the queue overflow (even if the event occurred over the network) and failed the transaction.
I believe it is when you review your colleagues, they review you and your manager collates all the reviews to access your performance. Some places allow you to nominate who you want to provide your review, perhaps people you worked closely with the last couple of months etc.
Welp, as a new grad there, I had brought down one very important database server on a Sunday night (a series of really unfortunate events). Multiple senior DBAs had to be involved to resuscitate it. It started functioning normally just a few hours before market open in HK. If it was any later, it would have been some serious monetary loss. Needless to say, I was sweating bullets. Couldn't eat anything the entire day lol. Took me like 2 days to calm down. And this was after I was fully shielded cuz I was a junior. God knows what would've happened if someone more experienced had done that.
I brought down the order management system at a large bank during the middle of the trading day. The backup kicked in after about a minute but it was not fun on the trading floor.
I'm so glad I'm not the only one feeling deployment anxiety. The project I'm involved in doesn't really have serious money involved, but when there's a regression found only after production deployment my stress levels go up a notch.
When I was working at a pretty big IT provider in the electronic banking sector, we (management and senior devs) made it an unspoken rule, that:
- Juniors shall also handle production deployments regularly.
- A senior person is always on call (even if only unofficially / off the clock).
- Junior devs are never blamed for fuckups, irrespective of the damage they caused.
That was the only way to help people develop routine regarding big production deployments.
Same thing -- used to work at a very large hosting provider. One of our big internal infra management teams wouldn't consider newhires fully "part of the team" until they had caused a significant outage. It was genuinely a right of passage, as one person put it, "to cause a measurable part of the internet to disappear".
I got to see a lot of people pass through this right of passage, and it was always fun to watch. Everyone would take it incredibly seriously, some VP would invariably yell at them, but at the end of the day their managers and all their peers were smiling and clapping them on the back.
Yep. It was supposed to be a very small change. I blundered. My team understood that and was super supportive about it all too. But this was after it was all fixed.
During the outage though, no one (obviously) had time for me. This was a very important server. The tension and anxiety on the remediation call was through the roof. Every passing hour someone even more important in the chain of command was joining the call. At that time I thought I was done for...
Underrated comment. If the government freezes your bank account, at least you can take them to court. If Google mistakenly disables your account, there does not seem to be any legal recourse. Considering the extent to which people depend on their services, perhaps there should be a more elaborate appeal process.
I agree, but the problem is that "ordinary rulefollowing" is not clearly defined by Google. Perhaps it was that innocent park frisbee party video with a Metallica sound played in the background by some other party there... and not only your video, but also your YouTube account, and worse, email account gets blocked. Maybe this scenario is dystopian - the point is that it is a black-box no-appeal/limited appeal system when such an event happens.
Google account terminations typically only affect the one service. If your YouTube account gets terminated for ToS violations, your email account will still work perfectly fine.
I am sorry, but that hasn't been my experience at all. Both on Windows and Android. I've noticed that Firefox eats up far more memory than chrome with way lesser open tabs on both the platforms. I've had tabs die on me multiple times that I simply could not recover. At this point I am very conscious when I am using Firefox because I don't want too many open tabs or leave them open for too long.
I'd love to use Firefox and ditch Chrome completely, but I don't think its there yet.
And I was surprised to know that this has made its way into hiring! So, the job hunt is going to get even more superfluous? Really reminds me of that Episode in Black Mirror, where everything depends on your rating..
