Twitter | Search | |
Rob Napier
Swift and Go. Love 'em both. They make me mad in completely different ways. Infosec as required.
13,755
Tweets
353
Following
6,269
Followers
Tweets
Rob Napier retweeted
Ben Sandofsky 13h
Replying to @sandofsky
“If you hire a contractor to do a job, they just do the job. They don’t argue about what’s technically perfect.” The good ones do. Otherwise you waste months battling with the city over permits.
Reply Retweet Like
Rob Napier 12h
Replying to @sandofsky
Oh good grief. My contractor pushes back on me all the time, and has more than once said that he's unwilling to do something I asked for because the quality won't be to *his* expectations. And that's why I hire him again and again.
Reply Retweet Like
Rob Napier Apr 18
Replying to @DuncanDaHusky
We’ve all missed you so much. Thanks for such a great night, and I hope to see you again soon!
Reply Retweet Like
Rob Napier Apr 17
I most need to come to conferences is for conversations like I had with where I’m forced to think about things I haven’t before. I’ve focused on diversity of speakers without thinking much about diversity of attendees. But also, 1:30 and go to sleep! (And thanks.)
Reply Retweet Like
Rob Napier retweeted
Mark Dalrymple Apr 16
Replying to @davedelong @bSr43
is an amazing tool. Love it.
Reply Retweet Like
Rob Napier retweeted
Aaron Douglas Apr 16
Today took my brain, flattened it, removed the empty space, and mapped it to .... and I can't even think enough to finish a quippy functional Swift joke.
Reply Retweet Like
Rob Napier Apr 16
Replying to @ryanwils @_Caro_N
Absolutely. But adding just three lines rather than one would make most of the issues go away. It can even swizzle if I ask for it. The problem is if I don’t want exactly what you default to, it’s hours of searching forum posts and experimenting. Classic easy/simple. Less magic.
Reply Retweet Like
Rob Napier Apr 16
Replying to @ryanwils @_Caro_N
But most of all it’s about trust. I need to know exactly what information FB is collecting about my users, and I need an easy way to stop that collection. Currently I don’t feel I can trust the service, so the features don’t really matter.
Reply Retweet Like
Rob Napier Apr 16
Replying to @ryanwils @_Caro_N
I don’t think docs are the answer. Configuration is just too complex. I should be able to just pass a config object with no magic files. Default config should be to do less, with single method calls to turn on common configs, not documents on how to turn things off ad hoc.
Reply Retweet Like
Rob Napier Apr 16
I don’t want a “does everything” solution particularly. I’d rather vendors do something well. I’m using Instabug now (recommend is too strong a word, but best I’ve found). I like my analytics simple, server based, and coarse. I don’t particularly like A/B testing.
Reply Retweet Like
Rob Napier Apr 16
It’s hard to say about stability. Crashlytics definitely had stability problems, which is why we had to leave it, but I don’t know if swizzling is any kind of cause. My problem with the swizzling is it’s done outside my control, and it’s hard to stop it.
Reply Retweet Like
Rob Napier Apr 16
Replying to @ryanwils @_Caro_N
Swizzling: maybe bad …that I didn’t ask for explicitly: bad …with poor docs on how to stop: really bad …and difficult to know stopping worked: horrible …for a feature I didn’t want: get out of my app. I shouldn’t be forced to take Analytics to get Push Notifications.
Reply Retweet Like
Rob Napier Apr 16
Replying to @taquitos @_Caro_N
The point is the analytics. That’s how they give the service away for free. If they can’t spy on your users, what pays for the product?
Reply Retweet Like
Rob Napier Apr 16
Replying to @bgannin @_Caro_N
Instabug. It’s not as good. I’m sorry for that. But it’s an honest service rather than spyware.
Reply Retweet Like
Rob Napier Apr 16
Replying to @sharedRoutine @_Caro_N
I found that disabling it didn’t necessarily fully disable it. Try to fully turn off analytics. It’s…difficult.
Reply Retweet Like
Rob Napier Apr 16
Replying to @_Caro_N
It’s a horrible implementation by Firebase, and very difficult to get rid of if you don’t want it. Firebase is probably the most invasive framework I’ve ever worked with, and I no longer recommend it to clients because of that. All to save a few lines of simple, clear code.
Reply Retweet Like
Rob Napier Apr 14
Someday I will type Result<X, Error> rather than Result<X> on the first try… But today is not that day.
Reply Retweet Like
Rob Napier retweeted
Joe Groff Apr 14
It's also something that would be superseded by a general enum feature to ask for a payload as an optional
Reply Retweet Like
Rob Napier Apr 14
Replying to @nicklockwood @owensd
😂 I can definitely see how Result could bikeshed to death… the following feels so obvious to me that I’m probably missing the ways that others thought were just as obvious. extension Result { var failure: Failure? { … } } But minimizing surface area was probably wise.
Reply Retweet Like
Rob Napier Apr 14
Replying to @krzyzanowskim
Yeah, it’s not bad, but requires a “return nil” at the end. In my case I want to pass the error onto another function, so “return” isn’t convenient.
Reply Retweet Like