Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add new post #28

Merged
merged 2 commits into from Mar 25, 2017
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
131 changes: 131 additions & 0 deletions _posts/2017-03-25-swifty-week-18.md
@@ -0,0 +1,131 @@
---
layout: post
title: Swifty Week 18
date: 2017-03-25 12:00:00 +0900
tags: swiftyweek
comments: false
---

This is the **#18** article. I started to contribute the awesome tool called [Marathon](https://github.com/JohnSundell/Marathon). It's a command line tool that manages scripts in Swift. If you don't know it, check it out:)
Thanks @JohnSundell!

<br>

---

### Article

#### [Swift enums with associated values defaults](http://ilya.puchka.me/swift-enums-with-associated-values-defaults/)

> In Swift enums are much more powerful than we got used to in other languages. One of the features that makes them more interesting to use is associated values - values that each instance of enum case can carry along with it. We can not have stored properties in the enum, so associated values is basically the only way to store additional data with enum value. Creating an enum value with associated value has a similar semantics as a method call. The difference is - we can not define defaults for parameters which represent associated values.

<br>

#### [Swift: Why You Shouldn’t Use Default Implementations in Protocols](https://www.natashatherobot.com/swift-use-default-implementations-protocols/)

> I think adding default implementations to protocols should be considered very very carefully. The default needs to be something that is consistent and is the default for most cases, so if someone forgets to implement it (because the compiler won’t complain), it’s most likely not a big deal.

<br>

#### [On Comments](http://khanlou.com/2017/03/on-comments/)

> My perspective on comments comes from two facts: 1) Comments don’t compile. 2) Comments are usually a subdued color in your syntax highlighter. Because they don’t compile and because they fade away from sight, it’s very easy to ignore them as you make changes to the code. If you make changes and don’t update the comments, you end up with a comment that doesn’t accurately reflect the content of code.

<br>

#### [Swift: When to use guard vs if](https://www.natashatherobot.com/swift-when-to-use-guard-vs-if/)

> One thing I’ve noticed recently in my code-base is that I tend to default to guard vs if. In fact, whenever I write an if statement, I facepalm myself and change it to a guard without thinking much.

<br>

#### [Variable Height Table View Header](https://useyourloaf.com/blog/variable-height-table-view-header/)

> Making a table view header that automatically adjusts its height to allow its contents to fit should not be so hard. Unfortunately it is a problem that has been with us for a number of years which means much of the advice on how to do it is out of date. This is what works for me for both iOS 9 and iOS 10.

<br>

---

### Slide

#### [Mixins over Inheritance — AppDevCon'17 by AliSoftware](https://speakerdeck.com/alisoftware/mixins-over-inheritance-appdevcon-17)

> In this talk you’ll discover what Mixins & Traits are, and how they can help you solve some interesting problems and make your architecture more flexible. Using some concrete examples, we’ll see also how these can be used in everyday challenges.

<br>

#### [My Open Source Journey by Juanito Fatas](https://speakerdeck.com/juanitofatas/my-open-source-journey)

> at OedoRubyKaigi 06

Talk at Ruby conference, but it looks useful for Swift developer!

<br>

---

### Github

#### [onevcat/FengNiao](https://github.com/onevcat/FengNiao)

> A command line tool for cleaning unused resources in Xcode.

<br>

#### [uraimo/SwiftyGPIO](https://github.com/uraimo/SwiftyGPIO)

> A Swift library to interact with GPIO/SPI/PWM on Linux/ARM boards (RaspberryPi, BeagleBone, CHIP, etc...)

<br>

#### [dbukowski/DBDebugToolkit](https://github.com/dbukowski/DBDebugToolkit)

> Set of easy to use debugging tools for iOS developers & QA engineers.

<br>

---

### Random

#### [There are 5 Points on the Scale of Remote Working. Here’s Where We Fall at Buffer.](https://open.buffer.com/remote-working-scale/)

> I’ve recently found myself reflecting a lot on being a distributed team and the nature of a company where the team works from remote locations to accomplish our work.

<br>

#### [Tell Me When It Closes](https://tellmewhenitcloses.com/)

Get 1 email when an issue or PR closes (instead of getting a million emails by subscribing)

<br>

---

### Podcast

#### [#72: Selling Apps](https://www.relay.fm/radar/72)

> Building apps with acquisition in mind, calculating your app's valuation, and what to expect in a sale.

<br>

#### [03: Source Stability (What is a Source Breaking Change?)](https://spec.fm/podcasts/swift-unwrapped/61851)

> Every Swift developer who has migrated code bases from Swift 1.x to 2.x, or even the more tedious 2.x to 3.x knows the pain of migrating to new Swift versions.

<br>

---

I found the filter function in Xcode console.

![Console Filter]({{ site.url }}/assets/console_filter.png)

If you have any questions and feedbacks about a kind of new Swifty week, feel free to ask me :+1:
You can catch me on [Twitter](https://twitter.com/pixyzehn) and [Github](https://github.com/pixyzehn).

Have a lovely week <3


Binary file added assets/console_filter.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.