I see the cons indeed, however I thought it would be really cool to continue training of a promising model in a more capable environment in just a couple of click.
Anyone who is messing around with convolutional networks is almost guaranteed to have anaconda installed. The convenience of a few less clicks in exchange for platform lock-in is exactly the devi's deal that the 3 major cloud providers have started doing.
Think really hard about the implications of enabling them. Do you want a future where Google® Colab™ is the primary way to work with data, where personal computing is dead and replaced by cloud? That's what they are striving for with this strategy.
Location: France, Lyon
Remote: Yes
Willing to relocate: Yes
Technologies: JS, ReactJS, Python, Node, PHP, Docker, System admin, Architecture | Hobbyist in Machine learning, Scikit-learn, TensorFlow
Résumé/CV: https://www.dropbox.com/s/ve2dpa6abofr3e6/Emmanuel%20Chappat%20-%20Resume%20-%20Full-Stack%20Developer.pdf?dl=0
Github: https://github.com/m4nuC
Linkedin: https://www.linkedin.com/in/chappatemmanuel/
Email: emmanuel.chappat@gmail.com
I have been building web apps for a decade and I've touched at every aspect of the process, from design to DevOps.
I am looking for remote mid/senior Full-stack work OR entry level Machine learning (will take a pay cut there as I am still learning.)
Rants without proposing any alternative solutions can't redeem any use at all. Their only reason to be is to wrongly make their authors feel smart or skilled.
He proposed list of languages. And really, there's a lot of good languages to use on the servers. JS was never good language and we use it on the client-side just because it's the only language browsers know.
He doesn't explain why... other than ranting about the callback model (which has been in our desktops forever, most event systems rely on callbacks). The quote in the post has also misleading statements, NodeJs does scale in load and performance which is one reason why people use it instead of Python (which was one of the quote suggestions)
That was not one of his suggestions, unless you count stackless python. It was an example (i.e. twisted in python) in support of his point that callback's are a bad way to structure concurrent programming. His suggestions were Erlang and Go which are arguably better approaches in a purely technical dimension to NodeJS.
What his rant misses is that most technical decisions aren't made on purely technical merit for a host of different reasons.
>His suggestions were Erlang and Go which are arguably better approaches in a purely technical dimension to NodeJS.
I would say that it is based on a subset of the technical dimension. Maybe Erlang and Go might have nicer ways to handle concurrency flows but if it doesn't have a library X to communicate with backend component Y then there is a technical reason not to use it.
>the fact that it lives in the web stack right next to the presentation layer, really sucks (I think)
I can't see by what logic the interviewee arrived to this conclusion. How is the presentation logic out of place in the presentation layer?
Modern API/consumer based architecture make way more sense than having MVC structures where business logic, storage logic and presentation logic intertwine.
I'm a fullstack software developer with 10 year experience, living in between France and China (theses days mostly China). I am deeply passionate about solving real world problems with the cleanest and the simplest possible code. I am currently looking for a steady remote work, ideally a development studio.
