<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.0.0">Jekyll</generator><link href="https://ebababi.net/feed.xml" rel="self" type="application/atom+xml" /><link href="https://ebababi.net/" rel="alternate" type="text/html" /><updated>2020-04-11T15:25:34+00:00</updated><id>https://ebababi.net/feed.xml</id><title type="html">ebababi</title><subtitle>Mutters about programming et cetera</subtitle><author><name>Nikolaos Anastopoulos</name></author><entry xml:lang="en"><title type="html">How the Ship of Theseus Relates to Major Code Changes</title><link href="https://ebababi.net/how-the-ship-of-theseus-relates-to-major-code-changes.html" rel="alternate" type="text/html" title="How the Ship of Theseus Relates to Major Code Changes" /><published>2019-11-23T00:00:00+00:00</published><updated>2019-11-23T00:00:00+00:00</updated><id>https://ebababi.net/how-the-ship-of-theseus-relates-to-major-code-changes</id><author><name>Nikolaos Anastopoulos</name></author><summary type="html">On the news: A couple of weeks ago at Mozilla, the final commit removing “XBL” has been pushed. That means that after years of effort they’ve completed the process of migrating the Firefox UI to Web Components. That story reminded me of the Ship of Theseus thought experiment. What? How is that even related?</summary></entry><entry xml:lang="en"><title type="html">Dockerfile for Ruby on Rails Deployments</title><link href="https://ebababi.net/dockerfile-for-ruby-on-rails-deployments.html" rel="alternate" type="text/html" title="Dockerfile for Ruby on Rails Deployments" /><published>2019-11-10T00:00:00+00:00</published><updated>2019-11-10T00:00:00+00:00</updated><id>https://ebababi.net/dockerfile-for-ruby-on-rails-deployments</id><author><name>Nikolaos Anastopoulos</name></author><summary type="html">We recently climbed the train of Docker images for production deployment at work, so I found myself in need of a good tutorial on Dockerfiles. Although there is a lot of information on Dockerfile best practices, the Ruby on Rails guides I looked up were a little bit outdated for modern applications. On top of that, the Rails official images are deprecated for some time now, so the task of creating a Dockerfile became challenging. I’ll go step-by-step on what I ended up with, explaining my thought process and any issues I stumbled upon along the way.</summary></entry><entry xml:lang="en"><title type="html">My 2¢ to Those Interacting with FANN</title><link href="https://ebababi.net/my-2c-to-those-interacting-with-fann.html" rel="alternate" type="text/html" title="My 2¢ to Those Interacting with FANN" /><published>2019-08-11T00:00:00+00:00</published><updated>2019-08-11T00:00:00+00:00</updated><id>https://ebababi.net/my-2c-to-those-interacting-with-fann</id><author><name>Nikolaos Anastopoulos</name></author><summary type="html">Summertime at last! As always, I needed an interesting topic to explore as a side-project (in parallel to my efforts to rest), and I thought of neural networks. After all, AI is catchy these days 😜 I tried to keep the side-project scope small: just take some social networks shares, encode a bunch of their attributes in a neural network and, after training, try to predict the social impact of these shares. So cool, right?</summary></entry></feed>