<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Michael Demetriou on Medium]]></title>
        <description><![CDATA[Stories by Michael Demetriou on Medium]]></description>
        <link>https://medium.com/@qwazix?source=rss-75498c7cf7a5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*eMr3NefEcKIt0L2bELLYmQ.png</url>
            <title>Stories by Michael Demetriou on Medium</title>
            <link>https://medium.com/@qwazix?source=rss-75498c7cf7a5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 08:30:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@qwazix/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Introducing print3d.social and the fediverse]]></title>
            <link>https://medium.com/d-e-weblog/introducing-print3d-social-and-the-fediverse-6b5145cb3ceb?source=rss-75498c7cf7a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b5145cb3ceb</guid>
            <category><![CDATA[photos]]></category>
            <category><![CDATA[print3dsocial]]></category>
            <category><![CDATA[3d-printing]]></category>
            <category><![CDATA[fediverse]]></category>
            <category><![CDATA[3d-printer]]></category>
            <dc:creator><![CDATA[Michael Demetriou]]></dc:creator>
            <pubDate>Fri, 12 Apr 2019 12:45:25 GMT</pubDate>
            <atom:updated>2019-04-12T12:45:25.201Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>The what-verse?</strong></p><p>Do you know what the <em>fediverse</em> is? It’s a social network. How do you join? You pick any one of the services on the fediverse that you like and join that. Imagine if you could follow your favorite YouTube channel from twitter and get to know every time they post a new video, without them having to go and post on twitter. Imagine if you could also reply to their videos in twitter and the replies showed below their video in YouTube. Doesn’t it sound awesome?</p><p><strong>Yeah that’s not gonna happen, like, ever…</strong></p><p>The thing is that the internet was meant to be like that. Enter the fediverse. The fediverse is a collection of social media apps that can communicate with each other. You can join mastodon or pleroma if you like short character-limited quips, or peertube if you prefer videos. Or pixelfed if you are a photo person. Prismo if you’re into news. Plume if you like longer writing forms. There are more, like misskey and anfora, and new apps are being developed right now too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C5AraSbj7_GT0cvmE9Cj_w.png" /><figcaption>A peek in Mastodon.</figcaption></figure><p><strong>So that’s all?</strong></p><p>Even when you do choose an app the journey doesn’t end there. There are many copies of that app on the web, called instances. Think about it as your local photography club. You can sign up to this one and if you don’t like the other photographers who hang out there, or if you have issues with the president of the board you can always pack up and go sign up on the one in the next town. All of them however communicate with each other. You don’t have to cut ties with that one friend you liked from the local place.</p><p><strong>And why is that better?</strong></p><p>This also distributes moderation so no big overseeing algorithm that sees <a href="https://mastodon.social/@qwazix/101187934629253321">nipples everywhere</a> will censor your posts. However, just like your local photography club has rules, and you probably can’t showcase anything you want in the annual photo exhibition the same goes for your friendly neighborhood instance. If you don’t like the rules, there are other instances.</p><p><strong>And how do I choose which instance? Eh, this is becoming hard work. I just want to be where all the cool kids are.</strong></p><p>Some instances are thematic. This makes it nicer to look at their general timeline and discover similar-minded folks if you’re really into one subject. Some are more generalist. Some others restrict their audience to a specific political affiliation or opinion. Yeah there are nazis on the fediverse. But most non-nazi instances have them blocked anyway so it’s unlikely to meet them if you don’t go looking for them.</p><p><strong>I didn’t get that name though fedi, what’s fedi?</strong></p><p>The thing that makes all these apps and services talk to each other is called <a href="https://activitypub.rocks/">ActivityPub</a> and it’s a form of federation. Another form of federation makes your e-mail from @gmail.com reach my email @qzx.gr and your boss’s @corporate-overlord.com despite being hosted by very different entities and on very different technology stacks. So the universe of federation is called the fediverse, or in short, fedi.</p><p><strong>Hmm,</strong></p><p>Oh, I forgot to tell you. All this looks like free but it is being supported by the people that run the instances. Be a good sport and give them a tip. There are usually no ads and these people will probably never ask you for money but this doesn’t make it less hard work or less costly for them to run the servers.</p><p><strong>And what’s </strong><a href="https://print3d.social/"><strong>print3d.social</strong></a><strong>?</strong></p><p>We just love 3D printing and we believe that prints can be works of art. We made a [pixelfed](https://pixelfed.org) instance so anybody who likes 3D printing can post his creations. It’s a great discovery mechanism too because the instance’s timeline will be full of awesome 3D prints. If you’re as into 3D printing as we are, sign up! And remember, if you have any friends on mastodon (or elsewhere on the fediverse) tell them to follow you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6kX7en-xmQRej3She_PjTg.png" /><figcaption>How print3d.social looks like.</figcaption></figure><p>By the way it’s pronounced “printed social” inspired by the popular 3D printing software <a href="http://slic3r.org/">slic3r</a>.</p><p><strong>But I want to post my cat.</strong></p><p>Then just 3D print a toy for it and post it playing with it. Ok, we won’t ban you for the odd cat-only pic but don’t overdo it. Also the server we run is very very small in order to keep the costs down so registrations will close at some point. <a href="https://print3d.social/">Hurry up</a> :-P</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4JAdKoN7VOalJ9a4HtXARg.jpeg" /><figcaption>Our latest print designed by <a href="https://www.thingiverse.com/UnpredictableLab/about">UnpredictableLab</a>. Download the files <a href="https://www.thingiverse.com/thing:3107770">here</a>.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b5145cb3ceb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/d-e-weblog/introducing-print3d-social-and-the-fediverse-6b5145cb3ceb">Introducing print3d.social and the fediverse</a> was originally published in <a href="https://medium.com/d-e-weblog">d-e weblog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tracing the path of Hotel Kastri]]></title>
            <link>https://medium.com/d-e-weblog/tracing-the-path-of-hotel-kastri-1a5f3b0dbb83?source=rss-75498c7cf7a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a5f3b0dbb83</guid>
            <category><![CDATA[historical]]></category>
            <category><![CDATA[structural-engineering]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[building]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Michael Demetriou]]></dc:creator>
            <pubDate>Fri, 29 Mar 2019 11:54:01 GMT</pubDate>
            <atom:updated>2019-03-29T11:54:01.288Z</atom:updated>
            <content:encoded><![CDATA[<h4>and we are proud to have been a part of it</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tjSDKrsSU2xNvEmHUUJ-AQ.jpeg" /></figure><p>After the peak of the financial crisis in Greece, the bank system consolidated significantly. This process saw the major banks absorbing (almost) all the smaller ones. In particular, <strong>Piraeus Bank</strong> absorbed 7 banks in the past 5 years. One of the biggest acquisitions was that of the <strong>Agricultural Bank of Greece</strong>, which, being a state bank for almost 80 years, came with significant real estate. This real estate portfolio includes many interesting buildings, such as the <a href="https://medium.com/d-e-weblog/serpieris-building-7ebc49e76f92"><strong>Serpieri Mansion</strong></a> in the center of Athens, the <strong>Archive Building</strong> in Tavros and the <strong>Zakynthos Branch</strong> we talked about in a <a href="https://medium.com/d-e-weblog/zakynthos-piraeus-bank-a95ff71920ef">previous article</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8IeAwaz8pzBI4N7Z3tUadQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tqVstCbVJ0n9UYjT8l7OpQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zeO3i7kYiLlCWLNjjC8Q3g.jpeg" /><figcaption>Serpieri Mansion — Tavros Archives — Zakynthos Branch</figcaption></figure><p>One of these properties is the <strong>Kastri Hotel</strong>, situated to the North of Athens at the homonymous suburb, along with the adjacent Education Center. The hotel was built some time in the 1920’s, around the time when Kastri (the suburb) along with <a href="http://www.mixanitouxronou.gr/i-ekali-choris-efoplistes-ke-idiotikes-froures-schediastike-to-1922-os-kipoupoli-ke-proevlepe-ena-xenodochio-se-lofo-to-vomvardisan-i-germani-ke-sto-idio-simio-chtistike-to-frourio-tou-latsi/">Ekali</a>, Psychiko and Filothei were designed according to the contemporary <a href="https://en.wikipedia.org/wiki/Garden_city_movement">Garden City Movement</a>. It is interesting to note that until today all four neighborhoods are still upscale parts of Athens. During the same period the Papandreou family bought the adjacent Mansion <em>Serenity</em>, which would later become central to the political life of the country. Rumor has it that the Hotel was owned by engineer Mavroleon, and passed to the Agricultural Bank at an unspecified period during the mid-20th century.</p><p>The history of Kastri Hotel and its cultural significance is highlighted by its multiple appearances in cinema. The earliest I could find is this dramatic noir shot from <a href="http://www.imdb.com/title/tt0184546/">Lost Dreams</a>, a 1961 film.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/712/1*2wJO95WnoMr4hUZULs-zcQ.jpeg" /></figure><p>It kept appearing in movies through the years, and I found references up to 1988 with a tv-movie named after the hotel, but a cursory glance through the movie suggests that it was not actually filmed on premises.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/478/1*qMwmL66gjnfaf5w3960ngA.jpeg" /><figcaption>The entrance in 1962</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/503/1*_NP3hDQgSs9IspxAXWCbQg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*t89zwfUNY2mHP5xvqrNcmw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*pwXzb3IWxL26772Jfc2mUQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zIt-QvFuiOOrfsH3eUklhA.jpeg" /><figcaption>The stairs in the lobby, in 1964, 2013, during the renovation and now, in 2019</figcaption></figure><p>During the late 80’s the Agricultural Bank expanded the complex with an education/conference center, certified for hosting seminars in the sectors of Finance, Marketing, Education, Agriculture and IT. The hotel was relegated to a hosting facility for the needs of the Education and Conference center.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n-ujQi6eqLsWjIlcVz_e2w.jpeg" /><figcaption>The excelixi education center and Kastri Hotel complex</figcaption></figure><p>In 2012, the Agricultural Bank was split into a good and bad bank and the good bank was acquired by Piraeus Bank. In 2013 the new administration created a new company to manage the education center and decided that the hotel deserved a new life as a contemporary luxury hotel in the outskirts of Athens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RJIa9PVFsYBUfyrxN2RsVA.jpeg" /><figcaption>The hotel before the renovation, who would believe what lies beneath the surface…</figcaption></figure><h4>Enter d-e</h4><p>Here is when we come into the picture.</p><p>The bank hired us to provide <strong>project management</strong> services, <strong>structural design</strong> and <strong>supervision</strong> for the complete renovation of the historic hotel. The hotel is comprised of two buildings, the main building and the guest houses.</p><p>We couldn’t find anything about the hotel in official archives. Thus everything had to be assessed by inspection. The new design included moving a load bearing masonry wall and the removal of several columns. The building had obviously gone through several renovations and expansions and several different building methods were used through the years.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JPx0MC4UKIyoqZ7J5c3fIw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qm_LVPTP1e4hjKYt3hdmqg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xXBocgqo2Jt1SdFwC_7aiQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AJqTU7IQlhW7NUQn02X88w.jpeg" /><figcaption>We found all kinds of building techniques behind the plaster.</figcaption></figure><p>Although the majority of the structure is comprised of load-bearing masonry walls, concrete beams were also discovered during assessment. Our assumption is that despite concrete being used since the <a href="https://en.wikipedia.org/wiki/Concrete">ancient times</a> it was still an exotic material in 1920’s Greece and was used only where absolutely needed. One such example is a ballroom which needed large unsupported spans. The concrete beams occasionally fuse with the masonry wall without supporting columns.</p><p>Bricks, masonry, concrete and steel all mix in every possible combination. Significant reinforcements were required in order to bring the ageing building to current standards.</p><p>The main building was depending on the outer masonry walls and a light inner concrete space frame. The load bearing capacity of the inner concrete structure was very low and thus deemed insignificant. It was replaced by new concrete space frame that supports the building in combination with the outer masonry wall, which was itself reinforced with new mortar and resin injections.</p><p>The slabs were either solid or ribbed concrete with ceramic bricks filling in the voids. Others were made of steel sections, lined with marble slabs and then filled with concrete. Some of them needed reinforcement with steel sections on the underside.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rztZampavbK-BkXdWgKe2A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*cEF2wlWDND5q3_Uq-ImRrg.jpeg" /><figcaption>Different slab types</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zKOFbmlYAuMtgV1jIQy8Kw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gjz-URKRYbSP2kAv0PBYVw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SokoYoAuQO56KGVojCCyPg.jpeg" /><figcaption>This particular beam was made of steel filled with concrete. It was completely removed and replaced with a reinforced concrete beam.</figcaption></figure><p>After the renovation, the hotel looks like this, and nobody can imagine what happened looking at the before and after photos.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nooYDkjxaRdv-J_2-w9AHA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lW6AqoXZ56kTAV0eIRbabw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BPl6Wl-srcJsDFlxeCL0RA.jpeg" /></figure><p>For more photos, follow the #hotelkastride on Twitter!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a5f3b0dbb83" width="1" height="1" alt=""><hr><p><a href="https://medium.com/d-e-weblog/tracing-the-path-of-hotel-kastri-1a5f3b0dbb83">Tracing the path of Hotel Kastri</a> was originally published in <a href="https://medium.com/d-e-weblog">d-e weblog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why “The fundamentalist FOSS mentality” entirely misses the point]]></title>
            <link>https://medium.com/@qwazix/why-the-fundamentalist-foss-mentality-entirely-misses-the-point-f53cbe56040a?source=rss-75498c7cf7a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/f53cbe56040a</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[free-software]]></category>
            <dc:creator><![CDATA[Michael Demetriou]]></dc:creator>
            <pubDate>Fri, 01 Feb 2019 09:01:51 GMT</pubDate>
            <atom:updated>2019-02-01T09:15:42.749Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m writing this in response to <a href="https://blog.hiri.com/the-fundamentalist-foss-mentality-c70a953f2821">David Power’s</a> article on free software fundamentalists. I think that the author entirely misses the point of why some of us choose Free Software.</p><p>I will start by arguing that I’m not a free software fundamentalist. I also have a mac. But <em>because</em> I like the shiny hardware. And that argument actually helps me to illustrate one of the practical reasons I choose Free Software: I don’t need a $99 piece of software to require me to buy $2999 hardware or tie me to a platform that one day I might not be able to install it on a decent desktop computer.</p><h4>Abandonware</h4><p>There’s also another practical issue. I have used a lot of proprietary software over the years. Guess what. My backup archive is filled with unreadable proprietary file types that I cannot open unless I find a computer with an optical drive and the original CD of that program (and this even if it still runs on modern versions of windows). So yes, a piece of proprietary software has a very high chance of becoming worthless in the long term.</p><h4>Working against your users.</h4><p>I will not try to pick apart the <a href="https://en.wikipedia.org/wiki/Security_through_obscurity">security by obscurity</a> argument, many have done this over the years. I will, however, argue that market forces can do nothing when software works against its users. Facebook is still king despite Cambridge Analytica. Smart appliances spy on us regularly and state so in the EULA. Only when software was revealed to do explicitly forbidden stuff then somebody was punished.</p><p>And it’s mighty hard to reveal what proprietary software does. Secret knowledge might help advance human knowledge but most other technology is reverse-engineerable quite easily. You don’t see new mechanical technology stay proprietary for long because it’s easy to pick an engine apart and see how it works. Disassembling software not only is hard, it’s illegal. So a super-efficient algorithm that is compiled in a proprietary binary cannot possibly help the advance of human civilization.</p><h4>Funding</h4><p>I admit I haven’t solved the funding issue but my little experience with developing free software was that even when I had it somewhere freely downloadable, people still paid me for the convenience of installing it via a package manager. This echoes the reality that proprietary software companies still make a lot of money even if software was really easy to pirate until recently.</p><h4>Extreme circumstances require extreme opinions</h4><p>I agree that Richard Stallman has extreme opinions. But I can argue that extreme opinions are a prerequisite for leaders of successful movements. Because if anybody saw Stallman using Windows he would have picked him apart. That’s the way it works and that’s the price activists have to pay.</p><h4>Running downloaded binaries on linux sucks</h4><p>The argument of advancing Free Software by embracing proprietary software seems ironic to me. We don’t want to grow the adoption of open platforms because we are Linux evangelists. It’s because we believe it is better software <strong>because it is Free Software. </strong>Using proprietary software to promote it doesn’t make even a tiny modicum of sense. However it also has a technical flaw: it doesn’t work like that. I have tried time and time again to use proprietary software on desktop linux and it is a painful experience. GNU/Linux depends on openness. Libraries change all the time, you can’t download binaries and expect them to work. And if they do, they might break any day. This is even true of <em>appImages</em> and<em> flatpaks</em> too in a bit smaller degree. And sticking to an old OS is less and less viable. I’m on Ubuntu 16.04 at work and I can’t even run the latest version of half the programs I use daily.</p><h4>Conclusion</h4><p>Some of us choose to run Free Software because of ideological reasons. But there are quite a few practical reasons to prefer it too. I can argue that choosing only the most convenient tool for the job at any point ignoring the ethical and practical repercussions (I choose Software X despite it costs me $2K and sends all my data to their servers) is proprietary software fundamentalism and an extreme position in itself.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f53cbe56040a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[is tech changing our life faster than ever?]]></title>
            <link>https://medium.com/@qwazix/is-tech-changing-our-life-faster-than-ever-582e5eae3936?source=rss-75498c7cf7a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/582e5eae3936</guid>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Michael Demetriou]]></dc:creator>
            <pubDate>Sat, 03 Mar 2018 19:10:04 GMT</pubDate>
            <atom:updated>2018-03-03T19:11:31.776Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KBH2VAYxDs0g6gWhDLgbZg.jpeg" /></figure><h4>Maybe not.</h4><p>Let’s imagine a man who fell in a coma in 1908 and woke up in 1928. That man, before falling unconscious would have probably never seen a car. He would have learned that two brothers managed to fly for a few feet but he would have probably never seen a plane either. His house and his city’s streets would have been lit at night by gas, if at all. If he was a cinemaphile he would have seen the first feature length film, but little more than that. Radio was still just used for communication with ships and the first audio broadcast was a two year old feat. The telephone existed, but the first switchboards had just been installed and if you lived somewhere without a network you had to buy two telephones and install the line between them yourself.<br> <br> And then he wakes up in 1928. The automobile market is almost saturated, and the Model T has sold 15 million units alone. Most middle class American families had a car. Plane travel was for the rich but the first transatlantic flight was already old news and airships flew wealthy passengers across the pond regularly. The sheer noise of all those machines would have been staggering. Then the night would come and the cities would not be dark anymore. A flip of a switch could light up your house in an instant. Neon lights adorned theaters, night clubs, town squares and other attractions and looked like something straight out of the future. In fact this 100 year old technology still looks like something from the future. Going to the movies was a regular night out for every American, and the movie industry has yet to surpass the proliferation of the 1920’s. Listening to radio programs was now a regular kind of entertainment and telephones connected almost everyone. (can’t find specific citation for this but it can be quite safely inferred)<br> <br> We usually think that a lot of things have changed during our lifetimes and it’s a general belief that due to exponential technology we have experienced the most staggering changes ever to be experienced in history. And that is almost universally true and the impact of the internet, the web and pocket computing cannot be understated, but in terms of how impressive the changes were, I think the early 20th century wins hands down.<br> <br> Of course our guy would be in for a nasty surprise a year later but that’s another story.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=582e5eae3936" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Η καλύτερη κρέπα στον κόσμο]]></title>
            <link>https://medium.com/@qwazix/%CE%B7-%CE%BA%CE%B1%CE%BB%CF%8D%CF%84%CE%B5%CF%81%CE%B7-%CE%BA%CF%81%CE%AD%CF%80%CE%B1-%CF%83%CF%84%CE%BF%CE%BD-%CE%BA%CF%8C%CF%83%CE%BC%CE%BF-851529bea754?source=rss-75498c7cf7a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/851529bea754</guid>
            <category><![CDATA[κρέπες]]></category>
            <category><![CDATA[fiction]]></category>
            <category><![CDATA[διήγημα]]></category>
            <dc:creator><![CDATA[Michael Demetriou]]></dc:creator>
            <pubDate>Fri, 23 Dec 2016 12:58:46 GMT</pubDate>
            <atom:updated>2018-03-04T09:57:03.647Z</atom:updated>
            <content:encoded><![CDATA[<p>Κάποτε έφτιαχνα κρέπες. Μόνος, σε μια καντίνα στο κέντρο της πόλης, εκεί που μαζεύονται οι καλλιτέχνες του δρόμου και οι μικροπωλητές και στήνουν τους πάγκους τους. Είχα την τύχη να σερβίρω έναν συντάκτη μιας τοπικής free press εφημερίδας.</p><p>“Η καλύτερη κρέπα στον κόσμο”, έγραψε την άλλη μέρα. Όπως φαντάζεσαι, η δουλειά μου εκτοξεύτηκε. Δεν ήθελα όμως η επιτυχία να αλλάξει αυτό που έκανα. Συνέχισα λοιπόν να φτιάχνω κρέπες, με τον ίδιο ρυθμό, με το ίδιο μεράκι. “Θα βαρεθούν να περιμένουν”, λέω, “θα φύγουν”. Δεν μπορούσα να φανταστώ ποτέ πόση θα ήταν η υπομονή των ανθρώπων.</p><p>Είχε πάει σχεδόν δύο το πρωί. Η ουρά άρχισε να σπάει. Μερικοί όντως έφυγαν. Τελευταίος ήταν ένας τύπος ντυμένος απλά, τζιν, σταμπαρισμένο T-shirt και μούσι τριών ημερών. Παράγγειλε την κρέπα του και περίμενε, περπατώντας πάνω κάτω. Είχε αρχίσει να κάνει κρύο.</p><p>Έφτασε στο παράθυρο και κοίταξε μέσα. Περιεργάστηκε την κρέπα, μύρισε το λιωμένο τυρί που τσιτσίριζε πάνω στην πλάκα, κοντοστάθηκε, αλλά τελικά είπε:</p><p>“Δηλαδή αυτή είναι η καλύτερη κρέπα στον κόσμο;”</p><p>Μ’αρέσει να το κάνω αυτό. Χαμήλωσα τη φωτιά, ακούμπησα τους αγκώνες στο παράθυρο της καντίνας και έσκυψα συνωμοτικά.</p><p>“Η καλύτερη κρέπα στον κόσμο είναι ένας μύθος. Ακόμα και αν συμφωνήσεις με όλους τους άλλους ανθρώπους για το τι έχει μέσα η τέλεια κρέπα, ακόμα και αν ταξιδέψεις σε όλο τον κόσμο, ακόμα και αν δοκιμάσεις από όλες τις κρεπερί ό,τι έχει ο κάθε κατάλογος, μπορεί να μην τη βρεις. Γιατί μπορεί αυτός που τη φτιάχνει να καυγάδισε το πρωί με τη γυναίκα του. Ή γιατί μπορεί να είναι ήδη στο στομάχι κάποιου. Ίσως και να ήταν αυτή που έφτιαξα χτες σε εκείνο τον κοντό, κατσούφη Κορεάτη που ήρθε στο παράθυρο βιαστικά και παρήγγειλε μια κρέπα με αντζούγιες, μανιτάρια και μεξικάνικα φασόλια· και που καθώς την έψηνα, μου έδωσε εκείνο το λευκο σακουλάκι με τα κόκκινα γράμματα και την πρασινοκίτρινη σκόνη για να τη βάλω στην κρέπα.”<br>Σώπασα λίγο για έμφαση.<br>“Αν κρίνω από το χαμόγελο που ήρθε να αντικαταστήσει την κατήφεια στο πρόσωπό του μόλις γεύτηκε την πρώτη δαγκωνιά, και πώς έφυγε χοροπηδώντας ανάμεσα στα φώτα των πάγκων, μπορεί αυτή να ήταν η καλύτερη κρέπα στον κόσμο”<br>Δυνάμωσα και πάλι τη φωτιά, και γύρισα την κρέπα να πάρει χρώμα κι απ’την άλλη. <br>Αυτός έκατσε σκεφτικός. Του έβαλα ένα σφηνάκι ουίσκι να ζεσταθεί. Σε λίγα λεπτά η κρέπα θα ήταν έτοιμη. Το λιωμένο τυρί είχε ήδη γίνει μια χρυσή, λαχταριστή κρούστα, κόκκινες και πράσινες πιπεριές συμπλήρωναν τα χρώματα και το μπέικον εμφανιζόταν σε μερικά σημεία λες και η μυρωδιά δεν ήταν αρκετή για να βεβαιώσει την υπαρξή του.<br>“Αυτή λοιπόν μάλλον δεν είναι η καλύτερη κρέπα στον κόσμο” είπα καθώς τον σέρβιρα. “Αλλά όπως βλέπεις, είναι μια γαμάτη κρέπα”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=851529bea754" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Doing SCRUM in a Project Management and Structural Engineering context]]></title>
            <link>https://medium.com/d-e-weblog/doing-scrum-in-a-project-management-and-structural-engineering-context-915308ef75b8?source=rss-75498c7cf7a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/915308ef75b8</guid>
            <category><![CDATA[structural-engineering]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Michael Demetriou]]></dc:creator>
            <pubDate>Wed, 04 May 2016 19:18:16 GMT</pubDate>
            <atom:updated>2016-05-04T19:18:16.596Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XwkewXAiXb6p82TzvuyOtQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H3fjrx8bQFKefHArj42xlQ.jpeg" /><figcaption>Programming language poster by O’REILLY (<a href="http://archive.oreilly.com/pub/a/oreilly//news/languageposter_0504.html">http://archive.oreilly.com/pub/a/oreilly//news/languageposter_0504.html</a>)</figcaption></figure><p>Software development goes forward with breakneck speed. New frameworks show up every day, new languages pop up every few years, the commonly accepted good practices change by the month.</p><p>Eventually the tools and processes that support the development of the software had to keep up to the frantic pace and have also evolved disproportionately fast, compared to the same tools and processes in other industries.</p><p>However, while the newest javaScript framework, or extensive use of lambda expressions and singletons are of no use to anybody but a programmer, the tools and processes are. Due to my stint in the world of software it struck me that importing the best tools and processes of a highly advanced and productive industry, to a slower-moving one (that of engineering and construction project consulting) could provide huge benefits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3PJIp85yl4_WS5SztaBZdg.png" /></figure><p>Version control first came to mind. As every seasoned coder will attest to, living without versioning seems today like writing cover letters on a typewriter. However, current versioning tools are too focused on code, making them hostile for other kind of intellectual work. I have a solid idea how this can be rectified, but this is a subject for another story.</p><h3>People and time management</h3><p>Managing teams and their work is the next obvious change. While most of the service companies still work with a traditional waterfall organization chart, most software development has long moved out and into agile development practices.</p><p>Agile, however, isn’t about software. It’s about intellectual work, productivity and worker satisfaction and addresses most of the issues where services are different than manufacturing, from where the traditional waterfall structure originates.</p><p>After studying various agile methodologies I decided to go with <strong>SCRUM</strong>, since that was the one that had more defined goals and was the easiest to do, without having to request outside help. Of course software development has its differences to engineering and even more to project management. We do both, here at <strong>d-e</strong>, so we had to adapt the system to our requirements.</p><h4>Differences</h4><p>Not all software development has been created equal, but it is clear that SCRUM is geared toward product development. Product development doesn’t have clients calling in the dev team asking for features. Furthermore, the possibility to have to wait for external (to the company) parties to finish some task, before you are able to continue, is almost nonexistent.</p><p>In consulting however, be it software or structural or I presume many other domains, it’s quite usual. This puts a wrench in the works of trying to accurately predict task duration. There is also the fact that the team is not always working on a single project that everyone knows about, so there’s (even) more friction when somebody needs to take on work on something he has no idea about.</p><h3>Where SCRUM works fine</h3><h4>Minimum Shippable Product</h4><p>Before getting into the adaptations to SCRUM we ended up implementing, let’s defend the core SCRUM principles here and show why (sometimes counter-intuitively) they work very well in a consultancy environment.</p><p>From now on I am assuming you are familiar with SCRUM. If you are not, go watch <a href="http://scrumtrainingseries.com/Intro_to_Scrum/index.html">this</a> or just <a href="https://www.google.gr/search?client=ubuntu&amp;channel=fs&amp;q=introduction+to+scrum&amp;ie=utf-8&amp;oe=utf-8&amp;gfe_rd=cr&amp;ei=8C35VurhOoeFaLOMo6gO">google it</a>. I’ll be waiting.</p><p>Back? Good. Now that you know the basics of SCRUM let’s see where it’s good as it is.</p><p>The concept of a Minimum Shippable Product is even more important in our case than it is in software. Breaking everything into small, gift-wrapped pieces of work that can be shipped out, functions beneficially for a couple of reasons:</p><p><strong>Shipping takes a lot of time: </strong>Shipping the work usually involves finalizing report layouts, combining documents, embedding drawings, fixing paging, creating covers, printing onto different media and on different orientations, binding and actually shipping. This time is very rarely correctly forecast and everybody often ends up frantically trying to do all these at the last minute. And because <a href="http://theoatmeal.com/comics/printers">printers came from hell</a>, there’s something bound to go wrong.</p><p><strong>If you are late, the damage is smaller:</strong> Say you have to clean a five-story building. You split the task to vacuuming, mopping, dusting and window-cleaning. It seems logical to do each task once for the whole building and then move to the next, so that you don’t have to put your tools back, and because of, you know, overspecialization. You forecast a day for each task, so you promise the building done by Friday. Due to unforeseen circumstances, or just because you predicted wrong, Friday morning comes and the building is still a mess. Half the desks have a thick layer of dust and the windows are so dirty you can barely look outside. You have no option but to call in, declare defeat and beg for two days more.</p><p>On the other hand, if you split your building into Minimum Shippable Products (i.e. each floor) and you do the “counterproductive” process of completing the 4 tasks consecutively for each floor, even if you are hopelessly late, you can call and say “<em>Hey, I’ve finished floors one and two, you can come start moving in, and by the time you’re finished with floor 2, I’ll have another two floors ready, ok?</em>”. That’s a much more manageable defeat.</p><p><strong>“Emergencies” are easier to handle:</strong> There’s always that guy, who calls and asks for a truckload of work and needs it yesterday. More often than not there’s no actual emergency but people tend to exaggerate, or underestimate their own part of the work. However it’s always a tough thing to have to say “NO” to the client, and having a pack of PSB’s ready to ship yesterday never harmed anyone. So the answer transforms from “<em>This is ridiculous!</em>” to “<em>Let me see what I can do, maybe I can have floors one and two ready by the end of the week so you can start working</em>”. This way you look good, help avert the crisis or if there’s no crisis, call his bluff.</p><p><strong>Missing work or unreliable external partners are identified earlier: </strong>When you have to put a wrap and bow on your work once every two weeks, you can identify parts of work that might have been overlooked, and helps put pressure on external partners who would otherwise send you everything the very last minute, disregarding the enormous shipping work needed and pushing you into overtime again despite all your efforts to be punctual this time.</p><h4>No team labels</h4><p>One of the most controversial provisions on SCRUM is that team members do not have assigned tasks at the start of the sprint. Let me clear up how that works and why it is one of the most useful provisions, even on an engineering/project management work-flow.</p><p>First of all the fact that there are no tasks pre-assigned, doesn’t mean that every team member won’t take the most suitable task from the list of to-do’s. But let’s take it from the beginning with a case study:</p><p><strong>Alice</strong> has extensive experience with Geotechnical Engineering. She has been in charge of all the projects of Delta Corp. over the years so she knows all the executives there.</p><p><strong>Bob</strong> is a seasoned Project Manager. He has hundreds of projects under his belt and knows the tools of the job (Gantt charts, spreadsheets, software etc.)</p><p><strong>Charlie</strong> &amp; <strong>Dave</strong> are both Structural Engineers, their competences are on different pieces of software but have mostly been doing calculations, without much experience outside the office.</p><p>At this point in time Engineering Consulting LTD has a new project from DeltaCorp that involves the design and supervision of their new ten story HQ building, which features 5 basements of parking garage. There is also some limited project management work involved. The contractor has already been selected so no tender documents or price bidding will be organized, but a time schedule and BOQ will be prepared.</p><p>There are three ongoing residential buildings structural analyses that do not involve supervision or otherwise contact with the client or contractor. The deadline for the first one falls inside the next sprint and the others do not yet have a defined deadline.</p><p>There are also some projects that have essentially been completed but issues still come up which involve visits on-site, meetings, e-mails and telephone calls.</p><p>This is a typical board that describes the situation</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FuJfOlGLt7DI9W1h8fIlzw.png" /><figcaption>This is a typical mid-sprint trello board</figcaption></figure><p>During the <strong>daily scrum</strong>, at the beginning of the sprint it is obvious that the DeltaCorp project is going to be done by Alice. She starts by taking some cards, assigning them to herself and putting them in the Doing column. Usually we put our avatars on the cards but this would require me to create fake accounts for the fake board above, so they are missing here.</p><p>As days go by and everyone chomps off of the things he is good at, or knows the subject well, it is possible that we arrive at a situation where no “suitable” cards are left for everyone.</p><p>Let’s say Bob is now out of cards that suit him and the only available cards are DeltaCorp ones. When this comes up it’s certain that Bob will go like this:</p><blockquote>It’ll take me two days to even get a clue about what’s happening in DeltaCorp HQ project. And I don’t know anyone in there, all communication will have to go through Alice, slowing her down, not to mention she’ll need to introduce me to the project. And she already has so much to do. And there’s another backlog Item that fits me perfectly, why not get that into the current sprint out of band?</blockquote><p>And Alice will likely respond as follows, because she sees only as far as the end of the sprint</p><blockquote>It’s true, I can handle it. And you know, they didn’t ask us for the parking feasibility study until the end of the month, so I can skip the shipping part and do it next week. I shouldn’t train Bob now on the project because I’ll stay behind.</blockquote><p>That is a very nice way to make sure SCRUM fails during it’s very first sprint. But I’m not going to elaborate as to what happens if things go Bob and Alice’s way because you already know: the same thing that’s been happening anyway. If you are reading this you probably want to read why doing SCRUM is better.</p><h4>Why should you stick to the plan?</h4><p>Because when this scenario happens, one of three things is true</p><ul><li>It’s the last day or two of the sprint. In this case Bob and Alice might actually be right, but I still believe the small hit in efficiency is worth it because the team will become more adaptable. Not only switching projects is actually not that painful, but the more you do it the easier it becomes. The whole team is familiar with all the projects making it easier to cover for someone if he is unavailable or lend a hand in an emergency.</li><li>The DeltaCorp project is huge. It’s gonna need more than one person anyway, and the earlier the two-day on-boarding is done, the less costly it is. It is easy to underestimate the work needed when the deadline is a few months ahead and believe that one man can pull it off. When you are only left with to-do’s of one project mid-sprint, it’s a good indicator that more people need to familiarize themselves with it and now is the best time to do it, as nobody has any other deadline (no other cards).</li><li>There’s a deadline at the end of the sprint, or earlier. If the project is not huge, but the product owner put it high up in the backlog, it might actually need to finish soon. It’s better for everyone to share the burden than leave one guy to do overtime. This is also a (shorter term) indicator, that there is going to be pressure.</li></ul><p>In sum, it probably means something about your workload, and not that SCRUM is broken.</p><h4>Two week sprints</h4><p>Someone working in consulting will certainly tell you that you can’t possibly split the work into sprints as the deadlines are rarely up to you. Our experience has shown that actually you can predict pretty well when every task will come up. If you think it’s going to come up, it will. Very rarely will completely new, unprecedented things come up that can’t wait until the start of the next sprint. If that rare possibility does actually happen, we do a longer morning SCRUM where we break down the new job, add it to the running sprint and remove anything that now doesn’t fit anymore.</p><h4>Using Trello</h4><p><a href="http://trello.com/">Trello</a> is a good tool for this job. It’s connected, it has an app, it’s fast and allows easy manipulation of tasks, sub-tasks etc. We have everything scrum related on a single board, as you can see a few paragraphs above. When tasks are moved to the <em>Doing</em> list, the person that is being assigned the task adds his avatar to the card. The avatar stays there until somebody else takes the task or the task is finished, even if the task moves back to the to do list for any reason.</p><h4>Breaking up tasks</h4><p>When breaking up the tasks in the planning meeting, we need a way to estimate whether we can manage the planned backlog items into the current sprint. We decided to add a time estimate to each task, and when the total reaches 70% of the available man-hours we stop. The remaining 30% is allocated to unexpected tasks, unplanned meetings, lost time etc.</p><p>For this reason we needed an easy way to add up times, so I developed a greasemonkey script that adds up the times, if noted as (XXh) somewhere in the card title. You can get it on our <a href="https://gitlab.com/d-e/trello-hour-sum-userscript">gitlab</a> page.</p><h3>Changes</h3><p>Up to now we talked about why SCRUM works for an engineering consultancy. However there are some differences that call for some modifications:</p><h4>Scrum Master cannot do all the communication</h4><p>Engineers have to talk to clients all the time. Especially in project management, phone calls are part of the job description. Not only routing everything through the SCRUM master is counterproductive, it’s downright impossible. Outsiders call all the time asking highly detailed questions about the designs, or meetings and calls have to be made to coordinate works.</p><p>Thus the SCRUM master can’t be a full-time job, at least for smaller teams. A software engineer that at the same time does IT duties, writes helpful scripts for day to day operations and other computer-y things, is a perfect fit for a SCRUM master. Especially if he has worked in a software company that did scrum earlier.</p><h4>Demos aren’t really possible</h4><p>During a sprint, an engineering office may manage complex constructions, produce tens of drawings, hold meetings, do phone calls and write reports. None of these are really demo-able. It’s possible to showcase some of the work (for example analysis results or decisions about building processes), but presenting drawings or reading reports aloud are considerably more boring than showing software features on a projector and definitely more time-consuming.</p><p>A small feature that can be demonstrated in five minutes can very well occupy the development team half a sprint, while a similar engineering team might need an hour to just display the same time’s production.</p><p>However, we replaced demos with a brief description of the things done during the sprint, so that the whole team gets up to speed with every task in the office.</p><h4>Waiting…</h4><p>A lot of tasks require outside input in order to be completed. They aren’t regular impediments in the sense that the team can’t do anything but wait. We used to keep these tasks in the <strong>To Do</strong> list. This however, not only is demoralizing, it makes the <strong>daily scrum</strong> harder, as we have to rummage through suspended tasks every day and repeat the fact that they are suspended. Thus we created a new list, called <em>waiting</em>, where all these tasks are stashed until something changes.</p><h4>Pizza</h4><p>And because we want to have some fun too, we always get together and order some food (or go out if the weather’s nice) before the <strong>sprint planning</strong> meeting.</p><h4>Digital pinboard</h4><p>We also got a TV and a <a href="https://www.raspberrypi.org/">Raspberry Pi</a> so that everybody can glance and see the tasks at hand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t5c__odmetpz59-PBy97CA.jpeg" /></figure><h3>Challenges</h3><p>One thing that has proven hard, is to remember that things (cards) in the first two columns are of a different class than cards in the last four. People go and move things from the <strong>backlog</strong> or the <strong>current sprint</strong> to the <strong>to-do</strong> or <strong>done</strong> lists causing hell. I don’t really know how this could be solved, but one attempt was to change the color of the first two columns via the time-adding script posted above. These two, could also have their separate board, but this would make the bi-weekly meeting much harder, because we would have to change back and forth boards all the time and would also stifle the spontaneous addition of backlog items when one thinks about them.</p><p>The other thing that requires attention is to keep the <strong>daily scrum</strong> time-boxed. While it’s not always bad to go a bit deeper into a task as not everybody is familiar with everybody else’s work in this context, it’s easy to get out of hand and waste everybody’s time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=915308ef75b8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/d-e-weblog/doing-scrum-in-a-project-management-and-structural-engineering-context-915308ef75b8">Doing SCRUM in a Project Management and Structural Engineering context</a> was originally published in <a href="https://medium.com/d-e-weblog">d-e weblog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hello, world!]]></title>
            <link>https://medium.com/d-e-weblog/hello-world-f59dab1993a5?source=rss-75498c7cf7a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/f59dab1993a5</guid>
            <category><![CDATA[hello-world]]></category>
            <dc:creator><![CDATA[Michael Demetriou]]></dc:creator>
            <pubDate>Mon, 22 Feb 2016 14:08:08 GMT</pubDate>
            <atom:updated>2016-02-22T14:08:08.891Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s8TKYqfJNqFBKIxC78g5aA.jpeg" /></figure><p>We are an engineering firm. We want to share some of our experiences, projects, thoughts and daily work lives with the world.</p><p>Thus, this is our new weblog.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f59dab1993a5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/d-e-weblog/hello-world-f59dab1993a5">Hello, world!</a> was originally published in <a href="https://medium.com/d-e-weblog">d-e weblog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>