florind

https://blog.newsplore.com/2017/07/31/zero-to-image-recognition-in-60-seconds-with-tensorflow-and-spring-boot

https://blog.newsplore.com/2016/12/22/on-engineers-and-technicians

http://blog.newsplore.com/2015/09/11/five-years-of-weather-in-a-timelapse

http://blog.newsplore.com/2015/09/03/a-tinygps-upgrade-adding-nmea-v3-0-and-glonass-support

https://github.com/florind/what-runs-where

What-runs-where is a service that parses and aggregates the version strings of any number of web services which choose to publish their version. It is useful when you have several testing&prod environments where several versions of your web services are running and you want to have a quick overview of what runs where. Live example hosted on Heroku: http://vast-brook-8589.herokuapp.com/

https://github.com/florind/Gborders

Live border overlay for Spain: http://blog.newsplore.com/wp-content/uploads/2009/03/embedmap.html

http://blog.newsplore.com/2011/09/09/bootstrap-your-nodejs-project-in-the-cloud

So you have a great website idea and you want to build and bring that first version online as fast as you can. You figured that node.js is the way to go. You kick-off the development and after a couple of hours of hacking you realize that although you’re progressing at breakneck speed you’re missing a few important bits...

http://blog.newsplore.com/2011/03/23/a-comparison-of-places-apis

A side-by-side comparison of the main features provided by the major Places API providers.

http://blog.newsplore.com/2010/06/27/building-a-content-aggregation-service-with-node-js