<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Yet another SWE's quiet place for ranting</title><link>https://elgris.github.io/</link><description>Recent content on Yet another SWE's quiet place for ranting</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 25 Dec 2024 16:32:09 +0100</lastBuildDate><atom:link href="https://elgris.github.io/index.xml" rel="self" type="application/rss+xml"/><item><title>Exploring opensource projects by building (Ollama)</title><link>https://elgris.github.io/posts/2024/12/exploring-opensource-projects-by-building-ollama/</link><pubDate>Wed, 25 Dec 2024 16:32:09 +0100</pubDate><guid>https://elgris.github.io/posts/2024/12/exploring-opensource-projects-by-building-ollama/</guid><description>&lt;p>I haven&amp;rsquo;t touched opensource code for quite a while, and that made me sad. There is lots of biz, but not much fun in the corpo world. One evening I got me a beer and decided to get some fun! And since LLMs are on hype, why not try running a local one? That&amp;rsquo;s how I came first to &lt;a href="https://github.com/ggerganov/llama.cpp">llama.cpp&lt;/a>, then to &lt;a href="https://github.com/ollama/ollama">Ollama&lt;/a>. And I asked myself: &amp;ldquo;What is the best way to start exploring Ollama&amp;rsquo;s internals?&amp;rdquo; The answer is: try building it yourself. So here we go!&lt;/p></description></item><item><title>Happy Birthday Docker!</title><link>https://elgris.github.io/posts/2016/03/happy-birthday-docker/</link><pubDate>Thu, 24 Mar 2016 00:00:00 +0000</pubDate><guid>https://elgris.github.io/posts/2016/03/happy-birthday-docker/</guid><description>&lt;p>Look at him! 3 years old baby which is growing and growing and growing!&lt;/p>
&lt;p>Celebrating birthdays of such tools is a good idea in general. Why? Because attendees of such events are usually students or people not familiar (much) with technology. I have participated at Docker Birthday #3 at RMIT (Ho Chi Minh City, Vietnam) as mentor and what I&amp;rsquo;d say: local students need MOAR Docker.&lt;/p>
&lt;p>&lt;img src="https://elgris.github.io/img/5_docker_birthday/docker_birthday.jpg" alt=" Docker Birthday! !">&lt;/p></description></item><item><title>FOSSAsia conference, Singapore</title><link>https://elgris.github.io/posts/2016/03/fossasia-conference-singapore/</link><pubDate>Tue, 22 Mar 2016 00:00:00 +0000</pubDate><guid>https://elgris.github.io/posts/2016/03/fossasia-conference-singapore/</guid><description>&lt;p>Finally got somewhere big and IT. Welcome to FOSS Asia IT conference that took place at Singapore at 18-20th of March.&lt;/p>
&lt;p>What did I see there? Well, a lot of people willing to learn. Some of the talks were really mindblowing, but majority of them were average. It doesn&amp;rsquo;t mean they were bad, they were not hardcore, meaning no crazy hacks or benchmarks or extremely low-level code surgery. But they were educating and very useful for students and those who wants to take a look at some other technology, tool or idea. Sometimes there were kinda weird but funny topics :D.&lt;/p></description></item><item><title>Appium VS Calabash</title><link>https://elgris.github.io/posts/2016/03/appium-vs-calabash/</link><pubDate>Sat, 12 Mar 2016 00:00:00 +0000</pubDate><guid>https://elgris.github.io/posts/2016/03/appium-vs-calabash/</guid><description>&lt;p>OK, what do we have here? A mobile application written with Cordova for 2 platforms: iOS and Android. I&amp;rsquo;m lazy, I don&amp;rsquo;t want to check that all critical functionality works as expected after each release. In 2 platforms. And I don&amp;rsquo;t want anyone to do that, because manual work is stupid in IT. So I need a proper tool to test both applications automatically, so I have enought free time to explore the world around me :)&lt;/p></description></item><item><title>Coworking space in Nha Trang, Vietnam</title><link>https://elgris.github.io/posts/2016/03/coworking-space-in-nha-trang-vietnam/</link><pubDate>Sat, 12 Mar 2016 00:00:00 +0000</pubDate><guid>https://elgris.github.io/posts/2016/03/coworking-space-in-nha-trang-vietnam/</guid><description>&lt;p>Found a nice coworking space in Nha Trang, Vietnam: &lt;a href="http://livincollective.tumblr.com/">LivinCollective&lt;/a>. Check &lt;a href="https://www.google.com/maps/place/LIVINcollective/@12.24055,109.191345,15z/data=!4m2!3m1!1s0x0:0x9e9b8620219644fb?sa=X&amp;amp;ved=0ahUKEwjP8PHApbvLAhVTGo4KHf4_CxcQ_BIIcTAK">the map&lt;/a>. The place is comfortable, the hosts are really friendly. Working there is free, but it would be great if you buy something (juice or coffee or something to eat) to help run the place. WiFi there was the fastest I had in Nha Trang :)&lt;/p>
&lt;p>Some pictures of the place:&lt;/p>
&lt;p>&lt;img src="https://elgris.github.io/img/3_coworking_nha_trang/IMG_0131.jpg" alt=" coworking space !">
&lt;img src="https://elgris.github.io/img/3_coworking_nha_trang/IMG_0132.jpg" alt=" again, coworking space !">
&lt;img src="https://elgris.github.io/img/3_coworking_nha_trang/IMG_0134.jpg" alt=" view from the second floor !">
&lt;img src="https://elgris.github.io/img/3_coworking_nha_trang/IMG_0135.jpg" alt=" and don&amp;rsquo;t forget to buy something to drink :) !">&lt;/p></description></item><item><title>Apitest - test and document that</title><link>https://elgris.github.io/posts/2016/02/apitest-test-and-document-that/</link><pubDate>Sun, 21 Feb 2016 00:00:00 +0000</pubDate><guid>https://elgris.github.io/posts/2016/02/apitest-test-and-document-that/</guid><description>&lt;p>Everybody knows that using an API with no documentation is like walking on a minefield with no map.&lt;/p>
&lt;p>&lt;img src="https://elgris.github.io/img/apitest/1.jpg" alt="danger!">&lt;/p>
&lt;p>In &lt;a href="http://seesawlabs.com">SeeSaw Labs&lt;/a> we build APIs and we&amp;rsquo;re doing our best to provide our customers with such a map :)&lt;/p>
&lt;p>But how to write a documentation? Here are 3 general approaches.&lt;/p>
&lt;h2 class="heading" id="1-do-it-manually">
 1. Do it manually&lt;span class="heading__anchor"> &lt;a href="#1-do-it-manually">#&lt;/a>&lt;/span>
&lt;/h2>&lt;p>Sounds obvious, right? You write the code, you write documentation for it separately. Sounds easy. Now add several dozens of API endpoints and a dozen of developers into this cocktail. Shake it. Boom - you got Molotov Cocktail! :)&lt;/p></description></item></channel></rss>