p0rkbelly

5 ms·

1.
by p0rkbelly 2y ago
There is the problem of literal style though. The aesthetics of say clothes do evolve overtime, not year to year big changes, but every 3-5? Sure. Just laughing at the thought of the model where any image generated is say stuck in 1990s gru
2.
by p0rkbelly 2y ago
The second paragraph discusses that BDT is an internal team at Amazon Retail. They used AWS and Ray to do this.
3.
by p0rkbelly 3y ago
Any insight of when the final action date when F2B -family sponsored Visas may move? Been stagnant for years and I'm one month off...
4.
by p0rkbelly 3y ago
8 figures. easily. Apple itself pays $1-million for bug bounties of this type. https://security.apple.com/bounty/categories/
5.
by p0rkbelly 4y ago
It would be nice if things only broke during "business" hours and didn't have real world impact. Nevermind impact millions of people around the world. But if you look at the customers of say code that is running cloud infrast
6.
by p0rkbelly 4y ago
yeah...different story now. The target comp numbers ) assume 15% stock growth per year from when it's allocated to you. That model is now broke for the first time in a decade+. How it gets fixed... I'm not sure, but, there is hist
7.
by p0rkbelly 4y ago
It's all about the RSUs. That all kicks in after year 2. If you're a lower level maybe you don't feel it as much. But for a high performing L6+ RSUs typically are -- or at least were designed to be -- the majority of your inc
8.
by p0rkbelly 4y ago
If your code breaks something, you should fix that code. Who else should? If your system/product/service is down because you have a dependency on something that broke -- well it's up to that team to fix their code.
9.
by p0rkbelly 4y ago
If you write code at Amazon you also are responsible for the availability of your service. So, you rotate in as an on-call. There is no central SRE teams, SysAdmins, etc. There is no throwing it over the fence. There is nobody better to fix
10.
by p0rkbelly 4y ago
OLR is employee performance reviews.
11.
by p0rkbelly 4y ago
PSA: In exposures like this, Contact the cloud provider too. They tend to have the right contacts for customers. And I'm guessing there are actions they can take as well.
12.
by p0rkbelly 4y ago
You assume they have a security team :)
13.
by p0rkbelly 4y ago
They could have been doing this on behalf of a paying customer. They will sell anything with our without having any expertise. "Pay us, bring your data, and we will do the AI for you and help you". They have case studies on it I s
14.
by p0rkbelly 5y ago
I think that is the same as AWS Wavelength which launched in 2019. https://aws.amazon.com/about-aws/whats-new/2019/12/announcin...
15.
by p0rkbelly 5y ago
This has nothing to do with MSFT or AMZN. A good CTO is at any company provides an example of what to aspire to become. They are mentors and teachers to the technical community as a whole.
16.
by p0rkbelly 5y ago
exactly. Everyone has "one job". E.g. Engineers write code -- they also make mistakes and write bad code.
17.
by p0rkbelly 5y ago
razzing from a lateral co-worker on your team is one thing. That's typically good natured (though I'm sure technically an HR Issue). Publicly called out from a CTO at your biggest rival, is not apples to oranges.
18.
by p0rkbelly 5y ago
I think there would be less harm if the possibly identifying information about the recruiter was left out. Everyone in Amazon recruiting is going to be made aware of this now, and this individual is being called out. Usually performance coa
19.
by p0rkbelly 5y ago
all recruiters for the most part.
20.
by p0rkbelly 5y ago
maybe they had multiple windows open, scrolled too far, saw a previous job history? Or an automated script gone wrong? Nobody is saying the recruiter did a good job here, when someone messes up code in Azure, you didn't see the CTO go
21.
by p0rkbelly 5y ago
We are all about junior people making a mistake, but, heaven forbid it's a recruiter and not an engineer (recruiting for an SDE II would be a junior recruiter). It's sort of a dick move for a CTO post that, since the "NN&quot
22.
by p0rkbelly 5y ago
How is Redis different than Hadoop?
23.
by p0rkbelly 5y ago
AWS uses Slack Internally.
24.
by p0rkbelly 6y ago
If you have a use case for spinning up nodes fast -- what is the use for nested virtualization? Sounds like that should be containers on any underlying single-virtualized layer?
25.
by p0rkbelly 6y ago
Who needs nested virtualization when you have bare metal? VM Migration is only for maintenance on GCP -- and customers can't control it, just Google. AWS can hot patch live systems in place without any downtime, so, that's better
26.
by p0rkbelly 6y ago
obligatory: "I could have done this in a weekend"
27.
by p0rkbelly 6y ago
14 years ago. That is called tech debt. Not an issue. They designed it for the use case at the time. Nobody knew what the cloud was becoming.
28.
by p0rkbelly 6y ago
To be fair, you are ALWAYS using a security device even if your instance should not be doing anything. You want to know when something malicious is incoming from the internet, or when suddenly that malware calls out to a C2 server. You may
29.
by p0rkbelly 6y ago
Azure had more specific routing capabilities, yes. But they can't do what this does and maintain the flow stickiness and sessions and scale out.
30.
by p0rkbelly 6y ago
Looks like it is built on the new Gateway Load-Balancer, which the Enterprise firewalls are a part of and auto-scale out. Meaning, third-parties have the same scaling capabilities now. So I see this as "Oh I don't need the big fan

More ›