<?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 Amarildo Lucas on Medium]]></title>
        <description><![CDATA[Stories by Amarildo Lucas on Medium]]></description>
        <link>https://medium.com/@amarildolucas?source=rss-fbc33eca6c0e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*JEVSp15sq4b2Oh4DPF3K-g.jpeg</url>
            <title>Stories by Amarildo Lucas on Medium</title>
            <link>https://medium.com/@amarildolucas?source=rss-fbc33eca6c0e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 22:23:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@amarildolucas/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 Run Multiple Claude Code Agents on the Same Xcode Project]]></title>
            <link>https://medium.com/@amarildolucas/how-to-run-multiple-claude-code-agents-on-the-same-xcode-project-b0ee921eb8de?source=rss-fbc33eca6c0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0ee921eb8de</guid>
            <dc:creator><![CDATA[Amarildo Lucas]]></dc:creator>
            <pubDate>Fri, 30 Oct 2026 20:45:54 GMT</pubDate>
            <atom:updated>2026-10-30T20:45:54.985Z</atom:updated>
            <content:encoded><![CDATA[<p>Learn how to run multiple Claude Code agents on the same Xcode project without simulator conflicts.</p><p>Running two or more Claude Code agents on one Xcode project is the natural next step once a single agent works well. <strong>The expectation is two tasks in roughly the time of one.</strong></p><p>Where it goes wrong is not in the code. An iOS project shares more than files: the simulator, the installed app, and the data the app saved. I wanted to see what happens when two agents reach that shared part.</p><p><strong>I gave two Claude Code agents separate tasks on a small SwiftUI weather app, each in its own Git worktree. One added a feature. The other added a test. Neither prompt named a simulator.</strong></p><p>Both agents picked the <strong>iPhone 18 Pro</strong> that was already booted. Both builds succeeded, and both reported success.</p><p>Then I checked what was installed. The simulator was running the second agent’s build, and the first agent’s build had been replaced. Neither agent’s output mentioned the other, or that its build was gone.</p><p>Worktrees keep files apart. They don’t keep simulators apart.</p><h3>Why it happens</h3><p>If two sessions install the same app on one simulator, they share the same build, app data, and screen. To see it, I built the app from two worktrees with different build numbers (<strong>111</strong> and <strong>222</strong>) and the same bundle ID. The first worktree branch (let’s call it Agent A) installed and launched its build, then the second (Agent B) installed its own, both on one simulator. The commands and results are specific to this example app, and the full run is in this gist:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4c2487db6e5158927a26ee2b2ff59cae/href">https://medium.com/media/4c2487db6e5158927a26ee2b2ff59cae/href</a></iframe><p>Four things happened, and none of them raised an error:</p><ul><li>The simulator held build <strong>222</strong>. Agent A’s build <strong>111</strong> was gone.</li><li>The app that <strong>A</strong> had launched was no longer running. The log shows the install sending a terminate request to the running app.</li><li>The cities that build <strong>111</strong> saved in <em>UserDefaults</em> were still there for build <strong>222.</strong> The log shows No saved cities found; seeding defaults (2) on first launch and <strong>loadCities loaded 2 cities from UserDefaults</strong> afterward. Installing over an existing app keeps its data; only uninstalling removes it.</li><li>When both agents launched their app afterward, simctl returned the same <strong>process ID</strong>. Agent A was now running <strong>B’s</strong> build, and reading the installed build number gave <strong>222</strong>, not the <strong>111</strong> it had built.</li></ul><h3>What real Claude Code agents do</h3><p>The manual test forces the collision. Real agents don’t need forcing. I started one session per worktree with claude --worktree and gave each agent an ordinary task, the way you would without thinking about simulators.</p><p>Agent A:</p><pre>Add a cloud-cover line to the humidity tile in WeatherApp. Build and test it, run the app on a simulator to check it, and tell me which simulator you used. Do not commit.</pre><p>Agent B:</p><pre>Add a test in IconMappingSwiftTests.swift for unknown weather codes. <br>Change WeatherIcon.swift only if the new test fails. <br>Build and test it, run the app on a simulator to check it, <br>and tell me which simulator you used. Do not commit.</pre><p>Both agents picked the booted <strong>iPhone 18 Pro</strong> and installed on it in both runs I did.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vCPq8szitydp4sZBjbBJpA.avif" /></figure><p>To see the consequence, I made the overlap certain. I stamped <strong>Agent A’s </strong>build <strong>111</strong> and <strong>Agent B’s </strong>build <strong>222</strong>, added “after launching, wait 90 seconds, then read the installed build number” to each prompt, and pointed both agents at the same simulator. Both builds succeeded. Only the check told them apart:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8-_rXWnLhZMMrnQWHVeFhA.avif" /></figure><p>Agent A&#39;s installed build was <strong>222</strong>, not <strong>111</strong>, and its process had changed. Agent B saw nothing wrong because it had installed last. Without the check, nothing in Agent A&#39;s output would have said so.</p><h3>Three ways to approach it</h3><p>You have three options:</p><ul><li><strong>Run one agent at a time.</strong> There is no collision, but the second task waits for the first, which defeats the point of running two.</li><li><strong>Give each agent its own simulator</strong>, set up by hand. It works, and the next section shows how.</li><li><strong>Use a tool that keeps each session’s simulator</strong>, worktree, and build state together. The last section shows how it does.</li></ul><h3>The fix by hand: one simulator per agent</h3><ol><li>Clone one simulator per agent, from a base simulator that is shut down. xcrun simctl clone prints each new UDID, and xcrun simctl list devices lists them all.</li></ol><blockquote>xcrun simctl shutdown &lt;base-udid&gt;<br>xcrun simctl clone &lt;base-udid&gt; “Agent A”<br>xcrun simctl clone &lt;base-udid&gt; “Agent B”<br>xcrun simctl boot &lt;agent-a-udid&gt;<br>xcrun simctl boot &lt;agent-b-udid&gt;</blockquote><p>2. Tell each agent which simulator is its own. Clones alone change nothing, because both agents took whichever simulator was already booted. Add this to each prompt (Agent A for the first prompt and B for the second):</p><blockquote>Use only the simulator named “Agent A” (UDID &lt;agent-a-udid&gt;). <br>Do not touch any other simulator.</blockquote><p>3. Pass the same UDID to every build and test command:</p><blockquote>xcodebuild test -project WeatherApp.xcodeproj -scheme “Weather App” -destination “platform=iOS Simulator,id=&lt;agent-a-udid&gt;” -derivedDataPath .build/dd</blockquote><p>I ran the same two prompts again with those lines and the 90-second check. <strong>Agent A</strong> read <strong>111</strong> and <strong>Agent B</strong> read <strong>222</strong>, and neither process had changed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m7x3RLgqIoAMTiQplz_QlQ.avif" /></figure><p>This works, but you have to repeat the setup.</p><h3>Let FlowDeck manage the simulator</h3><p>Every new session needs a clone, a UDID, and a prompt that carries it. A mismatched UDID sends both agents back to the same simulator, and a green run will not tell you.</p><p><a href="https://www.youtube.com/watch?v=A0jSTbS7nKI">https://www.youtube.com/watch?v=A0jSTbS7nKI</a></p><p><a href="https://flowdeck.studio/">FlowDeck Studio</a> moves that setup into the session, and each has its own branch, Git worktree, project configuration (scheme, destination, and build configuration), and separate DerivedData folder. The destination is part of the session, and you set it once in the app.</p><p>Here are two sessions on the same project, one per task. One works on the cloud-cover line, the other on the unknown weather codes.</p><p>Session “Cloud Cover in the Humidity Card” runs on Agent A Simulator</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OO4fY0LwSsHV_0U5swNcLA.avif" /></figure><p><strong>Session “Unknown weather codes show as Clear” runs on Agent B Simulator</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cAcxflUQr0dxkzubNhrBZg.avif" /></figure><p>Each session shows the simulator it runs on, so a shared simulator is visible before it causes a bad test run.</p><h3>Conclusion</h3><p>What made this collision easy to miss is that nothing failed. Both builds succeeded, both agents reported success, and the only giveaway was a build number that read <strong>222</strong> instead of <strong>111</strong>.</p><p>A passing build tells you the code compiled. It does not tell you whose code is installed. If you run agents in parallel, you want the work done in roughly half the time, while ensuring that each build runs the correct code and produces the right results.</p><p>Cloning a simulator and carrying its UDID into every prompt was the part I had to repeat for each session, and it is massive, repetitive work. <a href="https://flowdeck.studio/">FlowDeck Studio</a> makes the simulator part of the session setup, so you can get straight to work and focus on the feature rather than on customizing your setup.</p><h3>FAQ</h3><p><strong>Does this only happen with Claude Code?</strong></p><p>It’s safe to say that this impacts all agents that run xcodebuild and xcrun simctl against the same booted simulator. FlowDeck Studio solves it for all the agents it supports: Claude Code, Codex, Grok, Cursor, and anything running on OpenCode.</p><p><strong>Do I need to change my existing project to use FlowDeck?</strong></p><p>No. FlowDeck is fully compatible with Xcode projects, so you can open the same project directly in Xcode whenever you want. You can also add the existing .xcodeproj, .xcworkspace, or folder with File, Add Project, and pick the workspace, scheme, and build configuration. FlowDeck keeps those choices in its own state file, saved per worktree, so each session can use different settings.</p><p><strong>How many simulators can I run at once before my Mac runs out of space?</strong></p><p>It depends mostly on your Mac’s RAM and specs, and then on disk space. On a Mac with 16 GB of RAM, you’ll do fine with 1 to 3 simulators at once, as long as you have enough free disk space for DerivedData. It’s also good practice to free up space by deleting each agent’s simulator clone and build folder once it finishes its task and the work has been merged.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0ee921eb8de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sketch Note: SwiftUI App Structure]]></title>
            <link>https://medium.com/@amarildolucas/sketch-note-swiftui-app-structure-6beefbac67cb?source=rss-fbc33eca6c0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/6beefbac67cb</guid>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[swiftui]]></category>
            <category><![CDATA[sketch]]></category>
            <dc:creator><![CDATA[Amarildo Lucas]]></dc:creator>
            <pubDate>Mon, 20 Mar 2023 18:35:19 GMT</pubDate>
            <atom:updated>2023-03-20T18:35:19.623Z</atom:updated>
            <content:encoded><![CDATA[<p>The SwiftUI <strong>App</strong> <em>protocol</em> looks simpler but is decisive for your <a href="https://developer.apple.com/documentation/swiftui/app-organization">applications’ structure and organization</a>.</p><p>This sketch note shares a general look at the parts involved while implementing your app’s entry point.</p><figure><img alt="Sketch Note: SwiftUI App Structure" src="https://cdn-images-1.medium.com/max/1024/1*esusp2XK8kOh5SoL3cCi_w.jpeg" /></figure><p>Things to take in mind:</p><p><strong>1.</strong> The <strong>App</strong> <em>protocol</em> represents <strong>structure</strong> and <strong>behavior</strong>.</p><p><strong>2. </strong>The <strong>body</strong> is the <strong>content</strong> and can <strong>define scenes</strong>.</p><p><strong>3.</strong> <strong>Scene</strong> acts as the <strong>root view</strong> of the view hierarchy and can be more than one.</p><p><strong>4.</strong> The <strong>@main </strong>initialize and call the <strong>main()</strong> method which <strong>runs your app</strong>.</p><p><strong>5.</strong> The <strong>init()</strong> runs by default.</p><p><strong>6.</strong> You can have <strong>multiple scenes</strong> whose <strong>lifecycles will be managed by the system</strong>.</p><p>I hope this sketch note is helpful to you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6beefbac67cb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CustomPresentationDetent Protocol Implementation in SwiftUI for Modal Presentations]]></title>
            <link>https://medium.com/@amarildolucas/custompresentationdetent-protocol-implementation-in-swiftui-for-modal-presentations-14d8846d5aa9?source=rss-fbc33eca6c0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/14d8846d5aa9</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[macos]]></category>
            <category><![CDATA[swiftui]]></category>
            <category><![CDATA[xcode]]></category>
            <category><![CDATA[swift]]></category>
            <dc:creator><![CDATA[Amarildo Lucas]]></dc:creator>
            <pubDate>Wed, 08 Mar 2023 22:10:58 GMT</pubDate>
            <atom:updated>2023-03-08T22:10:58.703Z</atom:updated>
            <content:encoded><![CDATA[<p>Build more flexible and customized modal view presentations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Zh-QNrmtsrzH1y6dHo6sQ.jpeg" /></figure><blockquote>You can also read this article at my personal blog <a href="https://amarildo.codes/">https://amarildo.codes</a> or in my <a href="https://dev.to/amarildo/custompresentationdetent-protocol-implementation-in-swiftui-for-modal-presentations-o63">Dev account</a>.</blockquote><p>We can <strong>build more flexible and customized</strong> <strong>modal view presentations</strong> thanks to the CustomPresentationDetent<em>protocol</em>. It&#39;s common to use the .sheet modifier when presenting a <strong>modal view</strong>. However, occasionally we may need <strong>more control over the presentation</strong> and the .sheet&#39;s default behavior will not be enough. <strong>This is where</strong>CustomPresentationDetent implementation begins because it enables us to change the presentation&#39;s behavior in the modal view.</p><h3>What you will learn</h3><p>The article provides and outlines a step-by-step guide on how to use CustomPresentationDetent. You will <a href="https://github.com/amarildolucas/CustomPresentationDetent/tree/start-project">download a starter project</a> that explains how to create an extension of PresentationDetent <em>struct</em> and implements CustomPresentationDetent <em>protocol</em>.</p><ol><li>Getting started with the <a href="https://github.com/amarildolucas/CustomPresentationDetent/tree/start-project">starter project</a></li><li>Create PresentationDetent extension</li><li>Implementing CustomPresentationDetent</li></ol><h3>Getting started with the starter project</h3><p>Before we start, <em>clone/fork</em> or <a href="https://github.com/amarildolucas/CustomPresentationDetent/tree/start-project">download</a> the project from the main branch and run the following git commands:</p><pre>git clone git@github.com:amarildolucas/CustomPresentationDetent.git<br>cd CustomPresentationDetent<br>git checkout start-project</pre><ul><li>The main <em>branch</em> contains the final result of the implementation.</li><li>The start-project <em>branch</em> contains the version that you should use to follow through with this article. It is highly recommended that you use the start-project <em>branch</em>.</li></ul><p>The start project contains a ContentView.swift file that:</p><ul><li>Defines a SwiftUI view.</li><li>Contains a button that, when pressed, <strong>toggles the boolean value of</strong> isPresentingSheet and <strong>presents a modal sheet</strong> using the .sheet modifier. The content of the modal sheet is defined in a separate <em>struct</em> called ContentModalSheet. The ContentView <em>struct</em> also conforms to the <em>View</em> <em>protocol</em> and has a body property that returns a VStack containing the button.</li></ul><pre>// ContentView.swift<br><br>struct ContentView {<br>    // Used to toggle and present the modal sheet.<br>    @State private var isPresentingSheet: Bool = false<br>}<br><br>extension ContentView: View {<br>    // Returns a VStack containing the button.<br>    var body: some View {<br>        VStack {<br>            Button(action: presentSheet) {<br>                HStack {<br>                    Image(systemName: &quot;arrow.up&quot;)<br>                    Text(&quot;Present Sheet&quot;)<br>                }<br>                .fontWeight(.semibold)<br>                .foregroundColor(.white)<br>                .padding()<br>                .background(Color.accentColor)<br>                .cornerRadius(8)<br>            }<br>            .sheet(<br>                isPresented: $isPresentingSheet, <br>                content: ContentModalSheet.init<br>            )<br>        }<br>        .padding()<br>    }<br>}<br><br>extension ContentView {<br>    // Toggles the boolean value of isPresentingSheet and presents a modal sheet using the .sheet modifier. <br>    private func presentSheet() {<br>        isPresentingSheet.toggle()<br>    }<br>}</pre><p>The start project also contains another file called ContentModalSheet.swift that contains the <em>View</em> to be presented.</p><ul><li>Defines a view called ContentModalSheet, which is presented as a modal sheet.</li><li>Display the Text &quot;Showing Modal Sheet&quot; and the Button that dismisses the <em>sheet</em> by using the <em>Environment</em>dismiss property and calling the .callAsFunction method.</li></ul><pre>// ContentModalSheet.swiftstruct ContentModalSheet {<br>    @Environment(\\.dismiss) private var dismissModalSheet<br>}<br><br>extension ContentModalSheet: View {<br>    var body: some View {<br>        VStack {<br>            ZStack {<br>                Button(action: dismissModalSheet.callAsFunction) {<br>                    Image(systemName: &quot;xmark&quot;)<br>                }<br>                .fontWeight(.semibold)<br>                .foregroundColor(Color(uiColor: .label))<br>            }<br>            .frame(maxWidth: .infinity, alignment: .leading)<br>            <br>            Spacer()<br>            Text(&quot;Showing Modal Sheet&quot;)<br>                .font(.title3)<br>            Spacer()<br>        }<br>        .padding()<br>    }<br>}</pre><h3>Create PresentationDetent extension</h3><p>A straightforward implementation of the .presentationDetents() method sets the available detents/static properties and methods (<em>snap points</em>) for enclosing <em>sheet</em> presentations in different sizes:</p><ul><li>.large</li><li>.medium</li><li>.custom&lt;D&gt;(D.Type)</li><li>.fraction(CGFloat)</li><li>.height(CGFloat)</li></ul><p>All the above properties and methods return a PresentationDetent instance. Let&#39;s see this in practice in the bellow code by checking the .presentationDetents([.medium, .height(420), .large]) line of code.</p><pre>Button(action: presentSheet) {<br>    HStack {<br>        Image(systemName: &quot;arrow.up&quot;)<br>        Text(&quot;Present Sheet&quot;)<br>    }<br>    .fontWeight(.semibold)<br>    .foregroundColor(.white)<br>    .padding()<br>    .background(Color.accentColor)<br>    .cornerRadius(8)<br>}<br>.sheet(isPresented: $isPresentingSheet) {<br>    ContentModalSheet()<br>        .presentationDetents([.medium, .height(420), .large])<br>}</pre><p>By default, <em>sheets</em> present the PresentationDetent/large detent. If we want to change this behavior we can change this with two lines of code.</p><ol><li>Add a private property named selectDetent of type PresentationDetent and initializes it with a value of .height(64).</li></ol><pre>struct ContentView {<br>    // ...<br>    @State private var selectDetent: PresentationDetent = .height(64)<br>}</pre><p>2. Add the selection parameter to the .presentationDetents method and assign it with $selectDetent variable. The method will return the selected PresentationDetent assigned to this variable.</p><pre>// Button... {}<br>    .sheet(isPresented: $isPresentingSheet) {<br>        ContentModalSheet()<br>            .presentationDetents(<br>                [.height(64), .medium, .height(420), .large],<br>		selection: $selectDetent<br>            )<br>        }</pre><p>To explain a little bit further, a <em>detent</em> is a position at which our modal presentation can <em>snap</em> to. For example, if we have a modal presentation, we can define different <em>detents</em> for displaying the <em>View</em> in different sizes or styles.</p><p>Now that we understood how detents work, let’s extend our <em>detents</em> to a separate file called PresentationDetent+Extension, then add the following code to it.</p><pre>extension PresentationDetent {<br>    static let mediumBottomBar = Self.medium<br>    static let largeBottomBar = Self.large<br>}</pre><p>This code defines two <em>static</em> properties in the PresentationDetent <em>struct</em> and assigns them the original values of the medium and large <em>static</em> properties of the <em>struct</em>. This can be <strong>good if we want to improve the context and nomenclature of our properties</strong> and feature implementations.</p><p>In the next section, we will go further and finally implements our custom property.</p><h3>CustomPresentationDetent implementation</h3><p>To implement CustomPresentationDetent for our modal presentation, we need to create a custom <em>struct</em> that conforms with the <em>protocol</em>. The <em>protocol</em> contains a <em>static</em> method that returns an <em>optional</em> CGFloat.</p><pre>static func height(in context: Context) -&gt; CGFloat?</pre><p>So, let’s create our custom <em>struct</em> and implements the <em>protocol</em>.</p><pre>private struct BottomBarDetent: CustomPresentationDetent {<br>    // Calculates and returns a height based on the context.<br>    static func height(in context: Context) -&gt; CGFloat? {<br>        max(64, context.maxDetentValue * 0.1)<br>    }<br>}</pre><p>Now on top of our <em>extension</em> file, we can add a new property that uses our custom type.</p><pre>extension PresentationDetent {<br>    static let bottom = Self.custom(BottomBarDetent.self)<br>    // ...<br>}</pre><p>And respectively in our existing .presentationDetents method, we can update it to use our new custom properties .bottom, .mediumBottomBar, and .largeBottomBar.</p><pre>// Button... {}<br>    .sheet(isPresented: $isPresentingSheet) {<br>	ContentModalSheet()<br>	    .presentationDetents(<br>		[.bottom, .mediumBottomBar, .largeBottomBar],<br>		selection: $selectDetent<br>	    )<br>	}</pre><h3>Summary</h3><p>This article provided a detailed explanation of how to use CustomPresentationDetent. Now if necessary, create more flexible and customizable modal presentations in your future SwiftUI projects.</p><p><a href="https://github.com/amarildolucas/CustomPresentationDetent/tree/main">You can download the final project here.</a></p><p>If you enjoyed this article, please consider <a href="https://www.buymeacoffee.com/amarildocodes">supporting me by offering me a coffee</a>:</p><ul><li><a href="https://www.buymeacoffee.com/amarildocodes">https://www.buymeacoffee.com/amarildocodes</a></li></ul><p>Thanks for reading, and happy building! :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14d8846d5aa9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tips on remote work before COVID-19]]></title>
            <link>https://medium.com/@amarildolucas/tips-on-remote-work-before-covid-19-5dbe446edce6?source=rss-fbc33eca6c0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/5dbe446edce6</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[remote-work]]></category>
            <category><![CDATA[meetings]]></category>
            <dc:creator><![CDATA[Amarildo Lucas]]></dc:creator>
            <pubDate>Tue, 13 Sep 2022 18:03:53 GMT</pubDate>
            <atom:updated>2022-09-13T18:03:53.494Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Pj_CxvMvF111x4Q37Q312Q.jpeg" /><figcaption>Image from Behance</figcaption></figure><p>Before <em>COVID-19</em>, most of the companies and freelance jobs that I did always start the day with <strong>automated messages on Slack or Basecamp</strong>. These pieces of software are integrated with our core workflows and plenty of other tools. Something that I loved when I was writing technical content for <a href="https://semaphoreci.com/">Semaphore CI</a>, was the fact that even the daily in Basecamp were automated in 3 short questions:</p><ol><li><strong>What did you do yesterday?</strong></li><li><strong>What will you do today?</strong></li><li><strong>What (if anything) is blocking your progress?</strong></li></ol><p>This simple routine puts every teammate in the same loop related to what everyone is currently working on in a concise, compiled message. A mobile developer knows the same related task that a back-end developer is working on, the operations team, support, etc. Of course, this makes a lot of sense depending on the size of the team.</p><p>One of the benefits of this was the fact that <strong>it let all the related team members know the impact of work on each other, and this created engagement in our deliveries and a better outcome.</strong> It also makes the work transparent so that other teammates can quickly help you. That worked so well, and this was until the remote life before <em>COVID-19</em>. These simple activities alone boost our productivity and asynchronous work.</p><p>After that experience of working for some years, it was the same thing that I proposed when doing consulting work for <a href="https://www.usekamba.com/comerciantes">Kamba</a>.</p><figure><img alt="Slack conversations" src="https://cdn-images-1.medium.com/proxy/1*f5AcrLYbN8Ylp5lZ9mx3Qg.png" /><figcaption>Slack conversations</figcaption></figure><h4>Take time to share knowledge</h4><p>For us, this didn’t work in the 1-for-all way, where a single person tries to share knowledge and suggestions to help others.</p><p>For us,<strong> it is an all-for-all relationship</strong>. Even if you are an expert in that field, we all want to listen to each other and the best ideas come to life.</p><p>Take the time to teach and share knowledge with employees. This will free up your time to focus on your work, in the confidence that your employees will resolve any issues without the need of your input.</p><figure><img alt="Code review" src="https://cdn-images-1.medium.com/proxy/1*XgRWvHE8Aajl-DQx8PBqcQ.jpeg" /><figcaption>Code review</figcaption></figure><h4>Delegate, but not just delegate</h4><p>If you’ve ever worked in a company, you know what it’s like to be given multiple tasks and survive.</p><p>Receive an email and turn around.</p><p>One spec and turn around…</p><p>Mentoring is not something that is just in fashion. I hate how this practice has been turned gourmet like a pyramid to make more money by mentoring alone.</p><p>But we still have the good ones, the “<em>give and take</em>” ones.</p><blockquote><strong>Delegating with mentoring lets your employees know that they matter and that they are supported, and it helps them feel like they own the company, own the tasks, and account for any mistakes or successes, a sense of belonging.</strong></blockquote><h4>The time of difficult conversation</h4><p>In small teams, we always work closely together. This close relationship can make it difficult to initiate difficult conversations or provide feedback.</p><p>Some employees shy away from conversations that need to appear negative or even politely “<em>scold</em>”. Others do not so. They dump all the blame on the employee in a rather annoying way, without being in any way constructive. This is why one-on-one meetings work better.</p><p><strong>Pulling the good and the bad out of the person in a polite and most importantly isolated and empathetic way.</strong></p><p>Holding a half-hour or even 15-minute meeting with each employee every week or month helped us a lot. We even hold a small internal meet-up every day at a fixed time. A recurring event is marked on our calendars.</p><figure><img alt="Google Meet Notification" src="https://cdn-images-1.medium.com/proxy/1*zHasyYq6y2Hj1weAa7_8lA.png" /><figcaption>Google Meet Notification</figcaption></figure><p>Do not join the meeting or conversation because you were marked or invited. Set an agenda and participate. We have a general and not a systemic script, we imagine a circle, we define a script, and we all talk. Without having to name anyone, if you want to speak, you will be the next one, but everyone speaks. No one leaves without speaking, even if it means repeating what was said or worked on yesterday.</p><p><em>Jonathan Raymond</em> outlines five types of behaviors that managers can safely discuss with their employees:</p><blockquote><strong>1. Time management.</strong></blockquote><blockquote><strong>2. Responsive communication.</strong></blockquote><blockquote><strong>3. Take ownership of an error.</strong></blockquote><blockquote><strong>4. Lack of skills.</strong></blockquote><blockquote><strong>5. Not taking enough risks or taking too many.</strong></blockquote><p><strong>You have to know what’s going on with your team. Ever!</strong></p><h4>One-on-one</h4><p>One-on-one meetings are great for sharing about how you are performing, as well as for more difficult conversations like resolving strategic issues or solving problems.</p><p><strong>By avoiding sharing the performance of each employee in public, it keeps the work flowing to others, away from comparisons, thus being able to check productivity, and morale and help teams, getting to know them better and better.</strong> I also learned in these meetings to try to make the employee feel committed and valued and open to speak as he desires.</p><p>But they are not just for the employee, I also take advantage of them to request and attempt to understand “about me” and ask questions that helped me improve in general.</p><p><strong>In my day-to-day work, I learned to establish that my role is to help others fill in the gaps between where they are, and where they could be so that we are always where we need to be.</strong></p><p>I have learned a lot from them.</p><p>I also still contribute a lot with programming and code. :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5dbe446edce6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Navigation App Architecture on Apple eyes]]></title>
            <link>https://medium.com/@amarildolucas/navigation-app-architecture-on-apple-eyes-e4ee04d114b?source=rss-fbc33eca6c0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4ee04d114b</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[xcode]]></category>
            <category><![CDATA[swiftui]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Amarildo Lucas]]></dc:creator>
            <pubDate>Sat, 14 May 2022 20:44:13 GMT</pubDate>
            <atom:updated>2022-05-14T20:44:13.933Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>A visual on Apple human interface guidelines for navigation on iOS.</strong></p><p>If you are like me and love learning by seeing visuals or flows about some programming or UI/UX topics, I hope you enjoy this mind node that I created about how the Navigation should be on iOS on Apple eyes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hdI4acy5oB8XkQRLqHtLEw.png" /><figcaption>A visual on Apple human interface guidelines for navigation on iOS created by Amarildo Lucas</figcaption></figure><p>You can download it and use it as your need. 🚀</p><h4>References</h4><ul><li><a href="https://amarildo.codes/navigation-app-architecture-on-apple-eyes">https://amarildo.codes/navigation-app-architecture-on-apple-eyes</a></li><li><a href="https://developer.apple.com/design/human-interface-guidelines/ios/app-architecture/navigation/">https://developer.apple.com/design/human-interface-guidelines/ios/app-architecture/navigation/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4ee04d114b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Apresentando Kamba | Netkuya: uma nova experiência para recarregar a sua Internet]]></title>
            <link>https://medium.com/kamba-blog/apresentando-kamba-netkuya-uma-nova-experi%C3%AAncia-para-recarregar-a-sua-internet-134ac9e45424?source=rss-fbc33eca6c0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/134ac9e45424</guid>
            <category><![CDATA[usekamba]]></category>
            <category><![CDATA[carteira-digital]]></category>
            <category><![CDATA[fintech]]></category>
            <dc:creator><![CDATA[Amarildo Lucas]]></dc:creator>
            <pubDate>Tue, 27 Aug 2019 12:54:20 GMT</pubDate>
            <atom:updated>2019-08-27T13:28:12.714Z</atom:updated>
            <content:encoded><![CDATA[<p>Em menos de 10 segundos, seu pagamento online, recibo electrónico, recorrência e automação!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/954/1*ogXvijIoihh94e6m8FRaxg.png" /></figure><p><strong>Hoje estamos a lançar o serviço Netkuya na sua Carteira.</strong> Com o serviço Netkuya você poderá realizar o pagamento do seu plano de Internet através do telemóvel. Mas esta não é a grande novidade!</p><p>Como sempre, ao digitalizarmos os nossos serviços, tentamos trazer experiências diferentes das do mercado tradicional. Não é diferente com este novo recurso.</p><p>As vantagens em recarregar a sua Internet Netkuya com a Kamba reside em pequenos detalhes que fazem toda diferença para os antenados da transformação digital.</p><ul><li><strong>Menos de 10 segundos para adquirir o plano.</strong> Sério, você precisa experimentar para tirar suas próprias conclusões e benefícios.</li><li>Recibo electrónico pós compra. <strong>O código de recarga é enviado para seu e-mail através de um recibo electrónico personalizado, </strong>juntamente com as instruções de como finalizar sua recarga no Painel Utilizador NetOne.</li><li><strong>Lembretes de pagamentos 10 à 5 dias antes do seu plano atual de internet terminar.</strong> Assim você fica despreocupado com calcular datas ou perder o sinal de internet de repente.</li><li>Ao <strong>finalizar o pagamento da sua recarga Netkuya</strong> através da carteira <strong>você é elegível de descontos</strong> quando há uma campanha disponível.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/324/1*k-u00sTjnYa_sBQpW4573w.png" /><figcaption>Toque em Recarregar Netkuya para para ver a lista de planos mensais disponíveis para sua carteira.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/253/1*GYOrG1wjXGILGwJ4QASNgA.png" /><figcaption>Selecione o plano com o valor que deseja aderir.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/253/1*8oWXvk34eRIkD6Qvhf7zEw.png" /><figcaption>PAGUE! Toque em Pagar para finalizar o pagamento. Um recibo electrónico será enviado para o seu e-mail. Em caso de dúvidas antes de realizar o pagamento, toque em Ajuda na barra de navegação para compreender melhor como funciona o carregamento digital.</figcaption></figure><h3>A seguir</h3><p>Tudo na Kamba é rápido e iterativo, por isso você está em boas mão se deseja manter o seu aplicativo sempre atualizado. Lançamos atualizações toda semana para iOS (iPhones) e Android. Fique atento para as melhorias neste recurso, e se sentir falta de algo, as sugestões são bem-vindas. Entre em contato com a nossa equipa em <strong>suporte@usekamba.com</strong></p><h4>Faça o download desta atualização na <a href="https://apps.apple.com/app/kamba-pagamentos-sem-cart%C3%A3o/id1268906716">App Store</a> ou <a href="https://play.google.com/store/apps/details?id=com.usekamba.kamba.kamba">Google Play</a>:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/270/0*-RBZFr5euB7WpifX.png" /><figcaption><a href="https://apps.apple.com/app/kamba-pagamentos-sem-cart%C3%A3o/id1268906716">https://apps.apple.com/app/kamba-pagamentos-sem-cartão/id1268906716</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/270/0*qEquuuTTMFX0_G3x.png" /><figcaption><a href="https://play.google.com/store/apps/details?id=com.usekamba.kamba.kamba">https://play.google.com/store/apps/details?id=com.usekamba.kamba.kamba</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=134ac9e45424" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kamba-blog/apresentando-kamba-netkuya-uma-nova-experi%C3%AAncia-para-recarregar-a-sua-internet-134ac9e45424">Apresentando Kamba | Netkuya: uma nova experiência para recarregar a sua Internet</a> was originally published in <a href="https://medium.com/kamba-blog">Kamba Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pagamento com sensor biométrico? AQUI!]]></title>
            <link>https://medium.com/kamba-blog/pagamento-com-sensor-biom%C3%A9trico-aqui-18848ffb2c02?source=rss-fbc33eca6c0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/18848ffb2c02</guid>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[pagamento]]></category>
            <category><![CDATA[mobile-wallet-app]]></category>
            <category><![CDATA[carteira]]></category>
            <dc:creator><![CDATA[Amarildo Lucas]]></dc:creator>
            <pubDate>Tue, 12 Mar 2019 12:41:16 GMT</pubDate>
            <atom:updated>2019-03-12T12:44:07.397Z</atom:updated>
            <content:encoded><![CDATA[<p>Segurança e privacidade em seus pagamentos com o <a href="https://www.usekamba.com/">Kamba</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KE0cm4pESMxtUsKUf7xQdw.png" /><figcaption>Imagem do Google Images</figcaption></figure><p><strong>O Touch ID é um </strong><a href="https://pt.wikipedia.org/wiki/Digital"><strong>sensor biométrico</strong></a><strong> desenvolvido pela </strong><a href="https://pt.wikipedia.org/wiki/Apple_Inc."><strong>Apple Inc.</strong></a></p><p>Através deste sensor podemos realizar compras com segurança nas lojas virtuais como <a href="https://pt.wikipedia.org/wiki/ITunes">iTunes</a>, <a href="https://pt.wikipedia.org/wiki/App_Store_(iOS)">App Store</a>, compras internas em aplicativos como a sua <a href="https://www.usekamba.com/">carteira Kamba</a>, proteger os teus dados em aplicativos como o Google Drive e entre outros, desbloquear a tela do seu dispositivo sem a necessidade de digitar sua respetiva senha, apenas encostando a impressão digital no sensor.</p><p>Como dito acima, é possível identificar logo que ele foi <strong>desenvolvido pensando na segurança e privacidade dos usuários.</strong></p><p>Mesmo a própria Apple que desenvolveu o sensor não possui os dados recebidos pelo Touch ID, pois os mesmos são armazenados no processador e não são enviados aos servidores da Apple.</p><p><strong>Na sua </strong><a href="https://www.usekamba.com/"><strong>carteira Kamba</strong></a><strong> você tem a opção de pagar com a sua impressão digital para proteger as suas transações.</strong></p><p>Pense na sua <a href="https://www.usekamba.com/">carteira</a>. Apesar de ela estar segura pelos nossos servidores, você gostaria de uma ação tão sensível como pagamentos estar aberta para todos com acesso ao seu telefone? Provavelmente não. Mas tal como desbloquear o telefone com uma senha e depois digitar outra senha para acessar algo é chato, colocar simplesmente o seu dedo no sensor automatiza todo esse processo. Outros aplicativos enormes na indústria usam a mesma prática para autorizar transações. Tal como o Venmo ou o PayPal. Na Kamba também fazemos o mesmo.</p><p><strong>Agora vamos aprender a ativar este recurso na sua carteira.</strong></p><ol><li>Aceda o painel <strong>Carteira</strong></li><li>Toque em <strong>Active o PIN de Segurança</strong></li><li>Toque no botão <strong>Activar Touch ID</strong></li><li><strong>Informe a senha da sua carteira</strong>. A mesma que usa no Login.</li><li>E pronto! O <strong>Touch ID está ativado</strong> em sua carteira.</li><li>Pague alguém e verificará que <strong>de agora em diante será solicitado a autorização com a impressão digital.</strong></li></ol><p>As imagens abaixo ilustram os passos acima da esquerda para a direita, de cima para baixo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*J6L5euY7gsDs7Xu4NIgEsw@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*lO9xhjJ1TBpUk4jtEn3E2A@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*eUk_Bei1xpxgYm-KmqKngg@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*6XHR0FiCQvPajML-ht22HA@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*ijCP_iew7KECa3j_X9uMfw@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*JjkjBrpfI2QgJ0YlCq0WTg@2x.jpeg" /></figure><p><a href="https://www.usekamba.com/">Se você quer uma forma prática e segura de fazer e receber seus pagamentos no seu telefone, significaria o mundo para mim se você escolhesse usar o Kamba como a carteira do seu dia a dia.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18848ffb2c02" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kamba-blog/pagamento-com-sensor-biom%C3%A9trico-aqui-18848ffb2c02">Pagamento com sensor biométrico? AQUI!</a> was originally published in <a href="https://medium.com/kamba-blog">Kamba Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Descubra como o Kamba pode ajudar em doações ou causas sociais!]]></title>
            <link>https://medium.com/kamba-blog/descubra-como-o-kamba-pode-ajudar-em-doa%C3%A7%C3%B5es-ou-causas-sociais-1064bc2a3c92?source=rss-fbc33eca6c0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1064bc2a3c92</guid>
            <category><![CDATA[wallet]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[pagamento]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Amarildo Lucas]]></dc:creator>
            <pubDate>Thu, 21 Feb 2019 16:22:02 GMT</pubDate>
            <atom:updated>2019-02-21T16:36:34.519Z</atom:updated>
            <content:encoded><![CDATA[<p>Imprima seu código QR ou compartilhe seu número de telemóvel para pagamento…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d_C5VA4Cqk0iNWTkGOuKvg.png" /></figure><p>Você provavelmente já sabe que <a href="https://www.usekamba.com/"><strong>com a sua carteira pode pagar por serviços como recarga de telemóvel Unitel ou Movicel, recarga/subscrição Zap ou Dstv para a sua televisão</strong></a> automaticamente todo mês.</p><p>Nós até mesmo compartilhamos um vídeo sobre isso.</p><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=facebook&amp;url=https%3A//www.facebook.com/usekamba/videos/300708580584560/&amp;image=https%3A//i.embed.ly/1/image%3Furl%3Dhttps%253A%252F%252Fscontent-iad3-1.xx.fbcdn.net%252Fv%252Ft15.13418-10%252F49759262_384778022286257_2778107824851386368_n.jpg%253F_nc_cat%253D109%2526_nc_ht%253Dscontent-iad3-1.xx%2526oh%253D008d144210a9d6d4585a605449e7ba4b%2526oe%253D5CE53FE2%26key%3Da19fcc184b9711e1b4764040d3dc5c07" width="600" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/8d14f6e80f95f345b678a383aa2242c6/href">https://medium.com/media/8d14f6e80f95f345b678a383aa2242c6/href</a></iframe><p>Mas o contexto de utilização do Kamba é enorme quanto a criatividade em sua mente.</p><p>Você <a href="https://www.usekamba.com/"><strong>poderia estar a usar a carteira como forma de receber pagamentos em um evento, em uma loja online, em uma loja física, etc.</strong></a>, tudo depende da sua motivação e do seu caso de uso.</p><p>Mas o que eu gostaria de compartilhar hoje, é como <a href="https://www.usekamba.com/"><strong>a carteira poderia ser usada para causas sociais ou doações</strong></a>, e como esta seria a maneira mais rápida para você angariar dinheiro dos seus simpatizantes online</p><p>Novamente os casos variam… Então irei de forma singular exemplificar apenas um caso. Outro dia me deparei com algumas imagens/post no twitter :</p><h3>Ronilson Ferreira on Twitter</h3><p>Hoje vi esse jovem, senti-me comovido e decidi partilhar. Ele quer ser arquitecto, mas não tem condições para tal. Vamos ajudar a espalhar, quem sabe chegue a alguém que o pode ajudar. O contacto dele está nas fotos.</p><p>Quando eu vi estas imagens eu imaginei, uau!, tem como ajudar este jovem convenientemente. Tem o número escrito no papel sobre a madeira em seu trabalho. Mas depois pensei novamente, uau!, <a href="https://www.usekamba.com/"><strong>este papel poderia ser um código QR impresso e qualquer pessoa seguramente poderia pagar</strong></a> na rua. E continuei a pensar, uau!, <a href="https://www.usekamba.com/"><strong>através do número do telemóvel também seria possível pagar ele pela carteira</strong></a>.</p><p>As ONGs, organizações não governamentais possuem um enorme papel nestas questões, mas elas não estão em todas as causas, há diversas pendências, então, como cidadão eu avaliei o post do rapaz e repercussão de como <strong>seria mais simplificado de forma digital termos algum número/contato no post, um QR nas imagens ou link para pagamento em que qualquer pessoa poderia contribuir.</strong></p><p><strong>Ter a carteira aqui é mais simplificado e rápido que os meios tradicionais.</strong></p><p>As curtidas, os retweets e comentários neste post não irão doar dinheiro ao jovem. O processo de doação não é simples e pode ser dificultado quanto mais variáveis são adicionadas à ele. Sair de casa para banco, combustível, anotar dados bancários, não cair em golpes online, número da conta bancária compartilhado publicamente, agências bancárias e diversas informações burocráticas bloqueiam diversos doadores, os quais por mais que sentidos pela causa, acabam colocando suas prioridades pessoais em primeiro.</p><h3>Como este quadro mudaria?</h3><p>Usar a carteira de pagamentos Kamba para doar facilmente em apenas alguns toques no ecrã do telemóvel, ao procurar pelo contato telefónico ou fazer a leitura do código QR impresso na rua.</p><p><strong>O aplicativo oferece diversas modalidades de pagamento para diversos contextos</strong>. Neste caso eu recomendaria duas formas de pagamento.</p><p>1. Na sua carteira na tela inicial o usuário toca em Pagar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*5_GwSK4x4R2N0bd2uWDWNA@2x.jpeg" /></figure><p>2. Na tela Pagar, o usuário pesquisa e encontra a entidade que pretende pagar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*kS0g1OXYIymIlsOc8yw2Qg@2x.jpeg" /></figure><p>3. Informa o valor que pretende doar e finaliza a operação.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*jtDXbe-M9UaM1V5POQlqyQ@2x.jpeg" /></figure><p><strong>Nota:</strong> No passo 1 o usuário também poderia ler um código QR de pagamento na rua que encontraria esta entidade em alguns segundos e mostraria logo o passo 3 (Informa o valor que pretende doar e finaliza a operação ao clicar em pagar).</p><p>Com isso <strong>angariamos dinheiro digitalmente na internet através de uma solução conveniente, eliminando assim diversas barreiras no processo do doador </strong>que por diversas prioridades pessoais poderia não finalizar uma doação.</p><p>Você tem visto diversas causas ou jovens talentosos que precisem de ajuda? <a href="https://www.usekamba.com/"><strong>Recomende o Kamba como forma de pagamento</strong></a><strong>, explique sobre o processo e ajude se for possível a entrar em contato connosco: suporte@usekamba.com</strong></p><p>Assim juntos conscientizamos, educamos, transformamos e o melhor, ajudamos a acelerar o crescimento destas causas para angariar algum valor e facilitando os doares.</p><p><a href="https://www.usekamba.com/"><strong>A carteira de pagamentos está disponível na App Store para iPhones e Google Play para Android. Transforme seus pagamentos. CLICA AQUI!</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1064bc2a3c92" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kamba-blog/descubra-como-o-kamba-pode-ajudar-em-doa%C3%A7%C3%B5es-ou-causas-sociais-1064bc2a3c92">Descubra como o Kamba pode ajudar em doações ou causas sociais!</a> was originally published in <a href="https://medium.com/kamba-blog">Kamba Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reuniões “1/1 ou mais”]]></title>
            <link>https://medium.com/kamba-blog/reuni%C3%B5es-1-1-ou-mais-298159ff83e4?source=rss-fbc33eca6c0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/298159ff83e4</guid>
            <category><![CDATA[trabalho-remoto]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[trabalho]]></category>
            <dc:creator><![CDATA[Amarildo Lucas]]></dc:creator>
            <pubDate>Wed, 20 Feb 2019 12:12:35 GMT</pubDate>
            <atom:updated>2019-02-20T12:16:34.859Z</atom:updated>
            <content:encoded><![CDATA[<p>Na <a href="https://www.usekamba.com/">Kamba</a> sempre começamos o nosso dia de trabalho com uma mensagem automática no Slack.</p><p>Este pequeno hábito diário coloca todos os nossos colaboradores no mapa em relação ao que eles estão a trabalhar no momento. Um desenvolvedor Mobile sabe o que um desenvolvedor Back-end está a trabalhar, o Suporte, a equipa OP, etc…, como a nossa equipa é pequena, dessa forma conseguimos reconhecer o impacto do trabalho de todos e o engajamento em relação às entregas e resultados. Então isto funciona &quot;totalmente bem&quot;!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lrk-B3hRMZ6R5L-3SgjmMw.png" /></figure><p>Outras poucas ideias que pretendo compartilhar para equipas pequenas continuam abaixo e se você tiver gerindo alguma gostaria de ouvir os seus pensamentos e práticas também. Principalmente se for uma equipa remota/distribuída.</p><h3>Levar algum tempo compartilhando conhecimento com os colaboradores</h3><p>Para nós, isso não funciona na forma 1 para todos, onde uma única pessoa tenta compartilhar conhecimentos e sugestões para ajudar os outros.</p><p>Para nós é uma relação todos para todos. Ainda que você seja uma pessoa especializada naquela área, todos queremos ouvir uns aos outros e as melhores ideias ganham vida.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*T01yx6m6WF6Tz-ZPu_1f2w.jpeg" /></figure><p>Levar um tempo treinando e compartilhando conhecimento treina os colaboradores em geral e libera seu tempo para se focar em seu próprio trabalho, na confiança de que seus colaboradores irão resolver quaisquer problemas mais tarde.</p><h3>Delegar, mas não delegar apenas</h3><p>Se você já trabalhou em alguma empresa sabe o que é as vezes receber várias tarefas e se virar.</p><p>Receber um email e se virar.</p><p>Uma especificação e se virar…</p><p>Mentoria não é algo que está na moda apenas. Eu na verdade odeio o quão esta prática vem sendo <em>gourmetizada</em> como uma pirâmide para ganhar mais dinheiro pela mentoria apenas.</p><p>Mas ainda assim temos os bons, os que &quot;dão e recebem&quot;.</p><p>Delegar com mentoria deixa os seus colaboradores saberem que importam, que são apoiados, e isso os ajuda a sentirem-se donos da empresa, donos das tarefas, e responsáveis por quaisquer erros ou sucesso, um censo de pertencer ao meio.</p><h3>A hora da conversa difícil</h3><p>Em equipas pequenas trabalhamos sempre todos de perto. Esta relação tão próxima pode dificultar iniciar conversas difíceis ou prover feedback.</p><p>Alguns colaboradores fogem as conversas que necessitam de parecer negativos ou mesmo educadamente “dar uma bronca”. Outros nem por isso. Despejam no colaborador toda culpa de maneira bastante aborrecida, sem ser de algum modo construtivo. Por este motivo é que reuniões individuais funcionam melhor.</p><p>Puxar o bom e o mau da pessoa de maneira educada e mais importante isolada e com empatia.</p><p>Realizar uma reunião de meia hora ou até mesmo 15 minutos com cada colaborador todas semanas ou meses nos ajuda muito. Na verdade nós realizamos até todos dias também, um pequeno <em>meetup</em> interno em horário fixo. Um evento recorrente marcado em nossos calendários.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0NzuKNQwxwbjdvG4XcBB5w.png" /></figure><p>Defina uma agenda. Não entre na reunião ou conversa porque está marcado apenas. Defina um roteiro e siga. Nós temos um roteiro geral e nem um pouco sistêmico, imaginamos uma roda, definimos um roteiro e todos falamos. Sem precisar nomear ninguém, se desejar falar será o próximo, mas todos falam, ninguém sai sem falar, ainda que seja repetir o mesmo que se disse ou trabalhou ontem.</p><p>Jonathan Raymond descreve cinco tipos de comportamentos que os gestores podem discutir com segurança com seus colaboradores:</p><ul><li>Gerenciamento de tempo</li><li>Comunicação responsiva</li><li>Tomar posse de um erro</li><li>Falta de competências</li><li>Não correr riscos suficientes ou levar muitos</li></ul><p>Você tem que saber o que está acontecendo com sua equipa. Sempre!</p><h3>1/1</h3><p>As reuniões individuais são ótimas para compartilhar sobre performance ou desempenho, e também para conversas mais difíceis como resolver questões estratégicas ou resolver problemas.</p><p>Ao evitar compartilhar em público o desempenho de cada colaborador, mantém o trabalho fluindo para os outros, longe de comparações, podendo assim verificar a produtividade, o moral e ajudar as equipas, conhecendo-as cada vez melhor. Eu aprendi ainda à nestas reuniões tentar fazer o colaborador se sentir comprometido e valorizado.</p><p>Mas elas não servem apenas para o colaborador, eu também aproveito as mesmas para solicitar e tentar entender &quot;sobre mim” e fazer perguntas que me ajudem a melhorar à equipa no geral.</p><p>…</p><p>No meu dia à dia trabalhando na Kamba, eu aprendi a estabelecer que meu papel é ajudar a equipa a preencher os buracos entre onde estão e onde poderiam estar, para estarmos sempre onde realmente precisamos estar.</p><p>Tenho aprendido bastante com eles.</p><p>Eu também ainda contribuo com bastante programação e código. :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lKBCVBFcJhta640NIvyNDA.jpeg" /><figcaption>Rawpixel no Unsplash</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=298159ff83e4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kamba-blog/reuni%C3%B5es-1-1-ou-mais-298159ff83e4">Reuniões “1/1 ou mais”</a> was originally published in <a href="https://medium.com/kamba-blog">Kamba Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2018!]]></title>
            <link>https://medium.com/kamba-blog/2018-bf7e7f4ed089?source=rss-fbc33eca6c0e------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf7e7f4ed089</guid>
            <category><![CDATA[2018-in-review]]></category>
            <category><![CDATA[carteirapagamentos]]></category>
            <category><![CDATA[2018]]></category>
            <category><![CDATA[usekamba]]></category>
            <category><![CDATA[fintech]]></category>
            <dc:creator><![CDATA[Amarildo Lucas]]></dc:creator>
            <pubDate>Mon, 31 Dec 2018 15:23:06 GMT</pubDate>
            <atom:updated>2018-12-31T15:25:56.044Z</atom:updated>
            <content:encoded><![CDATA[<p>Obrigado a toda nossa comunidade… VISA, YCStartupSchool Advisor Track, Hot Fintech Ventures, Angel fair Africa e mais.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HqbB7B5SJsks1bCjNYe5DQ.png" /></figure><p><strong>Obrigado a toda nossa comunidade!</strong></p><p>Este ano nossa missão de criar experiências descomplicadas de pagamentos ao digitalizar e transformar serviços tradicionais tornou-se mais sólida.</p><p><strong>Nos bastidores trabalhamos em diversas soluções a serem lançadas a partir de Janeiro de 2019 em diante. Estamos muito empolgados por isso!</strong></p><p>Nossa equipa cresceu de 3 para 9 membros nestes últimos meses e continuamos a recrutar desenvolvedores com o objetivo de acelerar nosso desenvolvimento e transformar experiências tradicionais para digital com 10x de qualidade.</p><p><strong>A inovação é muito importante para nós.</strong></p><p>Nossa comunidade também vem crescendo mesmo sem um marketing ativo ou canal de aquisição…</p><p>Criamos um aplicativo e uma comunidade brilhante que se importa com sua experiência dentro do aplicativo e providencia bastante feedback! Desde consumidores, revendedores e comerciantes.</p><p>Estamos com um ótimo número de revendedores e comerciantes na fila de espera para usar nossas soluções. Liberarmos o beta para 32 revendedores e 15 comerciantes apenas por agora para testarmos, observarmos e aprendermos com suas dificuldades até lançarmos oficialmente.</p><p><strong>…</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*K8KbhHfTOofnauSOlqQpeg.jpeg" /></figure><h3>Angola Empreende on Twitter</h3><p>@usekamba, a Startup Angolana dedicada à pagamentos electrónicos via uma carteira virtual foi recentemente aceite para fazer parte do Programa Visa Ready mPOS (aceitar pagamentos sem contacto, de tarja magnética ou chip através de um aplicativo em um dispositivo móvel) #Empreende</p><p>Após um processo de avaliação rigoroso nossa solução faz parte do Visa Ready para MPOS e estamos a adaptar novos recursos face à essa realidade que mudarão o cenário de pagamentos da carteira atual.</p><p>Para uma Startup como a nossa isso signfica realmente muito uma vez que o processo é bastante cheio de requisitos, o que leva ainda mais a <strong>agradecer nossos desenvolvedores e equipa geral pelos esforços em atingir sempre um padrão de qualidade no desenvolvimento de soluções em nossa carteira.</strong></p><p>…</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FyhFcdPSNZhw%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DyhFcdPSNZhw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FyhFcdPSNZhw%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/cc7ff632443b1b57174f0a6f3eac912a/href">https://medium.com/media/cc7ff632443b1b57174f0a6f3eac912a/href</a></iframe><h3>Angel Fair Africa on Twitter</h3><p>Pitch Day 2: USEKAMBA Founder: Amarildo Lucas/Airton Lucas/ Alexandre Juca Email: airton@usekamba.com Website: https://t.co/f2T7Kx6Xzt Based in: Angola Industry: Fintech Founded: 4/13/18 Current funding status: Self funded</p><p>Participamos do Angel Fair Africa 2018 no final do mês de novembro em Moçambique, onde contamos um pouco da nossa história e sobre as dificuldades dos pagamentos móveis em Angola. Foi também uma ótima ocasião para conhecer outros ambientes e ecossistema de Startup.</p><p><strong>…</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*2ArbmaROUudpgP08hGL9JA.png" /></figure><p>Fomos selecionados pela YCombinator para o StartupSchool 2018. Também fomos escolhidos para o Advisor Track que só admitiu ~25% das empresas participantes 15K. Pessoalmente descrevo como a melhor experiência que pude ter este ano. Nosso mentor, outros companheiros de Startups e diversos fundadores compartilharam e orientaram bastante sobre diversas dificuldades e ideias em relação aos fundadores de Startups aprovados para o programa.</p><p><strong>…</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O9SzeWYK-SrYG5eZ_plrOQ.jpeg" /></figure><h3>Briter on Twitter</h3><p>@zedalm @ubuneka_africa @vasoliv @TUPUCA_LDA @sacyjosecarlos @ericksonmvezi @WilsonGangaJr @cfkappa @locristiano_ @deya_mais @BantuMakers @usekamba Hello @zedalm, thanks for the feedback. We included @usekamba in our #InnovationMaps (picture below). Let us know if you need any more information.</p><p>Vale compartilhar também algumas notícias sobre nós que atravessaram as fronteiras angolanas:</p><ul><li><a href="https://www.howwemadeitinafrica.com/startup-snapshot-angolan-payments-company-getting-in-early-ahead-of-the-big-banks/61326/">https://www.howwemadeitinafrica.com/startup-snapshot-angolan-payments-company-getting-in-early-ahead-of-the-big-banks/61326/</a></li><li><a href="http://disrupt-africa.com/2018/06/angolan-startup-claims-countrys-first-mobile-wallet/">http://disrupt-africa.com/2018/06/angolan-startup-claims-countrys-first-mobile-wallet/</a></li></ul><h3>Olhando para a frente, para 2019!</h3><p>Apelidamos 2018 como o ano de arrumação da casa. Pois, melhoramos bastante nossos processos internos, crescemos nossa equipa de desenvolvimento e captamos mais recursos para tornar possível desenvolver novas soluções e então focar em nosso lançamento oficialmente em 2019.</p><p>Pessoalmente estou empolgado em como nos preocupamos com todos aspectos nos fluxos de pagamento e outras funcionalidades. Até os aspectos mais simples.</p><p>2019 virá com diversos novos lançamentos de recursos na carteira, novos intercâmbios e parcerias, deverá ser um ano empolgante para a Kamba e para o ecossistema de Startups angolanas como um todo!</p><p>Se pudéssemos resumir nossos pensamentos para 2019 e o que temos finalizado nestes últimos meses para lançarmos em uma frase, simplesmente seria…</p><p><strong>2019! Só vem!!!</strong></p><p><strong>…</strong></p><p>Faça o download do aplicativo <strong>Kamba #1 Carteira de Pagamentos </strong>na <a href="https://play.google.com/store/apps/details?id=com.usekamba.kamba.kamba">Google Play Store</a> ou <a href="https://itunes.apple.com/ao/app/kamba-pagamentos-sem-cart%C3%A3o/id1268906716">Apple App Store</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf7e7f4ed089" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kamba-blog/2018-bf7e7f4ed089">2018!</a> was originally published in <a href="https://medium.com/kamba-blog">Kamba Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>