I have never understood this argument. What is exactly the problem with identifying the executed code?
If you inject the bean and call the method you will get caching (because you are using the proxy). If you call the method from within the bean itself however you're not using the proxy and you won't get caching.
It's stuff like this on steroids when you start mixing annotations that makes it really difficult to reason about the code.
I mean sure, if it keeps things fresh and keeps you moving it's better than nothing but that's not a good structure if you want to progress past a year of training or do anything serious.
Literally just doing a random program like the reddit recommended BWF routine is vastly superior and doesn't require chatgpt or serverless or anything..
When I read one of these articles or posts, I usually expect to see concrete prompts, their output, and how they can be used to speed up development. Instead all I see is generic vagueisms; "it helps me write unit tests", "it helps me code faster", or in the case of this article "it’s taken over how I plan, design, and implement software." with little to no real examples of how this works. It almost feels like people want to brag that they've discovered "the secret sauce" rather than help others understand how to use it.
I've tried multiple times now to use ChatGPT. In every case ChatGPT has produced code that has bugs, needs to be double checked, or simply straight up doesn't work. It IS impressive how it's able to create code that seemingly does what you ask, and it's lightyears ahead of other products, but in no way have I found it to be a gamechanger. IMHO, at best it might steer me in the right direction, and at worst it completely wastes my time. Seems pretty overhyped to me.
In several occasions it has produced code that took me longer to fix than just reading the documentation and in almost all of those cases it couldn't help me find the issue and I actually had to read the documentation anyway (it took just seconds to pinpoint the missing clue).
Something it seems really good at is unix commands (regexes, awk expressions, pipes and bash intricacies) so I do use it a fair bit for that.
The scanner has seen the credentials, yes, and it's then up to the individual to decide if that credential should be considered "compromised" or not (seeing as the Github scanner has seen that credential)
It's a step up from - oh sh*t everyone can see it and the user isn't even aware that they did the dumb
The screenshot says just amend the commit and all's good
Also I feel fairly confident Github/MS aren't about to change their business model to become a blackhat hacking collective
The message says to remove the secret from the commit but the actual action to take would be to rotate the secret since it's been exposed to github, no?
PayPal seems to be unique in being able to take payments from a passive web page, because the customer conducts their transaction at PP's website.
This is why I continue to use PP for my tiny little business (without eBay). Even though I consider myself reasonably tech savvy, I don't trust myself to maintain a website that is compatible with everybody's browser, phone, etc., and that guarantees the security of their personal data. Moving to another payment processor requires a quantum leap in technology that I'd rather not keep up with. I'd rather design another gizmo.
From time to time I look around for an alternative to PP, and haven't found one yet. I suspect that many small-time eBay sellers may be in the same boat.
There's a shared secret you can use to verify the payment when they callback to you after payment, and their HPP is skinnable.
[1] https://docs.adyen.com/developers/api-reference/hosted-payme...