Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror

Comment Re:VERY IMPORTANT CORRECTION (Score 1) 140

That being said, the article DID make clear that there WAS a court order for him to disband the account, and even if he was using in all the right ways for all the right reasons, not-complying with a court order is extremely problematic.

Then her remedy is to go back to court and compel the target of the order, aka the ex-husband, to do as ordered, not to claim that a third party with no standing in the case is at fault.

If you and I contract that I will sell you may Ford Escape for five grand, and you give me five grand and I don't give you the keys, you don't go to Ford and ask them to make you a key. They will, correctly, say "....and what does this have to do with us?" when you wave the sale contract at them.

Comment Re:In what sense can't Apple do anything? (Score 1) 140

And nothing Apple did or didn't do prevented the mother from having that custody.

She had a remedy from day one: make new accounts for the kids. Inconvenient? Sure. But way less inconvenient than most of the stuff that goes along with 'we're separating.'

*Should* Apple develop a system to deal with this a big more gracefully? I'd say so. But to conflate this with 'they're violating a court order for custody' is utterly ridiculous.

Comment Transparency and verification (Score 1) 65

Easiest solution is to issue employees a corporate credit card that they are responsible for. All reimbursable expenses have to be correlated against the copy of the statement issued by the credit card company to the corporation.

But what about cash expenses, you ask? Issue a per-diem for travel, and a periodic "here's your budget for IT refresh, whatever you don't spend, you get to keep."

My question is, what kind of receipt fraud are we looking at? Invented expenses that they're using to defraud the company, or real expenses that normally wouldn't be reimbursed that they're disguising as reimbursable ones?

Also, wouldn't invoice fraud be a bigger threat? Fake suppliers sending you real looking invoices in the same of actual suppliers, but with the bank details modified to point to the scammer's accounts instead? Instead of hundreds of dollars in fraud perpetrated by dozens, maybe hundreds of insiders (employees), you get tens, if not hundreds of thousands dollars of fraud perpetrated by outsiders trying to pretend that they're trusted suppliers. Or worse... an insider at your supplier deciding to doctor the outgoing invoice so they can skim money off the top...

Comment Re:Like debugging Java or C# is any easier (Score 1) 99

Learning COBOL is relatively easy (although there are some dialect differences between say, gnuCobol and the COBOL used on IBM mainframes). Learning Z/OS and JCL on the other hand...

There are resources, though... for example the Open Mainframe Project:

https://openmainframeproject.o...

As they say, if you want a job for the rest of your life, learn to work on mainframes...

Comment Re:Covid? (Score 1) 99

You're assuming the remaining old dude (or dudette) is maintaining the code at this point. They could just be serving the role of whacking people with sticks to keep them from accidentally pulling on the thread that is keeping the whole system working, and making loud noises if some new boneheaded manager tries to kill the system without realizing that doing so would cripple the entire company.

Being the last person who understands what all the components are supposed to do and why they are important is not the same as knowing how to modify and maintain said components.

With that said... there's still going to be a crisis when this person announces their retirement...

Comment Cobol (Score 1) 99

A mainframe system that has survived multiple waves of "this is the new thing" has one of two things going for it:

1. It works fine and isn't broken, and handles way more thoughput than any alternative proposed without having to spend a stupid amount of money.

2. Nobody understands how the code and logic work, and nobody wants to touch it for fear of breaking it, and all the prior migration projects failed miserably, so much so that there's no money or will to try again. So even if they want to change how things work, they can't.

The two are not mutually exclusive, but #2 tends to be more the case for a system that desperately needs an upgrade, which I'm assuming all these unemployment systems are.

With that said... systems tend to reflect processes and culture, so I don't have high hopes for replacing just the mainframe, to fix the problems that they had/are having.

Slashdot Top Deals

When a Banker jumps out of a window, jump after him--that's where the money is. -- Robespierre

Working...