<?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[bloomsolutions - Medium]]></title>
        <description><![CDATA[Bloom Technologies’ Blog - Medium]]></description>
        <link>https://medium.com/bloomsolutions?source=rss----a9eab4e58d48---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>bloomsolutions - Medium</title>
            <link>https://medium.com/bloomsolutions?source=rss----a9eab4e58d48---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 01:38:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/bloomsolutions" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Talking about Cryptocurrencies and Remittances in UPLB]]></title>
            <link>https://medium.com/bloomsolutions/talking-about-cryptocurrencies-and-remittances-in-uplb-7a70183f9a55?source=rss----a9eab4e58d48---4</link>
            <guid isPermaLink="false">https://medium.com/p/7a70183f9a55</guid>
            <category><![CDATA[public-speaking]]></category>
            <dc:creator><![CDATA[Ace Subido]]></dc:creator>
            <pubDate>Mon, 02 Apr 2018 00:57:37 GMT</pubDate>
            <atom:updated>2018-04-02T07:10:05.183Z</atom:updated>
            <content:encoded><![CDATA[<h4>Bloom at VISIV’s “DoDecrypt”</h4><p>An organization in the “University of the Philippines (Los Banos)” named VISIV reached out to Bloom to get us to sponsor an event called DoDecrypt that would happen on March 26, 2018. It was a blockchain forum and symposium. We participated as a sponsor and was given a speaking slot.</p><p>The entire team encouraged me to go and take this slot. I gave a yes without knowing what to talk about, and how to go on preparing for this in the midst of Q1 2018 ending. To be honest, I was nervous. Despite the nerves getting onto me, I knew that this was something I wanted to work on, so I took this chance. As Michael Jordan said: You miss 100% of the shots you don’t take.</p><p>I want to mark this year as the year I start improving my communication skills and help get the Bloom brand out there in the process.</p><h4>What to talk about</h4><p>The first thing that came into my mind was: what blockchain topic should I talk about? I figured I wanted to talk about what I learned from being with Bloom for the past year: cryptocurrencies and remittances.</p><p>Whenever we interview engineers I always end up explaining the remittance workflow when I see that they’re getting lost in the codebase. That explanation also gets carried over to dinner conversations whenever I have to explain why Bloom does what it does. A big part of why I also wanted to talk about this is because it’s something I learned after joining Bloom. It blew my mind how straightforward (and unnervingly brittle) every bank in the world handles the global flow of money.</p><h4>Preparing the materials</h4><p>To summarize, here are the steps I took:</p><ol><li><strong>Who are my audience? ‘</strong>Students’ were the audience, and they want to learn more about blockchain and cryptocurrencies. The topic I had in mind was about the use cryptocurrencies for remittances (as a settlement mechanism), so I need to make remittances as simple as I can.</li><li><strong>What type of talk should I give?</strong> There are 3 types: <em>Informative talks, Persuasive talks, Entertainment talk.</em> <em>Informative talks</em> are usually filled with data, concepts and diagrams, the goal is to explain an abstract concept and uncover what you’ve learned. <em>Persuasive talks </em>are used to get your audience to answer a call-to-action, it’s aim is to influence and change opinions. The tone is softer and subjective compared to an Informative talk. <em>Entertainment talks</em> are used for special events, the content is commemorative and leaning towards honoring the person/organization of interest.</li><li><strong>Drafting.</strong> This is probably the lengthiest part of the process. I started writing a number of paragraphs in an informal tone to cover the abstract topic, similar to how people talk about things over coffee. I hand-drew diagrams. Let’s just call this document, “cliff notes”.</li><li><strong>Making the slides.</strong> Chopped the “cliff notes” into slides and pasted them into the speaker notes section. I refused to add too much text in the slides because 1.) it’ll make me tempted to just read things off the slide, 2.) and they’re here to listen to someone talking, not someone reading a slide. Took the branding colors that we use and built the slides. Special thanks to Flaticons for the icons and Unsplash for the photos.</li><li><strong>Feedback.</strong> I gave the talk to my wife and parents while timing myself. I’m only given 20-minutes, and my audience are students, short and sweet was the goal. This part of the process was extremely helpful. I figured out if there were parts that I droned through too much prose just to power through the concept. I ended up culling out 30% of my slides, based on feedback, it was too heavy for a 20-minute topic.</li></ol><h4>How it all went</h4><p>My wife and kid came along. Elain wanted a road trip and was excited to support me on this. Surprisingly, my parents dropped by too!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1BbcphjYlxZ2lTGVraJ75w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e8ZFyMnDXN5IVyBiqmiqfA.jpeg" /><figcaption>Recently discovered toddler hack: Bring a pillow, some toys, books and snack books. Never did we pull out our phones to entertain him, Navi liked the road trip because of the pillow. Elain liked the pillow because when Navi sleeps she puts him down and she can relax with her hands free. AJ, a fellow engineer at Bloom, accompanied me for support.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a1UptOOOEYyIpGf0JrPvPQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RkJDkm4REJ8ITZAZiocwvQ.jpeg" /><figcaption>Arrived at UPLB after 1 1/2 hours of driving. Stopped by a coffee shop inside the campus called Ginhawa Craft Studio.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b1Kn3nAeIi28k310Lo5gog.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2PvuNsZWzff2337g-3S05w.jpeg" /><figcaption>Last minute preparation in the speakers table before going up the stage. Instead of bringing my laptop for notes, I placed my cliff notes on my phone and had more freedom to walk around the stage.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ngLSJULsquIO6e9AEhlP7A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r3zntehtRvZx66H57rjr-w.jpeg" /><figcaption>Closing the event, we got a certificate of recognition, a cake, and of course the attention and interest of students. <a href="https://medium.com/u/8f44bbd6e238">{cryptonight}</a> gave me his stack of Cryptop cards to give to the students, and it was a big hit!</figcaption></figure><h4>Lessons Learned</h4><ol><li><strong>If you learn about something that blows your mind, share it with others.</strong> To the general populace, “Correspondent Banking System” is probably the most boring string of words you could put together, but it just blew my mind how this system held together the global flow of money. It gave me a clearer picture of why things are the way they are just because I regular skim the surface of the underlying infrastructure.</li><li><strong>Don’t be afraid to ask for feedback.</strong> Generally speaking, unless it’s something really top-secret, the more you hide what you’re working on, the lesser you’ll learn and make it better.</li><li><strong>Progress is better than perfect.</strong> My initial slides sucked, it took me an entire day to make a 20 minute talk, I took 23 minutes instead of finishing in 20 minutes, I made a lot of ‘uhms’ and ‘ahs’, stuttering and getting lost in thought. The perfectionist in me would’ve liked to spend a week to make amazing slides and rehearsed this over and over; and I wouldn’t have been able to actually go and speak about a topic. Everyone starts somewhere and I’ve got a long way to go. As long as I keep putting myself out there, I’ll master the process of writing about a complicated topic and giving a clear talk about it. This can help me in so many ways, from programming to business development.</li><li><strong>Be human. </strong>When it was time to introduce myself, it was so tempting to read a company profile, some product description and get on with the topic. I’ll probably flash some diagram with a bunch of text under some icons and move forward. It’s easy and comfortable, but it sounds too robotic.</li></ol><p>There are many other lessons learned, and I’ll learn more as I keep on doing this. On the other side, I do hope the attendees got to learn something new about cryptocurrencies and remittances.</p><p>Thanks to UPLB and VISIV for inviting Bloom to participate in your event!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a70183f9a55" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bloomsolutions/talking-about-cryptocurrencies-and-remittances-in-uplb-7a70183f9a55">Talking about Cryptocurrencies and Remittances in UPLB</a> was originally published in <a href="https://medium.com/bloomsolutions">bloomsolutions</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Easy Team Management of Kubernetes Config]]></title>
            <link>https://medium.com/bloomsolutions/easy-team-management-of-kubernetes-config-44d209122843?source=rss----a9eab4e58d48---4</link>
            <guid isPermaLink="false">https://medium.com/p/44d209122843</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Ramon Tayag]]></dc:creator>
            <pubDate>Mon, 11 Dec 2017 07:50:30 GMT</pubDate>
            <atom:updated>2017-12-12T01:18:40.851Z</atom:updated>
            <content:encoded><![CDATA[<p>Being a two and a half person engineering team, we did not take the move to Kubernetes lightly. We did not want yet another system to manage, especially with such a small team as ours.</p><p>Our hands were tied behind our back, however: some of the software we need to run are difficult or impossible to run on Heroku, the platform we have used since our inception. There’s the consolation of having a cheaper infrastructure bill too.</p><p>We understood that the move would make our work a little more complicated. It was not until a few weeks after did we realize what those issues would be — <strong>management of cluster config by a team</strong> of developers.</p><p>After the system was setup on Google Cloud and I began teaching others how to deploy, we started to see application integrations “spontaneously” break. We soon found that we were overwriting one another’s configuration — especially secrets.</p><p>What does a programmer do when there’s a task they have to do often, not fun, and error prone? We automate!</p><p>The most painful problems for us were the following:</p><ol><li>Changing secrets</li><li>Restarting deployments</li><li>Deploying a new image</li></ol><h4>Changing Secrets</h4><p>Managing secrets was by far the most painful. We would have a local copy of the uncommitted secret template that we would have to copy from the Kubernetes cluster. If one of us either a) fails to update our copy and overwrites the copy on Kubernetes or b) encode it wrong (with that awful \n at the end), say hello to a new bug ticket.</p><pre>kcu secret list production/worker<br>kcu secret get production/worker sidekiq_concurrency<br>kcu secret set production/worker sidekiq_concurrency 10 </pre><h4>Restarting Deployments</h4><p>After a secret is changed, the more common action is to restart the deployments that read the secret. There isn’t a standard way of doing this, so we opted to take the advice of <a href="https://twitter.com/lukeheidecke">Luke Heidecke</a> and annotate the deployment and push those changes. This makes Kubernetes handle then restart of the pods.</p><pre>kcu deployment restart staging/website</pre><h4>Pushing A New Image</h4><p>Finally, after the image is built, it was less than ideal to copy and paste the new image name into the config. Why not have a deploy command like Heroku?</p><pre>kcu deploy master<br>kcu deploy staging</pre><p>Ok, I’m cheating a bit. There’s a kcu.yml you need to setup in your repo.</p><h4>That’s It</h4><p>We considered other features like automatically watching the rollout after you deploy, but decided to pause with these three. In the interest of not over-engineering our tools, we’ll wait and see what else bothers us.</p><p>We would <a href="https://github.com/bloom-solutions/kcu">love some comments and especially pull requests</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44d209122843" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bloomsolutions/easy-team-management-of-kubernetes-config-44d209122843">Easy Team Management of Kubernetes Config</a> was originally published in <a href="https://medium.com/bloomsolutions">bloomsolutions</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>