>starting with the problem they need to solve and focusing on the minimum needed to just solve that problem
To be fair if held strictly to these principles their work would revolve mostly around gluing together various Apis, services and sometimes adjusting already written software to company's needs. So I'm not surprised they are using every possible opportunity to write something here and there, this menial digital plumber's work takes its toll and one needs to try to squeeze in something a bit more enjoyable from time to time just to keep sanity in place a bit longer
When I WAS the bane of my existence was senior and staff engineers hoarding all the fun, new work for themselves and forcing me into "bitch work" where I'm just cleaning up old, broken code and handling bugs. I finally got promoted because I explicitly ignored my manager to deploy changes that were needed for my company, and that was what finally got me promoted. Of course, at that point, I had been looking for a new job and just left instead of taking the shitty, bottom-of-band promo increase.
It's awful for promotion chances, and it forced me to quit.
Not just politics, I almost feel it can hamper you as an engineer. If you just do basic plumbing for 10 years, are you really an engineer with 10 YOE or one with 2YOE 5 times over because everyone needs a plumber?
2-3 years seems to be where that valuable plumbing experience starts to plateu. I don't know how engineers these days that move companies every other year even get a chance to grow when you're doing a soft restart at every job hop.
> When I WAS the bane of my existence was senior and staff engineers hoarding all the fun, new work for themselves and forcing me into "bitch work" where I'm just cleaning up old, broken code and handling bugs.
Oh how I relate to this...
That's why these days I go out of my way to "save" interesting work for my junior colleagues and have them grow through it.
In my perspective the interconnection between all their services paired with lingering danger of all encompassing ban in case of perceived misuse is serving as big deterrent - I won't be trying any Gemini or AI offer from them because I don't want to have all my accounts banned without recourse in case of for example some incorrectly interpreted "cyber" usage.
Assistant booking a place for me is last thing I'd want, I want to see ratings, photos, overall look&feel of the place, not spin the wheel and get some random place booked
a) I won't trust booking's own assistant or "AI" and it will be garbage if/when they introduce it (despite fact that in order to handle it correcly it would need to have amount of information about me and my family and my trip that im not comfortable to provide them)
b) They will block 3rd party/independent assistant via CF or other measures - they want you to be on their property browsing on their terms upselling you features, not access via API/MCP
c) chat interface and general UI clunkiness related to AI and this kind of use case - when browsing booking I'm able to narrow to offers I want quickly, where accommodations are located on the map etc, lol, just thinking about doing all of that via chat UI and even more via voice interface makes me tired
What I would do if I were manufacturer hellbent on spying would be to search for devices of my own brand nearby to pass data using their internet access, if no access found then extend search - basically p2p/mesh network to pass data.
I haven't been around HN toooo long, this is the first time anything posted here has brought a tear to my eye. That's very sweet, and I'll be throwing a little rebeccapurple in to projects from here on out.
How does it work that some service that most people never heard of distributes (paid) images with alleged fix for vuln 24h before official vuln fix/image is available? Seems somewhat shady.
Mindboggling, wtf don't they release it if its ready and exploit is in the wild, its a lot of time until 14:00 UTC and a lot of websites will be breached.
They should have shut up, released a new stealth PHP version and told everyone to update ASAP. They gave way to many details ahead allowing some AI agents to find the vulnerability within half an hour...
The update was withheld because releasing it without notifying major providers and distros would turn it into the same race, with ai having a release is the same thing as a disclosure.
This would've worked if other people were able to shut up about it. Because its existence got leaked they posted the announcement
There is no functional difference between doing just an announcement and doing an announcement with a series of builds containing the patch while withholding the source code. You do understand that right?
A message as vague as "there is a major RCE somewhere in this entire programming language" is usually pretty safe. We'll see how the details actually got out in this situation and whether the announcement caused it, but it still took a while. If you put out a patched build people will find and decompile the changes nearly instantly.
One security provider put "session.upload_progress.enabled, session.use_strict_mode" in the SEO keywords for their initial announcement, which was probably a good enough clue to feed to an LLM. https://web.archive.org/web/20261021005246/https://sansec.io... (go to page source, search for session.upload_progress). At least one person on Twitter saw this: https://x.com/its5q/status/2112700519261032497 Of course there's enough people who knew about this that the exploit vector may have leaked out to the general public through a different source as well.
Yep. It's probably one of a handful of functions. It'll be based on request input, a script doesn't have to call the function, and it works with default configuration. I bet it takes a half hour for AI to figure it out.
Php4 -> 5 was a massive change including zendengine2 and an overhaul of many modules. Fortunately that information really doesn't tell us much. (Also it was a year of work between the first beta and the release - many changes at that time)
I mean an agent can walk those changes, but it's close to just walking all the whole source / research from scratch at that point.
A patched build is strictly more information, and you'd only need to cross correlate between the two.
At this point shipping the build already may have been the best option but not necessarily everyone is actually able to ship yet. And this is of course assuming the actual vulnerability is the same one as the PoCs that are being tried, and not something even nastier instead
He won't care because he has established position and is set. It will be just like everybody else - if the individual is at the top of the food chain then he/she is all over it how you are using it wrong and how you should use it (don't forget to follow and subscribe).
Yep, that's what I see in the CS field -- people at the top are advocating AI and don't understand why the hell the others are hesitant. I meant the top engineers, not the management. I look up to them because of their skills, but that doesn't mean I need to agree with everything they said.
To be fair if held strictly to these principles their work would revolve mostly around gluing together various Apis, services and sometimes adjusting already written software to company's needs. So I'm not surprised they are using every possible opportunity to write something here and there, this menial digital plumber's work takes its toll and one needs to try to squeeze in something a bit more enjoyable from time to time just to keep sanity in place a bit longer