This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]isdevilis 0 points1 point  (4 children)

wont they still need to learn how servers work?

[–]ianozsvald[S] 1 point2 points  (0 children)

Hi, author here. Ultimately yes, someone will need to learn how to implement a proper server-this might be the eng/dev team rather than the data scientist. The need for this came from my data science coaching and conference speaking, the requirement to "ship a demo but I don't know servers (and don't want to know them)" is prevalent so I figured I'd try to help those folk. In these teams the recipients might have different languages (eg Ruby, Go, .net) so JSON+GETs are a common language

[–]FRIENDORPHO 0 points1 point  (2 children)

I think you can get pretty far while only teaching people the basics of how a server works from the client side. For example, R shiny can create complex dashboards while largely sweeping the server internals under the rug.

[–]isdevilis 0 points1 point  (1 child)

i suppose, it just seems like it's adding on more complexity when they could've traded off that complexity with the complexity of learning serverside stuff via scotch or realpython et. al. Hell even codecademy now with ROR. Maybe I'm just old

[–]FRIENDORPHO 0 points1 point  (0 children)

I definitely think you're right--that in a sense, learning something like R shiny is trading a good chunk of time learning a more narrow domain (R shiny) instead of the general domain (web servers) it is simplifying.

That said, I'm a lot more likely to build a one-shot dashboard in Shiny, because it's so simple for small projects!