Sure, and delegated authority over an account is a well established process at all banks. It would be technically easy to add your trusted friend to your list of 'authorised users' and have them able to withdraw the money. Or issue your friend with their own card linked to your account.
Yup, SSMS is far, far better than pgAdmin. SSIS is years ahead of any postgres ETL tool. There's a bunch of other awesome features in SQL Server too - from memory merge doesn't work in Postgres, procedures/functions are harder to use and
I wasn't trying to say Postgres is all-round better than SQL Server. But there are a few things including R integration and spatial queries where Postgres is so far ahead that you are probably better to put up with the weaknesses.
MS SQL has a lot of good things going for it - but what you're asking for is one area where Postgres just runs rings around it. You can achieve similar benefits in MS using a CLR but it will be faster and easier in Postgres. Unless you have some compelling reason to stay MS, I suggest you take the hit and learn a new platform.
I'm guessing they'll slowly phase out OLAP.
OLAP got its stellar retrieval speed through lots of precomputation and that just isn't compatible with where the whole big data stuff is going. I'd guess instead they will bring in a NoSQL database as a per-table query engine and use that as the OLAP replacement.
No - MS will only need to release any changes they make to R.
This sort of thing comes up quite often and largely comes down to coupling. If Microsoft included R code in the binary of SQL Server then they would run into complications. However as long as they keep R on its own and arrange interprocess communication sensibly, they will not be affected by the GPL.
It's quite likely MS will modify R, e.g. writing low level routines for getting data out of SQL without needing to go via ODBC and those sort of changes will need to be released. It's also possible MS will want things like
Incidentially, this has been done before. The PgR project gives Postgres (BSD) has tight coupling with R (GPL) without requiring Postgres to be relicenced. Tableau also released similar features, though they don't add much value at this stage.
Because it's just like new for a tidy little discount. Why pay full price when you don't have to?
The $79k car you picked out had a couple options that put it to $91k new, so you're getting a one year old car for 15% off. I think that's about right.
The controls was a bit excessive with 8 movement keys, 8 gun aiming keys plus action and shoot - you certainly got good at contorted finger manipulation in order to wander around a room with your gun always pointing the right way. But very few future games beat the immersion that was created - I think the way that a single bullet sunk you lead to much better immersion.
Er, yes, of course it is. Tesla is not an Iowa company. Iowa customers are. When they buy off Tesla, that's an interstate commercial transaction.
it's pretty damn hard for a state like iowa to tell Tesla what they're doing is illegal when Tesla can point to a federal ruling that preventing car manufacturers selling cars to the public is legal. Until Tesla have that ruling all they can point to is legal opinions which carry a lot less weight.
Also the camera could be set to encrypt to a set of keys that only a limited number of people have access to - the officer, their superior, a couple 'court' keys, etc.
That way even if it records everything, that recording is inaccessible without a court order or similar.
Not a lot. Say you design a new heuristic for playing chess, you've now built a chess engine.
Say you build a tool which people can load new heuristics into - perhaps a variation of best first with your own pruning algorithm, you've now built an AI engine.
That was a lot of fun. I only got 45.
Yes, they've 'solved' it. Basically when you hit the start button you take liability.
First it lost its planetary status, and now the moon is classed as a planet for this competition.
Accountant - agreed, my point was many people refer to 'accountant' where they mean bookkeeper. I do not see computers replacing good accountants - if anything it will make them more important as the better raw data gives them more ability to make a difference.
But I completely disagree on your description of what current accounting software can do. Computers are opening the post (email) for remittance advice, chasing short payments and reconciling the ledger. They flag over-payments but leave chasing them to a person - too much thought required on the communication. They also collate expense receipts and chase staff for the various tasks coded into workflow (singoff from immediate manager, tracking against budget and authorisation limit, flagging suspicious values to appropriate people, etc). Paper invoices are also handled - scan it and it's emailed off to manually assisted invoice creation (too much variation in invoices for risking automated loading). Oh, and all purchases are also directly exported to the bank where you can configure them to either just be paid or require final authorisation depending on how reliable you feel your setup is..
They already integrate with stock tracking systems and so eyes they do depreciate stock, handle damage and lost items. Stock isn't something I have firsthand experience managing, but I haven't heard any complaints. Timesheeting and payroll are also fully integrated and I know they both work well.
Current state... I see an opportunity to help someone out. I create a quote in the accounting software. I email that quote to them and if they decide to go ahead then they create a corresponding PO in their ERP system. That process automatically checks against signoff limits, obtains approval from direct manager, etc. That is then automatically emailed to me where the accounting software automatically matches it to the quote. I then deliver the work and get them to sign it off. Once that's done I click a button to convert the quote or the PO into an invoice, adjust if necessary and click send. Again now their system receives that invoice, matches it to the PO and emails my contact to validate the work was signed off as complete. Then it schedules it for payment and sends remittenance advice. That gets matched by my software which sets the invoice expected date. When the payment is made it reconciles against this invoice. If they don't pay then it automatically kicks off whatever workflow I choose to set up - friendly reminders by email with summary of outstanding and a note to me.
Sure, it's not perfect and there's still a need for bookkeepers. Someone screws up the reference code on the payment, accidentally double pays. Subcontractors who charge a different rate depending on which client they're working on, reversing out declined expense claims, client or supplier correspondence beyond simply sending out statements, etc. But compare it to say 5 years ago - I wouldn't feel very safe as a book keeper.
Computers _are_ replacing accountants. Or more precisely computers are replacing bookkeepers and a lot of so called accountants are actually bookkeepers.
Most of the drudgery is leaving the profession now. What's left will be much more interesting and valuable work, but I suspect there will be a bit of a glut in lower end accountants.