Home

on drawing circles

2017/07/06

The way you draw circles says a lot about you, claims a post that popped into my INBOX today. Indeed I thought, since I was reminded of an older post about Giotto and his true mastery drawing the perfect circle which kind of also required that you were able to recognize the craftsmanship.

Which keeps me wondering what the perfect circle for DevOps would be? At least for this point in time.

Advertisements

Ο φίλος μου ο Παναγιώτης άλλαξε το cover page του σε αυτό εδώ και με πήγε χρόνια πίσω.

sprite

sprite magazine

Τότε που μαζευόμασταν στο σπίτι του Τάκη και παίζαμε στην Amiga Kick Off 3. Ο Παναγιώτης είχε αναπτύξει την θεωρία της “ψυχολογίας του sprite” για να εξηγήσει κάποιες ενέργειες των παικτών στο γήπεδο. Γελάγαμε μεν, αλλά δεν είναι πως είχε άδικο ο Παναγιώτης. Γιατί δεν ξέρω για το Kick Off 3, αλλά στον Pac Man, τα φαντάσματα είχαν συγκεκριμέμενες, καθόλου τυχαίες συμπεριφορές:

In an interview, creator Toru Iwatani stated that he had designed each enemy with its own distinct personality in order to keep the game from becoming impossibly difficult or boring to play.[4] More recently, Iwatani described the enemy behaviors in more detail at the 2011 Game Developers Conference. He stated that the red enemy chases Pac-Man, and the pink and blue enemies try to position themselves in front of Pac-Man’s mouth.[5] Although he claimed that the orange enemy’s behavior is random, the game’s code reveals that it actually chases Pac-Man most of the time, but also moves toward the lower-left corner of the maze when it gets too close to Pac-Man.

Το ήξερα χρόνια αυτό, από όταν είχα διαβάσει για τις μυρωδιές, αλλά μόλις μου το θύμισε μια φωτογραφία.

I am doing a variation of spaced learning with the books I am currently reading. It flows almost naturally, since three of them have similar (economic) premises:

I highly enjoyed reading the first three. Last week I was switching between them every hour (I was on vacation and got a lot of downtime and reading time). Not that I did not like the fourth one, but the first three make a nice economics spaghetti.

And thus concludes a short blog post after some silence.

I won’t pretend that I’ve read it. I’ve read critiques of it, I’ve read a book that heavily relies on it and I’ve gifted the iPad app of it twice I think. But now, according to Wolfram, it is available for free download:

http://www.wolframscience.com/nks/

You can download each chapter individually in PDF and use something like pdftk to concatenate them.

No, I will not even pretend that I will try to read this. I have other weird books in the pipeline. But still automata appeal to me, so the occasional glimpse may happen. Then again, the web version has been there for years and I’ve browsed it very few times.  Time is a resource that I cannot devote to Wolfram’s thought it seems.

 

Δεν είμαι φαν του Πετρίδη και του Ζουγρή. Περιστασιακά τους άκουγα και ακόμα σπανιότερα τώρα (είναι κάπου μετά το Βήμα FM, δεν ξέρω). Όμως έστω και έτσι μια κάποια ανακούφιση μου την έχουν προσφέρει (ειδικά την περίοδο της Θητείας). Το να “κεράσεις” έναν εσπρέσο τον Πετρίδη δεν είναι κάτι παράλογο, ειδικά αν σκεφτείς σε τι μπούρδες και απίθανους ανθρώπους έχεις δώσει τα λεφτά σου κατά καιρούς.

Και πόσο πιο καλά νιώθεις όταν σου στέλνει για ευχαριστώ ένα PDF με τα 200 καλύτερα rock album κατά τη γνώμη τους. Μπορεί να μην τους ξανακούσω ποτέ, αλλά πλέον μπορώ να ανανατρέχω.

Πατήστε “donate” στο site τους: http://www.apotis4stis5.com/

The Goal

2017/05/09

Well if you’re doing DevOps (whatever that means for you) you’re supposed to have read The Phoenix Project (which I have). Inside the Phoenix there are constant references to Visible Ops and The Goal. Well, The Goal is a something of a gospel it seems so I went ahead a few months ago and read it.

It is a far better book to read than the Phoenix. Much more entertaining and insightful. I guess Goldratt is a better writer. The book does a hell of a good job to explain the basics of The Theory of Constraints which receives new attention in this age of software automation and pipelines and the perceived “clash” between DevOps, ITIL and any other related acronym. I see ToC posts pop up weekly now. The only thing that you may not like in the book is the technology from the 80s, but only if you’ve never used it.

My best part was the really nice simulation example it used to make clear a counter-intuitive result and his family crisis management. Granted, many things went the right way for the main hero, but hey, the author was trying to make a point and needed a vehicle. Fiction is not life.

I read it from the latest kindle edition. According to my Kindle I am still at 97% of the book and that is because right after the end of the book there is a paper explaining some of the concepts with real industry examples. The boredom to read this after the turmoil the hero has gone through is evident. It also explains why the author needed a novel in order to engage you in ToC.

Like a good friend said: “I really want to get in the book and help him out!”

Memory gets triggered in the most unexpected ways. I maintain a fairly large library of printed and electronic books (most of them DRMed -the light cases socially, kindle and Adobe locked the rest unfortunately) on subjects that interest me. It is fairly evident that I will not read them all, but I always have a book (and sometimes a paper) to recommend to a friend that has a problem. It seems that I am not the only one that thinks that personal libraries are supposed to be full of unread books.

Anyway, I was listening to Podcast.__init__ Episode 95 and one of the guests mentioned Parsing Techniques – A Practical Guide by Grune, I think it was when they touched Earley parsers and how most books about parsing do not really touch on how the actual parser is built. Wait a minute I’ve got that PDF! And you can go to the author’s site and download it. And you know what? There is a second edition out. For > 100 euros for a DRMed PDF I may not buy it since parsing is definitely not my thing, but somebody else out there might need the second edition. Judging from my skimming of the first edition, this is close to the encyclopaedia of parsing. I will go through some pages tonight.

Just for a refresher.