Re: Front-end Driven Applications

On 10/2/2014 5:30 PM, John Yeung wrote:

On Thu, Oct 2, 2014 at 9:35 AM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 10/1/2014 5:47 PM, John Yeung wrote:

If you're in a position to be building APIs, then for the purposes of
the article, I think you count as a back-end developer.

This is my own bias on exhibit. We have a web development group (front
end, yeah?) and they do their UI / UX thing completely independent of
the database. When they need something, I write them a stored
procedure. We cooperate on the interface, but I don't know how it will
look when they're done, and they don't care how normalised (or not) the
stuff is in the database.

Right. So in your case, you have some coordination between front-end
and back-end development, and every time you make a custom stored
procedure, you're increasing the coupling between the front and back
ends.

That would be true if I designed the SP to be tightly coupled to the
front end, but I've been seriously labouring to make those SPs usable by
my own code base as well. It's been a mixed success, but just thinking
about that tends to make these procedures general purpose APIs as
opposed to specific one-offs.

With so many layers of computing and networking in today's world, I
think the thing the article calls FDA is more like one end of a
spectrum, rather than a demarcated category.

I think you're right about that!
--buck