I kept seeing this headline...but this is the first time I've seen it from a credible source.
I think we've lost the sensitivity to respond to this nonsense. Years of rage baiting etc.
I think Trump could take full autocratic control of this country and nothing would happen at all. Not from the citizens, not from congress. It would be business as usual as we shushed our nerves with "this is just fake news" or "I'm trying to live an unplugged life" or "if it was really bad somebody would do something about it"
Using AI lazily is a problem though. Writing code has never been the most important part of software development, making sure that the code does what the user needs is what takes most of the time. But from the github issues and the comment here from the few who have tested the tool, it looka like the author didn't even test the AI output on real PDF.
If you use AI to build in 3 month something that would have taken a year without it, then cool. But here we're talking about someone who's spending 2-3 hours every other day building a new fake software project to pad his resume. This isn't something anyone should endorse.
Sure, if the warning levels are poorly tuned I might configure my LSP to ignore everything and loosen the enforcement in the build steps until I'm ready to self review. Something I can't stand with Typescript for example is when the local development server has as strict rules as the production builds. There's no good reason to completely block doing anything useful whatsoever just because of an unused variable, unreachable code, or because a test that is never going to get committed dared to have an 'any' type.
An example I like to use are groups that put their autofmratter into a pre-commit. Why should I be held to the formatting rules for code before I send my code to anyone?
I'm particular about formatting, and it doesn't always match group norms. So I'll reformat things to my preferred style while working locally, and then reformat before pushing. However I may have several commits locally that then ge curated out of existence prior to pushing.
Not if I push my branch it to origin. But until I do that, it's none of your concern if I do or don't. Once it gets thrown over the wall to my colleagues and/or the general public, that's the point where I should be conforming to repo norms. Not before then.
Surprisingly, 3GB is a real practical RAM limit for aws lambdas in 2025: you can only have more than that if you submit a support ticket. But it's not really mentioned anywhere in the docs.
The default Lambda quota for all accounts is 10240 MB. I've never seen it below that (in recent memory, at least), even on fresh accounts not connected to a big org.
I know I routinely use 10gb of RAM for my account that's never talked to support for the related CPU allocation.
I think we've lost the sensitivity to respond to this nonsense. Years of rage baiting etc.
I think Trump could take full autocratic control of this country and nothing would happen at all. Not from the citizens, not from congress. It would be business as usual as we shushed our nerves with "this is just fake news" or "I'm trying to live an unplugged life" or "if it was really bad somebody would do something about it"