placardloop

10 ms·

31.
by placardloop 1y ago
13 years is an incredibly long time for something as fast moving as data center development. I guarantee that a _lot_ has changed. I know AWS in particular has gone through multiple entire revisions of their DC designs, and I recall a talk
32.
by placardloop 1y ago
My significant other is going through this situation, and in my experience it seems as though most doctors just simply don’t care to actually find a diagnosis (or at least, don’t have the time or motivation to care), combined with a hefty
33.
by placardloop 1y ago
There’s a massive, incredibly dense neighborhood of houses and offices less than 1000 feet to the south, west, and north of every one of SFOs runways.
34.
by placardloop 1y ago
No, they’re not. Of the 20 largest airports in the US, all but one of them have homes and offices surrounding them. The one that doesn’t is Denver, that’s mostly only because Denver’s airport is relatively new and the development hasn’t rea
35.
by placardloop 1y ago
Your comment stated “nobody is, at all, forced to use any of the AI tools”, which is entirely false - I’m looking at an email in my inbox from my VP right now saying everyone must use AI every day. You said “None are installed by default or
36.
by placardloop 1y ago
If you truly believe what you’re saying, then you’re uninformed as to what is going on outside your own team. And just because it’s not happening in your team does not mean it isn’t happening. Q is installed by default in all browsers on Am
37.
by placardloop 1y ago
MCP and Smithy aren’t comparable. Smithy is an internal tool used by almost every single team (it is used far, far more widely than just the SDK teams) at Amazon to define APIs and generate API servers/clients. It was released public
38.
by placardloop 1y ago
You’re right there won’t be any going back. You’re wrong about who is being smart about it. If Apple wins appeal, they’ll happily and quickly reinstate the fees. It’ll be the app developers who then get stuck paying the fees because, as you
39.
by placardloop 1y ago
It’s not orthogonal. The foundation of good security is using your tools correctly. AWS explicitly tells users to not store sensitive information in policies. If you’re doing so, it’s not AWS making the mistake.
40.
by placardloop 1y ago
ListPolicies does not show the contents of policies, so the information you mentioned isn’t possible to obtain from there. Things like GetKeyPolicy do, but as I mentioned in my comments already, the contents of policies are not sensitive in
41.
by placardloop 1y ago
No, that’s not the reality. “Production data” isn’t as black and white as that. Metadata about your account, regardless of if you call it “production” or not, is not guaranteed to be treated with the same level of sensitivity as other data.
42.
by placardloop 1y ago
AWS does not treat metadata with the same level of sensitivity as other data. The docs explicitly say that sensitive information should not be stored in eg tags or policies. If you are attempting to do so, you’re fighting against the very t
43.
by placardloop 1y ago
This so called “security risk” is a role in a nonprod that can list metadata about things in your production accounts. It can list secret names, list bucket names, list policy names, and similar. Listing metadata is hardly a security issue.
44.
by placardloop 1y ago
It’s inaccurate to say that there’s “basically no zoning whatsoever in much of Texas”. In Texas, zoning is up to the individual cities. Houston is notorious for having a lack of zoning laws, but all of the other major cities like Dallas, Au
45.
by placardloop 1y ago
My company sells AI tools, so there’s a pretty big incentive for to promote their use. We have the same security restrictions for AI tools that weren’t created by us.
46.
by placardloop 1y ago
The article is typical security issue embellishment/blogspam. They are incentivized to make it seem like AI is a mission-critical piece of software, because more AI reliance means a security issue in AI is a bigger deal, which means mo
47.
by placardloop 1y ago
I’d be pretty skeptical of any of these surveys about AI tool adoption. At my extremely large tech company, all developers were forced to install AI coding assistants into our IDEs and browsers (via managed software updates that can’t be
48.
by placardloop 2y ago
You must not work in big tech, then. At my company, AI-companion tools were forcibly installed in everyone’s browser, soon followed by a press release parading how “100% of people at our company now use AI because it’s so great”. Attempts t
49.
by placardloop 2y ago
It isn’t even close to being the greatest tool in human history. This type of misunderstanding and hyperbole is exactly why people are tired/bored/frustrated of it. The uncomfortable truth is that AI is the world’s greatest con ma
50.
by placardloop 2y ago
AI is really bringing out the worst in capitalist corporatism. I think even the most pessimistic AI doomer will agree that the technology is fascinating and can do some cool things, but our corporate overlords have made it such an all-encom
51.
by placardloop 2y ago
Amazon Nova is a foundation model created by Amazon and is offered as one of the models you can use in AWS Bedrock, so the model gets a marketing page for it. Note that Llama also has an AWS marketing page (as do other models), but that doe
52.
by placardloop 2y ago
This isn’t an AWS product, it’s Amazon (the non-AWS side). I don’t think this has anything to do with AWS billing. AWS already has Amazon Q, which is its chatbot offering for AWS customers.
53.
by placardloop 2y ago
The GriGri does not have an autobrake. Petzl is very intentional in saying it is an “assisted braking device”, not auto braking. If there is any tension at all on the rope (even just lightly being held), then the GriGri will likely brake,
54.
by placardloop 2y ago
It’s kind of funny that people think of “sandboxing” as the main feature of containers, or even as a feature at all. The distribution benefits have always been the entire point of Docker. The logo of Docker is a ship with a bunch of shippi
55.
by placardloop 2y ago
> Additionally, deployments to ECS are typically handled by invoking the AWS API within a GitHub Action, without continuous reconciliation or drift detection. No they aren’t. All of the major IaC solutions (TF, CDK, etc) do ECS deploymen
56.
by placardloop 2y ago
Mentioning “no IaC management overhead” is weird. If you’re not using IaC, you’re doing it wrong. However, GitOps is IaC, just by another name, so you actually do have IaC “overhead”.
57.
by placardloop 2y ago
> Having a (targeted, scope and time-limited) design discussion or giving your candidate some made-up context around an engineering cycle and then doing a retrospective with them You just described a contrived, “unreal” problem. > I&#
58.
by placardloop 2y ago
The “real problems” most companies want people to help solve involve the evolution of products that last for years, involve repeated design discussions, in depth research, and applying retrospective learning. I don’t need someone that can j
59.
by placardloop 2y ago
+1 to all this. It still surprises me how many people, even after being in the industry for years, think the goal of any interview is to “write the best code” or “get the right answer”. What I want to know from an interview is if you can be
60.
by placardloop 2y ago
“Real problems” aren’t something that can be effectively discussed in the time span of an interview, so companies concoct unreal problems that are meant to be good indicators.

More ›