Why wouldn't the explore/exploit balance leave at least a little to the explore side? Huge amounts of money are going into AI, why not save a little bit to keep an eye on the things that don't currently look like they're going to scale up?
Like maybe a couple dozen people on an explore team?
I imagine that, unfortunately, a lot are, but others might lack things like MFA at their trust boundaries
IT security is a pretty complex topic and a lot of businesses don't have the knowledge in-house to access the security of their own infrastructure
If you have no-one to actually patch your devices and architect your infrastructure, you'll probably end up with just asking the "geeky" student assistant to get it sorted. They'll throw it on the office WiFi, set the same user+password on all the devices and call it a day
In my experience, the vast majority of orgs have essentially no IT security
ProphetX is one of the fastest growing prediction markets in America. Fully CFTC regulated and particularly big in the sports area, we are looking to fill a number of roles across engineering and product.
Among others, we are looking for:
Engineering Manager
Staff Backend
Senior Backend
Staff DevOps (note this hasn't appeared on the job site yet, check in a day or so). This one should be open for EU timezones as well.
It's not terribly important which stack you are in, but we are building some low latency, high throughput distributed systems.
Please mention Hacker News so I can show everyone the wonderful quality of candidates available on this board.
With anything that requires patience, you have a problem competing with immediate rewards.
Why should I learn Stoke's Theorem? Why should I learn Nietzsche? Questions you can't answer until you learn them, and questions that compete with "how will I find a job" and "how will I find a girlfriend".
The problem is, if you don't learn how to answer such questions, you will not know that such questions exist. You will find a job and a partner, and think you never needed to contemplate any of the things you didn't think about.
The heist itself only took 20 minutes, but the preparation is a business that has gone on for years. Much like a heist movie, the exciting bit is just the conclusion after a long build-up where Danny gets the gang together, plans it, and executes it.
> But maybe it wouldn't be that exciting to see some guys sitting at a desk.
Let me introduce you to the TV show Industry which takes you into the world of London high finance where tense phone calls, compliance violations and financial crimes are the order of the day [1]
Not sure why they do this, anyone has an idea? Like, the Internet is just there, I can go and watch porn whenever I like. If I am watching your show, it's because I am interested in something that is not porn. Also, if your show has a lot of these scenes, I can't watch in many places (ie: cafe, plane, with other people, etc..)
>
Not sure why they do this, anyone has an idea? Like, the Internet is just there, I can go and watch porn whenever I like.
It's HBO. They are known for this. But they definitely went too far with Industry in my opinion.
The sex and drug scenes are much more toned down in the latter two seasons. Part of the reason why is the cast had more leverage and strong armed the writers / directors.
Great show but definitely would be better with 90% of the sex / drug scenes removed.
This is like medical series about ER, in real life it doesn't happen. In real life nobody cares, things slip trough, people die, finally someone receives a huge bill.
I imagine it would look like a bunch of North Korean guys (probably not starving like their countrymen, but probably not looking great either) sitting in something like a cross between a NK state prison and an American office.
There's a very good BBC podcast about the north Korean and Russian hacking teams by BBC, one in Lazarus and one on evil Corp or something. Shoudnlt be hard to search for if interested.
Plenty to film/story to tell - Binance team freaking about the operation, the users who find out funds are gone, and the thieves living it up on the stolen money.
Well, no. The locksmith paradox is where a skilled person can walk up to a novel problem and quickly solve it, irking the customer who paid a large sum for the results. Here the thieves almost certainly didn't trip over the Binance vulnerability and solve it in 20 minutes; they planned and researched this task for a long time before executing.
If you want to get that narrow, then why not dismiss my comment by saying that they are not literal locksmiths? The locksmith paradox is about underestimating the expertise behind a quick result, and that expertise can include extensive preparation.
The locksmith paradox is about paying a lot for a small amount of apparent work, right?
The paradox is resolved by considering the expertise, which took a long time and much effort to acquire.
With the heist, the analogous paradox is somewhat weakened. There is hidden effort, but it’s highly specific to the actual target task.
With the locksmith, the hidden work is done on entirely separate tasks and so on, which happen to provide the necessary skills for the current target task.
A related issue is when you set up automation, and it turns out the automation script runs as a different user with different authorizations from the user who tested the script. It's just one of those little annoyances that appears when you try to go from "works on my machine" to "works".
I always build a massive testing harness. I care about correctness, of course, and that is normally dealt with by the AI without having to ask. If you ask for a function, it will write tests.
But I also care about the complexity classes of the solution. I prod it about the time and space complexity, and about cache locality.
I do a lot of black box testing: take the solution, see if it does what I expected, then bake in those expectations in a document.
I find that if I do those things, it produces better code than I could do in the same time.
I also think it's more or less the same as how I used to work, just more thorough and with fewer time-consuming, trivial bugs.
Like maybe a couple dozen people on an explore team?
reply