Forgot your password?
Close
typodupeerror

Submission + - Bank of America kindly asks that you don't share your password with your AI asst (techcrunch.com)

Submitted by schwit1
schwit1 writes: In an email blast to customers titled “Protecting your finances in the Al World,” Bank of America urged customers to never share their username and password with another person or an outside service, “including an Al-enabled tool or agent that offers to act on your behalf.”

You can practically sense the frustration in the person sending the email. Still, customers are increasingly handing over their log-ins as personal AI assistants grow more popular. Sharing your banking username and password with an AI assistant runs the risk that it could do something with your finances without your knowledge, or that your bank thinks someone’s raiding your account and locks you out of it. Worse, a security flaw in the AI assistant could result in it leaking your banking credentials elsewhere, giving financially motivated hackers a way into your bank account.

Submission + - This frog bacterium wiped out cancer tumors in mice with a single dose (sciencedaily.com)

Submitted by fahrbot-bot
fahrbot-bot writes: Science Daily has reported that scientists at the Japan Advanced Institute of Science and Technology (JAIST) have identified a naturally occurring bacterium from the intestines of Japanese tree frogs (Dryophytes japonicus) that demonstrated remarkable anticancer activity in mice. The findings, published in Gut Microbes, introduce a new approach to cancer treatment that uses living bacteria to directly target tumors rather than simply altering the gut microbiome.

In a mouse model of colorectal cancer, a single intravenous dose of E. americana completely eliminated tumors, producing a 100% complete response (CR) rate. The researchers emphasize that these findings are limited to mice, but they believe the results provide an encouraging proof of concept for developing new bacterial cancer therapies.

First, E. americana directly attacks tumors. As a facultative anaerobic bacterium, it thrives in both oxygen rich and oxygen poor environments, allowing it to multiply inside the oxygen deprived regions commonly found within tumors. Once there, the bacterial population increased by roughly 3,000 fold within 24 hours after treatment, directly damaging cancer cells.

Second, the bacterium stimulates the immune system. Its presence attracted T cells, B cells, and neutrophils into tumors. These immune cells then released inflammatory signaling molecules, including TNF- and IFN-, which strengthened the immune response and promoted cancer cell death.

One of the most striking findings was that E. americana accumulated almost exclusively inside tumors and did not colonize healthy organs.

They found that the bacteria were rapidly cleared from the bloodstream, with a half life of approximately 1.2 hours, and became undetectable within 24 hours. No bacterial colonization was detected in healthy organs, including the liver, spleen, lungs, kidneys, or heart.

The treatment caused only mild, temporary inflammation that returned to normal within 72 hours. During a 60 day observation period, the researchers found no evidence of chronic toxicity.

Submission + - Blue Chip - fully US supply chain laptop (anduril.com)

Submitted by fadethepolice
fadethepolice writes: Anduril, arguing that its manuftacuring capabilities are directly applicable to laptop manufacturing is starting a project for a fully 100 percent US sourced laptop. The computer will use a Qualcomm snapdragon SOC. I did not see any information for the OS, but I'm assuming with the type of processor this will be Linux based?

Comment Get Off My Lawn (Score 1) 123

by bmajik (#66395158) Attached to: Firefox Tries to Bring Back the Internet's 'Good Old Days'

Firefox was never there for the "Good Ole Days"

Firefox was a reaction to Mozilla becoming too ambitious and too unfocused.

The Netscape/Moz split was already after things had gotten bad. Moz completely jumping the shark was already bad.

The Good Ole Days were NCSA Mosaic and Navigator 1.1. Before the AOL invasion. Before people on the internet expected you to care about their feelings, and before politicians and mega corps knew how to screw it up.

Once upon a time, having friends on irc or usenet was like the nerd equivalent of _living on a pirate ship_

(except the avg pirate was at least +1SD on the IQ scale.)

It was the last vestige of freedom.

There is no "good internet" with Tay Zonday on it. Or girls.

Comment Re:"Management or Bust" is Stooopid! (Score 3, Informative) 136

by bmajik (#66394384) Attached to: Microsoft Offers Mass Buyouts For Roughly a Quarter of Its Workforce

>I find this very stupid.

I agree with you.

>Some people are good, reliable, and experienced "worker bees" who either don't want to be in management or are not qualified for it. I see no logical reason to get rid of such people, do you?

Agree completely.

>I'm not sure if "Sr. Engineer" means quasi-management at MS

It doesn't.

The people manager track and individual track are separate tracks, and both go all the way to the top. There were hundreds of Partner Software Engineers who didn't have any people management responsibilities. These engineers, because they were Partner level, had a minimum of $1m total comp some years. (The higher your level at MS, the more of your pay at MS is contingent: bonuses, stock, etc. MS has a "low" guaranteed salary and a wild bonus/stock award range, all based on your performance and overall company performance)

There are level 70 people who are not people managers; the job title changes to "Distinguished Engineer" somewhere up there, and somewhere past that becomes "Technical Fellow".

There is a level floor for being a manager; but (effectively) there is no level ceiling for being an individual software engineer.

IIRC, When I left, they wanted people to be Senior level before being people managers. But there were more senior level engineers than senior engineering managers...

Here's some quick lingo: an "M1" is a manager who only has engineers reporting to him. An M2 is a "manager of managers", e.g. an M2 has M1s that report to him - and may have 1 or 2 engineers engineers or support staff. There are also M3s, but M1 vs M2 is the main useful cutline.

MS generally wants an M1 to have at least 5 people reporting to him, but not more than 15. So the "span" is pretty narrow; MS R&D is pretty management heavy, with an M1 typically having around 8 people or so.

(I was an M1 for a few years, then went back to being a normal engineer with no people management responsibilities.)

Being an M1 at Microsoft is kind of a dual mandate: you are given a staff of engineers to go work on a problem that is (was?) too big for one person. The M1 has engineering & product responsibilities (e.g. make sure the right thing gets built on time and works correctly). The M1 also has people management responsibilities (coaching people in their careers, rewards and promo justifications, delivering bad news, etc)

Good M1s wrote code and reviewed code, but also burnt a lot of time in meetings ("what are the other parts of the company that are near me doing?") and individual meetings ("i have 8 people who report to me and I need to have a dedicated meeting with each of them every week to see how they are doing, give them career feedback, etc)

M2s rarely wrote code. They would occasionally write code for some demo or prototype, and then show it to people. If the idea had legs it would get spun off to underlings to flesh it out.

I say all this in past tense because I don't think how it was in 2022 necessary holds in Oct 2026. I know that I am not developing software or managing software engineers the same way now as I was even at the beginning of 2026. AI has changed all of it.

Comment Quick bit of context (Score 4, Informative) 136

by bmajik (#66394016) Attached to: Microsoft Offers Mass Buyouts For Roughly a Quarter of Its Workforce

An article says:

>Employees at internal levels 64 and below received one week of base pay per six months of service, for example, and employees at levels 65 to 67 will receive two weeks of base pay per six months of service, according to offers reviewed by Business Insider.

Within MSFT, here's what those "levels" mean for software dev positions:

68-70: Partner & Above [entirely different comp structure; limited quota]
65-67: Principal
63-64: Senior
61-62: Engineer 2
59-60: Engineer

When I left in 2022, you unofficially had a limited amount of time to make it to the senior band. The "up or out" philosophy very much applied to junior engineers; if you didn't have the potential to make senior engineer (because you hadn't made it yet after x years), you were managed out.

People who made it to Principal could park their careers at the principal level and stay there indefinitely, so long as they were providing good results (but were still subject to random layoffs not based on their own performance)

The VEOs and other "voluntary" downsizing plans have been targeting older, higher-level folks. Yes, those folks are more expensive. They are also more male, more American, and more white.

Comment Re:IPO ~= Rug Pull :: Venture Capital (Score 1) 71

by bmajik (#66393992) Attached to: Anthropic Files For IPO

>I believe the future will include AI but it will be small models that are self-contained and that people have on their own equipment and not not spending vast amounts of money on paying for tokens to third-party companies

Why do you think there will just be one picture of the future?

For sure, self-hosted models will be part of the future (even if they are illegal). But I think paid services will also be part of the future.

Self-hosted and unencumbered workflows are a key part of the future for freedom / autonomy reasons. And for some, economic reasons.

But paid services and private models are also going to continue to exist.

Right now, 99% of humans don't even self-host their own _email_. Not only do they not run it on their hardware/environment, they don't even manage the service on other people's infra. They have no involvement whatsoever in their email service.

Some businesses are going to choose to pay an AI subscription, just like some businesses use cloud services today. In both cases, operating local IT infrastructure isn't their core business.

Comment We need AI-free social media areas (Score 1) 146

I wouldn't be surprised if most of the complaints are from ai bots and not real people.

There's nothing wrong with having a community were AI content is prohibited. In the future, such areas will probably be significantly more valuable anyway.

Some social media site is going to restrict all AI and find that many people would prefer such a community.

This doesn't mean you can't find AI slop online - there's tons of places. Why not have a few that are more selective?

Comment Re:They can, but you can never trust it (Score 1) 173

by bmajik (#66392758) Attached to: Ask Slashdot: Can AI Bots Really Write Most of Your Code?

I don't.

The creator of the pi harness did say that the claude system prompt changes often enough that he had to build his own tooling to try and improve reliability and repeatability.

I'm not convinced the differences in roles I've observed are claude personality differences as much as humans giving different prompts.

Submission + - Will AI expose the rickety infrastructure of the internet? (techcrunch.com)

Submitted by sziring
sziring writes: A startling announcement went out earlier this week: Due to recently discovered vulnerabilities in the open source programming language PHP, website owners had to immediately patch their sites â" or if they couldnâ(TM)t update right away, they should take the sites down to be safe.
On this weekâ(TM)s episode of TechCrunchâ(TM)s Equity podcast, Kirsten Korosec, Sean Oâ(TM)Kane, and I discussed the significance of the PHP-ocalypse and whether weâ(TM)ll see more incidents like this in the future.
Sean called this âoea real reckoning momentâ that highlights how âoewhen you get down to the bone level of the internet,â everything seems to be âoeheld together by glue and dreams.â And with widespread access to large language models and AI agents, itâ(TM)s only going to become easier to find these vulnerabilities. (That said, these specific vulnerabilities were found by human researchers, not AI models.)
Kirsten, meanwhile, wondered if weâ(TM)re about to see the âoenext level of prepper doom [â¦] because you could see how banks could get exploited, and [with] data and privacy concerns, it just feels a lot bigger than we can fix right now.â
Keep reading for a preview of our conversation, edited for length and clarity.
Sean Oâ(TM)Kane: The internet is breaking in lots of ways this week, it seems.
I think the best way to think about this, if people are coming into this kind of cold: How many times over the last 10 years have we had these moments where something breaks or something nearly breaks, where one person maintaining one tiny repro repository as a hobby or whatever happens to catch that something nefarious is going on and and saves us from the infrastructure of the internet completely crumbling?
Now multiply that by a billion, when people have access to not only extremely advanced software in the form of these LLMs that everybody uses, but also the ability to task them to go out and do it themselves, with creating AI agents that are single-minded at accomplishing those things.
Weâ(TM)re seeing a balance of two things happening this week. One is a bunch of the labs and companies like Google and OpenAI actually had people go out and find a bunch of vulnerabilities, including the one with PHP. And then we also have a bunch of people seeming to rush to take advantage of those vulnerabilities to try and hack into websites. So we have governments taking down websites, we have really popular websites that are going down briefly to be able to fix this vulnerability.
This is a real reckoning moment, where weâ(TM)re going to find out the downside risk of building so much of the internet on open source technology like PHP. When you really get down to the bone level of the internet, it is held together with glue and dreams.

Comment Re:They can, but you can never trust it (Score 3, Insightful) 173

by bmajik (#66392242) Attached to: Ask Slashdot: Can AI Bots Really Write Most of Your Code?

How do you decide to trust code you write?

How do you decide to trust code someone else wrote?

Tests. Design discussions. Code reviews. Code review questions. Design Questions. "What about this problem?" Real validation testing.

I was in a funny situation last week. Two different humans told their claude agents to fix the same bug. Claude came up with two _slightly_ different implementations.

I told _my_ claude agent to code review both implementations - using a new prompt I'm working on to try and automate away a lot of the code review value I was adding manually.

Same model; same bug, two implementations, and the code-reviewer agent found different bugs in both PRs.

We ended up blending the best things from both PRs into the one that shipped.

I am really confident that the code I ended up shipping here is better than what our specific humans would have done without using AI, and 10x-100x faster.

I am spending more of my time telling agents how to think like me, what to look for, what tradeoffs to make, etc. They wont do those things unless I tell them to. They don't always do those things perfectly.

(Neither do the real human software engineers who work for me.)

Slashdot Top Deals

A CONS is an object which cares. -- Bernie Greenberg.

Close