In message , at 10:45:36 on Sun, 15 Jan
2017, tim... remarked:
Ah, a slight light dawns - you think Uber is just an App, and the
tooth fairly provided the backoffice/online platform?
There is no connection with this discussion on the way that
"software engineer" has been Hijacked
and Uber's requirement.
You are still insisting that it doesn't require software engineers
to build Uber's platform?
Jesus, no I am not
You really are not understanding the point that I made
Just to be clear, you *do* accept that the term "software
engineering" applies to the task of implementing Uber's platform?
like all software, yes
Good.
I have written Windows Applications in a past world (starting at 2.0)
Bully for you. Uber's backoffice/online platform is not an
"application".
the back office part isn't, and even when I did work on Win stuff I
had no experience of that.
As to the online part, surely it is, as in "there an app for that!"
In the days of Windows 2.0 there was a Windows app which purported to
produce customised Windows apps. The problem was that both the app
itself, and its offspring were excrutiatingly slow, and the offspring
had a very limited UI feature set.
but it was also possible to write "raw" windows code, that used an SDK.
Yes, however the projects I've been describing are mainly contained
within the online platform rather than the thin client.
Fast forward to today, and the way you make a new Android App is to
use an SDK on a PC (not an Android app on a phone).
This is no different to my writing ARM targeted code on a (Intel based) PC
Indeed, but can you justify your comment "there's an app for that" which
made it sound as if you thought the process of making an Uber app was
trivial?
A huge skills shortage in the areas under discussion.
The one you are now discussing perhaps, but not where we came in
Same area, it's just taken you a while to understand what it was we were
discussing.
This Blockchain tool/process appears to be targeted at database
requirements (if this isn't so you need to tell me)
So there is no point even thinking of using it on a product that
doesn't require a database.
Almost everything these days is data in a database.
it is (/would appear to be) not a useful tool when writing software
for an engineering product.
Blockchain isn't a tool, it's a process (or protocol if you prefer).
Though it seems to be something to do with accessing stored records
(let's call that a database, shall we?)
One way of thinking about it that it's to databases, what bitcoin is
to money in your bank account.
I have no idea what bitcoin is to my bank account
It's money whose existence is held in a distributed form, rather than
centrally in your bank's mainframe.
Bitcoin is a chimera
https://www.ft.com/content/b5d66ed8-...b-680c49b4b4c0
(Sorry, you have to register,
It's trivial to get round their paywall.
but you can read it for free if you do)
Is this the one (29/12/16):
"...most people in the financial world have written it off as a
failed experiment in digital finance, even though the idea
behind a core part of its technology - the blockchain, a
distributed ledger that simplifies transaction processing - has
since moved across into mainstream finance."
Many people would disagree that it has "failed", but as an example of a
widely used blockchain, it ticks all the boxes.
--
Roland Perry