Twitter | Search | |
Bruno Rocha
iOS at , writing about Swift's innards at
149
Tweets
50
Following
740
Followers
Tweets
Bruno Rocha May 25
Replying to @peres
I failed Uber last year but I don't even know why since the norm now is to ghost everyone
Reply Retweet Like
Bruno Rocha May 23
Replying to @Javi @AndyyHope
DAMN
Reply Retweet Like
Bruno Rocha May 22
Remember autoreleasepool? Having dealt with memory intensive code I wondered if it could still be used in Swift, so I went to find out! ❓What's autoreleasepool? 🤔Why does it exist? 😕Can it help you in Swift? Check it out:
Reply Retweet Like
Bruno Rocha May 21
Replying to @rockthebruno
Also I'm going to bring SwiftRocks stickers
Reply Retweet Like
Bruno Rocha May 21
🇧🇷 I'll be speaking at TDC São Paulo 2019 about "Avoiding Release Anxiety: Building Stress-Free iOS Apps". See you there!
Reply Retweet Like
Bruno Rocha May 20
danger-SwiftInfo and SwiftInfo 2.3.1 are officially out! You can now extract info from specific pull requests.
Reply Retweet Like
Bruno Rocha May 19
I made a Danger plugin to run SwiftInfo in PRs! Once I solve an issue with CircleCI you'll be able to extract info from individual pull requests to see how they will change your project.
Reply Retweet Like
Bruno Rocha May 10
Replying to @rockthebruno
If weak self was used, an abrupt deinit of this class would prevent `save()` from being called. If calling `save()` here is important, then using strong self would be a better option. The closure would keep the class alive until it executes, deiniting only after calling `save()`.
Reply Retweet Like
Bruno Rocha May 10
It's widely taught that you should use [weak self] in closures to avoid cycles, but I think there's a lack of content on how to identify these cycles. In the following example, the closure retains `self`, but `self` doesn't retain the closure or the queue. No leaks here.
Reply Retweet Like
Bruno Rocha May 7
The second part of "Avoiding Release Anxiety" is out: "On the importance of creating a code Style Guide"! I shared a bit of my experience working with huge teams and how having an unique style guide helped us improve and scale the project.
Reply Retweet Like
Bruno Rocha May 3
Thanks to Cihat Gündüz, you can now install SwiftInfo with Homebrew! It's super awesome when you guys submit PRs for the things you want! 😍
Reply Retweet Like
Bruno Rocha May 2
Submitted talks for a few CFPs lately. Crazy how much iOS-related events we have now, just a few years ago you had way less options! Happy to see how much the community grew.
Reply Retweet Like
Bruno Rocha Apr 24
Replying to @natanrolnik
Ultra galaxy brain: utilize time travel to make sure the bug never happened in first place
Reply Retweet Like
Bruno Rocha Apr 24
I'm so happy today. Saw that someone opened an issue in one of my libs, but instead of mindlessly complaining they also opened a PR with the fix 😍
Reply Retweet Like
Bruno Rocha Apr 20
SwiftInfo 2.1.0 adds 🚚 ArchiveDurationProvider and fixes tons of issues with the other providers. It now continues executing if a provider fails.
Reply Retweet Like
Bruno Rocha Apr 20
New post: "Avoiding Release Anxiety 1: Block-based UI Testing in Swift"! I'm trying a new format where I share tips on what you can do to reduce that anxious feeling where you're unsure if you're shipping something that works.
Reply Retweet Like
Bruno Rocha Apr 16
Replying to @natanrolnik
Sounds good, will definitely take a look! Thanks!
Reply Retweet Like
Bruno Rocha Apr 16
GoDaddy's support is a complete mess, they assist you by literally asking for your pass/2FA to log in your account... To make it worse I called them because it doesn't let me add my new credit card, and the person asked me for my card info so she could try on her side, wtf?
Reply Retweet Like
Bruno Rocha Apr 16
Just published the first version of SwiftInfo-Reader! You can now convert SwiftInfo outputs into a static HTML page. It's not pretty, but I'm happy to finally have an use for the outputs 😅
Reply Retweet Like
Bruno Rocha Apr 11
Thanks to a community suggestion, SwiftInfo 1.2.0 adds the 💻 Executable Lines of Code provider!
Reply Retweet Like