<?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 Dominika Rogala on Medium]]></title>
        <description><![CDATA[Stories by Dominika Rogala on Medium]]></description>
        <link>https://medium.com/@DominikaRogala?source=rss-a1f4fe2e131d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*K35UnQlfX2XlaV1pQx9ePQ.jpeg</url>
            <title>Stories by Dominika Rogala on Medium</title>
            <link>https://medium.com/@DominikaRogala?source=rss-a1f4fe2e131d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 07:47:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@DominikaRogala/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[How to start organising your company if you have no time or money]]></title>
            <link>https://medium.com/@DominikaRogala/how-to-start-organising-your-company-if-you-have-no-time-or-money-74d44194c600?source=rss-a1f4fe2e131d------2</link>
            <guid isPermaLink="false">https://medium.com/p/74d44194c600</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[inspiration]]></category>
            <dc:creator><![CDATA[Dominika Rogala]]></dc:creator>
            <pubDate>Fri, 07 Jul 2017 07:59:06 GMT</pubDate>
            <atom:updated>2017-07-07T07:59:06.039Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*St8PbtiMT3LY7PgxkPbQgQ.jpeg" /><figcaption>Photo: Simson Petrol</figcaption></figure><p>You already have a big team and you haven’t noticed when it grown so fast. You are a master of chaos-driven development. But you feel that there’s so much to gain in managing it all better. At the moment you have neither time nor money to start working on introducing serious management.</p><p>I talked recently with leaders from 2 startups that went from a small team to over 50 people. Problems they observe are similar to my experiences building R&amp;D team from scratch only the scale is much bigger.</p><p>Here’s a couple of ideas I checked with smaller teams and observed working in big environments as well. Things you can use to start turning your chaos into order.</p><p><strong>Observe and find out what already works</strong>. There are things some teams in your company already organised on their own. Try to apply this in other teams or areas.</p><p><strong>Ask your people.</strong> For ideas. For what makes them <em>feel</em> good (and don’t mistake the question for what makes them work good). Treat it as your company UX research. Your questions may be: <br><em>What did your best day at work/meeting look like? What was so good about it?</em> What <em>did your worst day at work/meeting look like? What was so bad about it?</em></p><p><strong>Make sharing ideas easy.</strong> Put a poster on a wall in your kitchen with <em>I love it/What irritates me </em>table on it where everyone can post a post-it note. Set a virtual inbox or a channel on Slack for praises/complaints/ideas where people can easily send their thoughts.</p><p><strong>Brainstorm.</strong> Ask people the right questions and make them write 1 answer per post-it. Make the questions specific. Example:<em> If you could change one thing to make our company better, what would it be?</em> Be careful not to promise anything. Instead, let people know you’re together looking for ways to make the company a better place to work.</p><p><strong>Find the smallest issue with the biggest impact and start with resolving that. </strong>Think this 5mm domino causing over 1m domino to fall:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fy97rBdSYbkg%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dy97rBdSYbkg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fy97rBdSYbkg%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/48595746259a778bdc0abf853d87e44b/href">https://medium.com/media/48595746259a778bdc0abf853d87e44b/href</a></iframe><p><strong>Experiment </strong>— check out ideas on solving a problem. Tell everyone it’s an experiment. It’s easier to introduce something new if you and your team know it is not necessarily permanent. And it’s much easier to change your mind if you haven’t made the new rules final. If anyone has a good idea — give it a try.</p><p><strong>Deal with bad ideas withouth sentiment.</strong> If you tried something and it didn’t work — let it go. Make space for new experiments. But look for reasons why the idea was bad.</p><p>Bad ideas may be temporarily bad. It’s good to have them written down for future reference. What doesn’t work in a team of four ma be a life saver when you grow to 50.</p><p><strong>Look for patterns.</strong> If one person says the office is too cluttered for her to focus, maybe it’s an individual problem. If 3 people say that, consider looking for bigger space. Or getting rid of unused equipment.</p><p><strong>Make sure people get credit for their input.</strong> If somebody’s idea got verified and you’re using it now, they deserve at least a round of applause from all their colleagues.</p><p><strong>Set a no-meetings day.</strong> For everyone including you. It may seem scary or impossible to do. But remember, it’s only an experiment. After a month or two, if it doesn’t work, let it go.</p><p>Dealing with growth of your team is a challenge. You’re growing fast and usually there’s no quality time to spend on adjusting management. Don’t give up! If you want to organise your ever-growing team better, try out one of this ideas and let us know how it went in comments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O2N5Pv76pHNiOvcrQWV3yw.jpeg" /><figcaption>Photo: Jeff Sheldon</figcaption></figure><h3>If you enjoyed this article, please recommend it by clicking on the heart below.</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74d44194c600" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Worst Hardware Development Sprint Ever]]></title>
            <link>https://medium.com/@DominikaRogala/worst-hardware-development-sprint-ever-1c333a93b92c?source=rss-a1f4fe2e131d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c333a93b92c</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[hardware]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Dominika Rogala]]></dc:creator>
            <pubDate>Thu, 15 Sep 2016 12:44:07 GMT</pubDate>
            <atom:updated>2016-09-15T13:12:56.355Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nin0nMzd2x3YpwzxlxsBKw.jpeg" /><figcaption>Destroy everything. Photo: <a href="https://unsplash.com/@darmfield">Dawn Armfield</a></figcaption></figure><p>How to make sure your Scrum Sprint makes no sense and brings no effect.</p><p>These brilliant ideas are universal. Feel free to use them to destroy your work.</p><p>1. Let stakeholders completely change their mind in the middle of Sprint. They are stakeholders so they know what’s best for the product, right?</p><p>2. Have many distractions and extra tasks. All are urgent and unexpected. Like photo shoot for company website.</p><p>3. Don’t notice cables are attached incorrectly. Repeat tests twice because of that.</p><p>4. Accidentally destroy your prototype made for tests. Repeat tests twice again.</p><p>5. Don’t make sure people you need to run tests are available in advance.</p><p>6. Break the foosball table. You don’t need it anyway.</p><p>7. Estimate tasks fast just to get over it.</p><p>8. Super underestimate all tasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*rzL-SXOJFioAEpcmWoGMrQ.jpeg" /></figure><p>9. Ignore what you planned for the Sprint and do whatever comes to your minds at the moment.</p><p>10. Waste a lot of time working on unimportant details.</p><p>11. Continue working on things that can’t be resolved.</p><p>12. Start writing documentation from scratch. So much fun.</p><p>13. Don’t check if you have all parts needed to complete a task. Wait over one week for delivery and don’t finish the task on time.</p><p>14. Ignore task review — approve teammates’ tasks without even looking at them.</p><p>15. Don’t check every day if we are focused on our goal and running in time.</p><p>16. Stop doing Daily Scrums at all. You work so well there’s no daily planning needed, don’t you?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*bpzJ5shrUJjUAZSw6M4Y3Q.gif" /><figcaption>source: <a href="https://churchm.ag/stand-up-meetings-comic/">churchm.ag</a></figcaption></figure><p>17. Play foosball 5 times a day. (Maybe breaking it was not that bad?)</p><p>This list is a result of games from my teams&#39; Sprint Retrospectives. Big thanks to my team at <a href="http://www.rnd.neurodevice.pl/">Neuro Device</a> for coming up with these ideas. Big thanks to <a href="http://plans-for-retrospectives.com/">retromat</a> that’s full of great retro games.</p><h3>If you enjoyed this article, please recommend it by clicking on the heart below.</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c333a93b92c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Estimating Time in Hardware Development]]></title>
            <link>https://medium.com/@DominikaRogala/estimating-time-in-hardware-development-9046f79d2527?source=rss-a1f4fe2e131d------2</link>
            <guid isPermaLink="false">https://medium.com/p/9046f79d2527</guid>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[hardware]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Dominika Rogala]]></dc:creator>
            <pubDate>Mon, 05 Sep 2016 18:03:59 GMT</pubDate>
            <atom:updated>2016-09-05T18:06:02.283Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*efMHYhrLaXB-A1qC.jpg" /><figcaption>Estimate time in hardware with care, source: <a href="http://freshgadgets.nl/wekker-bom">Fresh Gadgets</a></figcaption></figure><p>Life would be great if we never had to answer the question:</p><blockquote>How long will it take?</blockquote><p>But we have to.</p><p>It’s always tricky.</p><p>It is super tricky in hardware. In new projects with unknown technologies. When you work with physical objects — electronic components, circuits, enclosures. When you have new people on your team. When you have yet to find the solution…</p><p>There are so many unknowns it should be called <em>guesstimating</em>. And you better call it that to your boss/investor/family.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/0*MJI7Gn6sLJkaF7OL.jpg" /><figcaption>The wheel of estimation (source: <a href="http://www.commitstrip.com/en/2012/04/24/the-wheel-of-estimation/">commitstrip</a>)</figcaption></figure><p>There are many things to take into account in hardware development. Some of them are different with every new project you start. Even if you can, more or less, estimate how much work it would take to finish, there are many things you can miss.</p><p>Having managed many hardware projects, I’ve made many mistakes when estimating. With each of them my list of things to remember is more complete. And my teams meet more deadlines.</p><p>To help you with planning and save you from learning all this the hard way, here are some things to consider:</p><h4>Work is hard to count</h4><p>1. When people say <em>It will take a week </em>they mean full working week.<br>It may seem obvious but see point 2.</p><p>2. Not all weeks are working weeks. Not all working weeks are full working weeks.<br>National holidays steal your weeks. So do vacations. <br>People get sick and can’t work.<br>People go to <a href="https://medium.com/@DominikaRogala/one-thing-funerals-teach-us-about-time-management-56bf7aa983fc#.2pov3p2cg">funerals</a>.<br>You send them for trainings, etc.</p><p>3. A month is on average 20 days long. Not 30.</p><h4>Hardware is not software</h4><p>4. Electronic components can’t be downloaded like software.<br>You’ll wait for them a day, a week or much longer.</p><p>5. Your PCB is not ready when you finish designing it. You still have to order it and wait days till it arrives.</p><p>6. Your PCB is not ready when it comes from printing company. You still have to test it.</p><p>7. Your mechanical parts are not ready when you finish designing them. You still have to order them and wait days till they come. Even 3D printing takes time.</p><p>8. Your mechanical parts are not ready when they come. You still have to check if they fit and work.</p><p>9. Testing hardware takes a lot of time. Add it to every step of development.</p><p>10. If something goes wrong you may need to redesign PCB or mechanical parts. And order them again. And wait again. And test them again.</p><p>11. Chinese New Year is in second half of January or the first half of February and holidays last at least one week. <br>Whatever you order from China, don’t do it then. You’ll have to wait. And you’ll have to wait at your local suppliers. Guess what — everyone is asking them to do things they usually order from China. So you’ll wait longer than usual there. Been there, waited.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tsYGH6IAIwCX6yCX.png" /><figcaption>Estimation Team from <a href="https://stanfy.com/blog/how-to-estimate-mobile-projects-why-estimation-fails-and-how-to-prevent-this/">Stanfy</a>.</figcaption></figure><h4>Your team consists of humans, not robots.</h4><p>12. Your team needs time to research the technologies and dive into chosen one.</p><p>13. Research takes more than anyone expects.</p><p>14. When someone joins your team they need a lot of time to get up to speed. And your team needs a lot of time to help them with onboarding.</p><p>15. If you outsource, let’s say, enclosure design to a freelancer, someone will have to communicate with them. Prepare briefs, answer questions, check their work and answer more questions. And it — wait for it — takes more time than you think.</p><p>Have I covered everything? — for sure not! More to come in part two of this post. <strong>Any ideas on things to remember when planning hardware? Leave a comment!</strong></p><h3>If you enjoyed this article, please recommend it by clicking on the heart below.</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9046f79d2527" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One thing funerals teach us about time management]]></title>
            <link>https://medium.com/@DominikaRogala/one-thing-funerals-teach-us-about-time-management-56bf7aa983fc?source=rss-a1f4fe2e131d------2</link>
            <guid isPermaLink="false">https://medium.com/p/56bf7aa983fc</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[time-management]]></category>
            <dc:creator><![CDATA[Dominika Rogala]]></dc:creator>
            <pubDate>Tue, 22 Mar 2016 21:57:05 GMT</pubDate>
            <atom:updated>2016-03-23T13:12:01.365Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cHADhjD4oWzROWxjNaxfTQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/veri_ivanova">Veri Ivanova</a></figcaption></figure><p><em>This post will tell you nothing about values or getting to know what is important in life. Pure time management observation.</em></p><p>Last week I’ve attended a funeral of a person I have never met. And it was a great lesson.</p><p>I had a hard week at work. I was running late on most of my weekly goals. I had every day packed up with working blocks to achieve them. It was late Wednesday and I was planning on how to complete it all till the end of the week. In the middle of this oh-so-important-everything my husband called. And asked if I could go with him on the funeral the next day.</p><p>I first thought— <em>no way</em>, I have to do this and that and it’s so late. Have I known it earlier…</p><blockquote>Yeah, could you please, like, announce your death a month in advance so I can put it on my to-do list?</blockquote><p>I’ve never met the person. She was a not-so-close relative of my husband and one of the oldest in family. But we try to attend funerals whenever we can for two main reasons. To show that we care for the family and to meet the people we would probably not meet on other occasions.</p><p>I decided I’d go to work the next day but be prepared to leave half-day to go to the funeral. And if something happens I’d just call Marek and tell him I can’t go. But nothing happened. I squeezed the important things in this half of day and let go of some other.</p><p>As I was walking through cemetery in the middle of the sunny day I thought it is a great example of what <a href="https://medium.com/u/76ce36768">Lolly Daskal</a> once <a href="http://www.lollydaskal.com/leadership/master-time-management-from-inside-out/">wrote</a>:</p><blockquote>To master time management is to set priorities among your goals. There is never enough time to do everything, but there is always enough time to do what is important.</blockquote><p>Funerals teach you exactly that. To set priorities.</p><p>It just happens. It can’t be planned. You get informed a day or two earlier. And you are, usually, not obliged to go there. I decided to go and my week didn’t collapse. So maybe it’s time to set <em>funeral priority level </em>for some truly important tasks.</p><p><em>Like what you read? Why don’t you hit recommend and share it with your friends? Thanks!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56bf7aa983fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nie jestem Czarną Wołgą.]]></title>
            <link>https://medium.com/@DominikaRogala/nie-jestem-czarn%C4%85-wo%C5%82g%C4%85-372488d9dfeb?source=rss-a1f4fe2e131d------2</link>
            <guid isPermaLink="false">https://medium.com/p/372488d9dfeb</guid>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[polish]]></category>
            <category><![CDATA[diversity]]></category>
            <dc:creator><![CDATA[Dominika Rogala]]></dc:creator>
            <pubDate>Sun, 04 Oct 2015 20:17:06 GMT</pubDate>
            <atom:updated>2015-10-04T20:17:06.020Z</atom:updated>
            <content:encoded><![CDATA[<p>Na wykładach i prezentacjach branżowych regularnie słyszę:</p><blockquote>Jak Panowie widzą…<br>Kiedy zagłębią się Panowie w ten temat…</blockquote><p>Spotkanie z poważną firmą marketingową. Szef przedstawia mnie jako twórcę prototypu i modelu przygotowywanego do sprzedaży urządzenia. Komentarz szefa tej firmy:</p><blockquote>Nie wiedziałem, że kobiety zajmują się takimi rzeczami.</blockquote><p>Słyszałaś i słyszałeś już kiedyś podobne historie.</p><p>Koleżanka opowiadała Ci o tym, jak nie mogła zaliczyć projektu z programowania. Prowadzący zakładał, że dziewczyna na pewno taki dobry projekt musiała od kogoś ściągnąć.</p><p>U siostry kumpla wykładowcy na studiach mówią, że kobieta nie może być dobrym inżynierem.</p><p>Znajoma na imprezie wspominała, jak prowadziła techniczną prezentację produktu u klienta. Przyszła na salę kilka minut wcześniej. Jeden z grupy mężczyzn — jej przyszłych słuchaczy — odruchowo poprosił, żeby poszła skserować jego dokumenty. Uznał, że musi być sekretarką.</p><p>Ale, myślisz sobie, przecież to się <strong>tak</strong> <strong>naprawdę </strong>nie dzieje.</p><blockquote>Relacje dziewczyn i kobiet o niewłaściwym ich traktowaniu na uczelni albo w pracy są traktowane jak <strong>urban legends.</strong></blockquote><p>Rozmawiam z bliskim kolegą. Opowiadam o tym spotkaniu z marketingowcami. Śmiejemy się. On mówi, że to żenada. Ja się zgadzam. Przejął się.<br>Ale od razu stwierdza, że to chyba się raczej nie zdarza. Mówię, że zdarza.<br>Podaję przykłady osób, które znam — mojej siostry, koleżanki…<br>Już się tak nie przejmuje. Nie zna ich.</p><blockquote>Nasze historie mają zasięg jednego uścisku dłoni.</blockquote><p>Wygląda na to, że dopóki nie usłyszysz takiej historii z pierwszej ręki to nie uwierzysz, że to się dzieje.<br>Koniecznie od bliskiej osoby (siostry, dziewczyny, przyjaciółki).</p><p>Poznałam przy okazji <a href="http://mceconf.com/">Mobile Central Europe</a> prelegenta z Kalifornii. Dobrze nam się rozmawiało. Wypłynął temat dziewczyn w IT. Opowiedziałam Kevinowi kilka sytuacji z moich studiów na Elektronice.<br>Na przykład odbiór jednego z moich projektów studenckich. Robiłam go w grupie z 3 chłopakami. Każdy z nas był oceniany za wkład w ostateczne rozwiązanie zadania projektowego.</p><p>A dokładniej tak:</p><blockquote>Pan Patryk, widać, że się dużo napracował — 15 punktów.<br>Pani Dominika, wiadomo — dziewczyna — 15 punktów.</blockquote><p>Kevin zareagował na te historie z typowym zdziwieniem.</p><blockquote>Serio? To są takie historie, które niby każdy z nas gdzieś słyszał, ale nie sądziłem, że one się dzieją naprawdę.</blockquote><p>O to właśnie chodzi. Nie o same sytuacje i historie — to sprawa złożona, na osobny tekst albo nawet książkę.</p><p>O zmianę z <em>coś tam kiedyś o tym słyszałem </em>na <em>wiem, że to się dzieje naprawdę.</em></p><p>Kiedy następnym razem usłyszysz jedną z takich historii, nie wrzucaj jej do szuflady legend miejskich, zaraz obok Czarnej Wołgi.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=372488d9dfeb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Should you go to Bluetooth Innovation Training?]]></title>
            <link>https://medium.com/@DominikaRogala/should-you-go-to-bluetooth-innovation-training-cf236d3c038b?source=rss-a1f4fe2e131d------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf236d3c038b</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[bluetooth]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Dominika Rogala]]></dc:creator>
            <pubDate>Mon, 21 Sep 2015 21:34:47 GMT</pubDate>
            <atom:updated>2015-09-22T06:42:34.457Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NmHBdVU-zqTdnMQpxJ1ong.jpeg" /></figure><p>A week ago I participated in Bluetooth Innovation Training in London. I went there mostly out of curiosity about Bluetooth Developer Studio. And <a href="https://www.bluetooth.org/">Bluetooth SIG</a> trainings at all.</p><p>What I liked most was <a href="https://twitter.com/bluetooth_mdw">Martin Woolley’s</a> introductory talk on Bluetooth Low Energy. From the general idea behind BLE through its market potential to technological details. The level of details was interesting enough for someone knowing the topic. At the same time it was not too complicated for newbies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*JGLgn3klaz6-tapGIEyiDA.jpeg" /></figure><p>Training parts by Martin were actually quite fun. I even felt sorry for him when most of the audience was indifferent to his cats slides. Come on, what kind of engineers ignore cute cats?</p><p>Martin also introduced Bluetooth Developer Studio — a tool that will significantly speed up your BLE development. <strong>Or so Bluetooth SIG claims. </strong>You can use it for code generation and testing of both virtual and real BLE devices. Taking part in the training gives you access to BDS beta so you can check it out for yourself. I’ll write a separate post on BDS soon.</p><p>Another thing covered was <a href="https://www.nordicsemi.com/">Nordic Semiconductor</a> BLE chipsets. One of Nordic’s engineers talked about how to use nRF51 Series to develop BLE devices. And how they deal with BLE stack. He also presented Nordic’s BDS plug-in. I currently work on nRF51 and hope to check its code generation in one of my projects.</p><p>What I didn’t like was a fully marketing presentation by one of the sponsors. It had no value to me so forgive me for not even remembering the company name.</p><h3>What you’ll get?</h3><ul><li>access to the Bluetooth Developer Studio limited beta program</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/628/1*z1LqK93keeQG9cfeLqHeRw.jpeg" /><figcaption>nRF51 DK</figcaption></figure><ul><li><a href="https://www.nordicsemi.com/eng/Products/nRF51-DK">nRF51 Development Kit</a></li><li>BluetoothPTS dongle to test physical devices against the Bluetooth Developer Studio.</li><li>full training material with nRF, Android Studio and Bluetooth Developer Studio examples</li></ul><h3>So, answering the initial question — should you go there?</h3><p><strong>Yes</strong>, if you know a bit about BLE (tiny bit should be enough). And you want to get some general understanding. Plus you’re interested in Bluetooth Developer Studio features.</p><p><strong>Maybe</strong>, if you know absolutely nothing about BLE and want to know. Be prepared you may not follow everything during the training.</p><p><strong>Maybe</strong>, if you are an experienced BLE developer. Most of the topics covered you already know. But if you want to get a look at BDS and its features — it’s worth trying.</p><p><strong>No…</strong> well I’m not sure if there is a no-no group for this training. But if you are familiar with BLE and you can wait for the official release of BDS there may be a better way to spend your time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf236d3c038b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Królowa kodu]]></title>
            <link>https://medium.com/@DominikaRogala/kr%C3%B3lowa-kodu-299971801f95?source=rss-a1f4fe2e131d------2</link>
            <guid isPermaLink="false">https://medium.com/p/299971801f95</guid>
            <category><![CDATA[polish]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[code]]></category>
            <dc:creator><![CDATA[Dominika Rogala]]></dc:creator>
            <pubDate>Wed, 09 Sep 2015 06:50:13 GMT</pubDate>
            <atom:updated>2015-09-09T06:50:13.413Z</atom:updated>
            <content:encoded><![CDATA[<h4>Spopularyzowała termin debugging<em> </em>na oczyszczanie kodu z błędów. Zaczęło się od usunięcia ćmy wstrzymującej pracę jednego z pierwszych komputerów.</h4><p>Jako admirał U.S. Navy pracowała nad pierwszym komputerem — <a href="http://en.wikipedia.org/wiki/Harvard_Mark_I">Harvard Mark 1</a>.</p><p>Oprogramowała rozwiązanie ostatniego elementu układanki pozwalającej stworzyć bombę atomową.</p><p>Prowadziła zespół, który stworzył pierwszy kompilator kodu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*I-YMHqA6n3rB4FpE.jpg" /></figure><p>Współtworzyła <a href="https://en.wikipedia.org/wiki/FLOW-MATIC">FLOW-MATIC</a>, pierwszy język programowania podobny do języka używanego przez ludzi.</p><blockquote>“Kiedy twierdziłam, że da się wydawać komputerom polecenia po angielsku, mówili, że jestem szalona. Co z tego, skoro działało.”</blockquote><p>W oparciu o jej prace nad pierwszym kompilatorem i językiem FLOW-MATIC powstał COBOL — język, który do 2000 roku stanowił 70% czynnie działającego kodu na świecie.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZswblstEosQ9Pb8G.jpg" /></figure><p>Chcesz poznać całą historię?</p><p>Obejrzyj koniecznie krótki 15-minutowy film dokumentalny “The Queen of Code” (reż. <a href="http://www.imdb.com/name/nm1843026/">Gillian Jacobs</a>) o Grace Hopper — błyskotliwej programistce i wizjonerce.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fsw88.go.com%2Fb%2Fss%2Fwdgespvideo%2F5.4%2FREDIR%2F0057640791580376161441731616897%3FD%3D..%26url%3Dhttps%253A%252F%252Fonce.unicornmedia.com%252Fnow%252Fod%252Fauto%252F4d993388-8b49-4f34-9e48-87906e690281%252F85957be9-026a-415e-a8ce-7bfdc19d5e23%252Ff03ba1a4-c6fe-4525-8c1b-627a90f016eb%252Fcontent.once%253FUMADPARAMreferer%253Dhttps%253A%252F%252Fespn.go.com%252Fvideo%252Fclip%253Fid%253D12205119%2526UMADPARAMcsid%253Despn%253Aclips%253Atwittermobile%26pe%3Dmedia%26mediaName%3DFIVETHIRTYEIGHT%253A%253A538_FILMS%253A%253Adm_150121_QueenofCode_12205119%26mediaLength%3D991%26mediaPlayer%3Dembed09%26mediaSession%3D0-0%26c3%3Dvideoid%253DFIVETHIRTYEIGHT%253A%253A538_FILMS%253A%253Adm_150121_QueenofCode_12205119%26v2%3Dvideoid%253DFIVETHIRTYEIGHT%253A%253A538_FILMS%253A%253Adm_150121_QueenofCode_12205119%26events%3Devent1%26v52%3DinlinePlayer%26c52%3DinlinePlayer%26v53%3DinlinePlayer%253Atwitter%26c53%3DinlinePlayer%253Atwitter&amp;src_secure=1&amp;url=http%3A%2F%2Fespn.go.com%2Fvideo%2Fclip%3Fid%3D12205119%26ex_cid%3Despnapi_internal&amp;image=http%3A%2F%2Fa2.espncdn.com%2Fcombiner%2Fi%3Fimg%3D%252Fmedia%252Fmotion%252F2015%252F0121%252Fdm_150121_QueenofCode%252Fdm_150121_QueenofCode.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=video%2Fmp4&amp;schema=go" width="800" height="448" frameborder="0" scrolling="no"><a href="https://medium.com/media/6248b53c3e4feff6584fd7742d30a0aa/href">https://medium.com/media/6248b53c3e4feff6584fd7742d30a0aa/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=299971801f95" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dlaczego dołączysz do #iLookLikeAnEngineer?]]></title>
            <link>https://medium.com/@DominikaRogala/dlaczego-do%C5%82%C4%85czysz-do-ilooklikeanengineer-d854cd2ca272?source=rss-a1f4fe2e131d------2</link>
            <guid isPermaLink="false">https://medium.com/p/d854cd2ca272</guid>
            <category><![CDATA[polish]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[diversity]]></category>
            <dc:creator><![CDATA[Dominika Rogala]]></dc:creator>
            <pubDate>Tue, 01 Sep 2015 07:09:25 GMT</pubDate>
            <atom:updated>2015-09-04T17:52:51.437Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jtuIYsUg_PLTE2DTdkMDxw.jpeg" /><figcaption>Programistki, które spotkałam na konferencji Codepot. Było ich więcej :)</figcaption></figure><p>Kiedy chodziłam po konferencji programistycznej <a href="http://www.codepot.pl/">Codepot</a> z kartką #iLookLikeAnEngineer usłyszałam pełen troski i przerażenia w głosie komentarz jednego z uczestników (chłopak):</p><blockquote>Ale przecież Ty dobrze wyglądasz, nie jak inżynier.</blockquote><h3>O co chodzi?</h3><p>Jednym zdaniem: o zmianę powszechnego przekonania o tym, jak wygląda lub nie wygląda inżynier.</p><p>A dokładnie o to, że każdy inżynier — kobieta i mężczyzna — <strong>wygląda jak inżynier, bo nim jest.</strong></p><h3>Skąd taka akcja?</h3><p>Zaczęło się od tego, że firma OneLogin zrobiła bilboardową kampanię rekrutacyjną. Prosty przekaz: zdjęcie pracownika i krótka osobista opinia o zespole.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1LeZl8FeTABlp6wJpNaAdw.jpeg" /></figure><p>Byłaby to kolejna fajna akcja promocyjna, gdyby nie reakcje na billboard ze zdjęciem Isis Wenger — programistki OneLogin.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U-BsVBQCbZPBTl5x4kXV6Q.jpeg" /></figure><p>Widok kobiety promującej pracę w firmie informatycznej był dla niektórych tak niewiarygodny, że zaczęli wrzucać na Twitterze i Facebooku zdjęcia billboardu.</p><blockquote>Myślę, że chcieli tym zachęcić kobiety, ale trafiają raczej tylko do mężczyzn. Może o to właśnie im chodziło?</blockquote><blockquote>Ciekaw jestem czy ktoś kupi ten obraz tego, jak wygląda programistka.</blockquote><blockquote>Za ładna jak na inżyniera.</blockquote><p>Niektórym przeszkadzał też “seksowny uśmieszek” Isis.</p><p>Po dwóch dniach czytania o sobie, że jest za ładna, by być programistką, Isis napisała na <a href="https://medium.com/the-coffeelicious/you-may-have-seen-my-face-on-bart-8b9561003e0f">blogu</a>, że nie prosiła się o całe to zamieszanie i jest to dla niej, jako ekstremalnej introwertyczki, trudna sytuacja.</p><p>Opisała też swoje doświadczenia z pracy w “męskiej” branży i postanowiła wykorzystać szum wokół siebie do zmiany stereotypów narosłych wokół zawodów inżynierskich.</p><p>Post Isis kończy się wezwaniem do działania:</p><blockquote>Chcesz pomóc rozpowszechnić świadomość i zwiększyć różnorodność branży technologicznej?</blockquote><blockquote>Nie pasujesz do szablonu, wg którego ludzie oceniają jak “powinien wyglądać” inżynier?</blockquote><blockquote>Jeśli Twoja odpowiedź na któreś z tych pytań brzmi <strong>tak, </strong>zapraszam Cię do pomocy w popularyzowaniu i zmianie definicji tego, “jak powinien wyglądać inżynier”. <strong>#iLookLikeAnEngineer</strong></blockquote><p>Na jej odzew w pierwszych kilku dniach odpowiedziało<strong> 50,000</strong> osób. Akcja szybko zmieniła się w międzynarodową kampanię obecną w ponad 50 krajach.</p><p>25. sierpnia Isis Wenger została zaproszona do Zespołu Doradców <a href="http://www.womenwhocode.com/">Women Who Code</a> — organizacji non-profit inspirującej kobiety do pracy w branży technologicznej.</p><p>Do tej pory na Twitterze <strong>#iLookLikeAnEngineer</strong> pojawił się już <strong>115,596 razy.</strong></p><h3>I co teraz?</h3><p>Dołączamy do międzynarodowej akcji i szerzymy ją u nas.</p><p>Pokażmy, że w branży technologicznej w Polsce też pracują różni ludzie. O różnych typach urody i stylach ubierania. O różnym wyglądzie.</p><p><strong>Każdy inżynier wygląda jak inżynier, bo nim jest.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/615/1*WJxqGnmbRfVm1bBpf5Jwxg.jpeg" /></figure><p>1. Zrób sobie zdjęcie, dodaj krótki opis tego czym się zajmujesz i wrzuć na Twittera/Facebooka/Instagram z hasztagiem #iLookLikeAnEngineer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*jEr9SfbD7oaZdC3m_sxtcw.jpeg" /></figure><p>2. Zbierz ekipę z pracy, studiów albo konferencji i zróbcie sobie zdjęcie grupowe. Możesz też powiedzieć swojemu szefowi, że wrzucenie takiego zdjęcia na firmowy profil społecznościowy to świetny pomysł (robią tak duże i małe firmy z całego świata, choćby Intel czy NASA).</p><p>3. <strong>Udostępnij ten wpis</strong> albo prześlij go znajomym i zachęć, by się dołączyli!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d854cd2ca272" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>