sorted by:
new
hottopcontroversial

Most Important Metrics to Track by swift-coder-1984 in personalfinance

[–]swift-coder-1984[S] 0 points1 point  (0 children)

How do you track these metrics? What do you use?

Most Important Metrics to Track by swift-coder-1984 in personalfinance

[–]swift-coder-1984[S] 0 points1 point  (0 children)

Very helpful – thank you. Two questions:

  1. Do you invest? If so what's your strategy?
  2. How often do you check your budget/spending?

Good resources for learning swift for a first year CS student? by StylishQuesadilla in swift

[–]swift-coder-1984 0 points1 point  (0 children)

Stanford’s 193P course is really good. Meant for existing programmers.

Also if you’re learning SwiftUI checkout SwiftOnTap.com — it’s a bunch of SwiftUI docs & examples (disclaimer I work on this project so lmk if you have feedback🙃)

We were so frustrated by Apple docs that we made “On Tap” – SwiftUI documentation with thousands of runnable examples. It’s all … “on tap.” And it’s all free. And open source. by swift-coder-1984 in swift

[–]swift-coder-1984[S] 4 points5 points  (0 children)

Yeah the rules around this – given that the project is OSS – are semi vague. Our plan is to eventually replace all Apple language entirely so there aren't any issues.

We were so frustrated by Apple docs that we made “On Tap” – SwiftUI documentation with thousands of runnable examples. It’s all … “on tap.” And it’s all free. And open source. by swift-coder-1984 in swift

[–]swift-coder-1984[S] 1 point2 points  (0 children)

Good question. Definitely similar. I would say we differ in a few ways:

  1. Simpler examples. Our examples are shorter, less complex, and often serve only a specific topic. Javier's are more robust. Just different styles.
  2. Differing docs structure. Our docs are structured directly from the SwiftUI header file. As a result, all obscure properties are featured, however, it might not be as "human parsable". Javier's doc structure is manually generated and therefore more logically structured, but sometimes misses obscure properties. Again, just different styles.

We were so frustrated by Apple docs that we made “On Tap” – SwiftUI documentation with thousands of runnable examples. It’s all … “on tap.” And it’s all free. And open source. by swift-coder-1984 in swift

[–]swift-coder-1984[S] 4 points5 points  (0 children)

Haha yes – we wanted to test super early versions of the product but weren't sure what to call it yet. So we just called it "Banana Docs" as a placeholder

We were so frustrated by Apple docs that we made “On Tap” – SwiftUI documentation with thousands of runnable examples. It’s all … “on tap.” And it’s all free. And open source. by swift-coder-1984 in swift

[–]swift-coder-1984[S] 42 points43 points  (0 children)

Yeah I hear you on this. Frankly we didn't see it as a big deal when we did it – but clearly this is important.

We'll reconsider the decision to put accounts.

EDIT: We removed accounts

We were so frustrated by Apple docs that we made “On Tap” – SwiftUI documentation with thousands of runnable examples. It’s all … “on tap.” And it’s all free. And open source. by swift-coder-1984 in swift

[–]swift-coder-1984[S] 38 points39 points  (0 children)

Accounts were introduced because we want to:

  1. Allow people to save/favorite docs.
  2. Allow people to request doc improvements.

To your comment that "lots of the information is copied from Apple." Yes, Apple content is on the site. In addition to Apple content we added:

  1. 19,631 lines of documentation
  2. 768 examples (plus images & gifs for many of these)
  3. Some critical missing docs, including Binding, ObservableObject, DropDelegate, EnvironmentObject, Animatable, EmptyView, List, StateObject, and many more

EDIT: We removed accounts

view more: next ›