Twitter | Search | |
Mischa Hildebrand
Physicist, Developer and Journalist.
143
Tweets
204
Following
112
Followers
Tweets
Mischa Hildebrand retweeted
Lulu Cheng Feb 17
I got 99 tabs but I generally know where things are
Reply Retweet Like
Mischa Hildebrand Feb 17
How to name your hotel rooms so that no one can remember his/her room and gets completely lost when trying to find it. Great example for in . Otherwise a really awesome hotel:
Reply Retweet Like
Mischa Hildebrand Feb 14
Replying to @BObereder
However, I am working on a blog article to put the key points of my talk in a written format. It'll still take some time but you'll find it here: .
Reply Retweet Like
Mischa Hildebrand Feb 14
Replying to @BObereder
Happy to hear you liked the talk! I won't publish the slides (yet) as I would like to use (most of) them for a conference talk soon and because many of the slides would look messy due to the animations.
Reply Retweet Like
Mischa Hildebrand retweeted
How I Built This Feb 12
As a long-distance runner at school, James learned that almost everyone gets tired and feels like giving up at the same time....and that's exactly when you have to go the extra mile.
Reply Retweet Like
Mischa Hildebrand retweeted
Spits 2.0 Feb 8
The German opposite of 'umfahren' (running something over) is 'umfahren' (drive around something). Good luck mastering this language.
Reply Retweet Like
Mischa Hildebrand Feb 8
Reply Retweet Like
Mischa Hildebrand retweeted
intive Feb 7
Calling all & Developers and enthusiasts! If you are in Munich tomorrow and are up for learning some useful tricks & tips in development, drop by and join 's Swift Meetup VIII speakers. More info:
Reply Retweet Like
Mischa Hildebrand Jan 31
It’s another Interface Builder bug: You can make 0 line labels work in a stack view when you set their preferredMaxLayoutWidth to a fixed value. But that’s an ugly hack and not dynamic at all. It’s really frustrating.
Reply Retweet Like
Mischa Hildebrand Jan 31
Thank you! 😉
Reply Retweet Like
Mischa Hildebrand retweeted
Paul Hudson Jan 20
All three match – how many ways can you think of to make this true in Swift? You’ll learn by trying 👍
Reply Retweet Like
Mischa Hildebrand Jan 8
Replying to @chriseidhof @objcio
I've created a fork of your repo with a full code example: . You still have separation of concerns and testability but you gain increased readability, I think.
Reply Retweet Like
Mischa Hildebrand Jan 8
Replying to @chriseidhof @objcio
If you take this one step further, you can even do this:
Reply Retweet Like
Mischa Hildebrand Jan 8
Replying to @chriseidhof @objcio
If you spilt it in two parts – 1. the creation of the flow layout with setting up its parameters and 2. the calculation of the frames – the intent gets a lot clearer.
Reply Retweet Like
Mischa Hildebrand Jan 8
Replying to @chriseidhof @objcio
Generally, I think the last step to remove the `FlowLayout` struct is one step too much. It's difficult to express the intent clearly in code if you all put it in a single function.
Reply Retweet Like
Mischa Hildebrand Jan 8
Replying to @chriseidhof @objcio
If we stick to the current logic I'd keep the `flowLayout(...)` function inside the struct `FlowLayout` and then rename the function to `frames(forSizes: [CGSize], inContainerWithSize size: [CGSize])`.
Reply Retweet Like
Mischa Hildebrand retweeted
Chris Strider Jan 4
This is the best thing you'll see all day. 😍🐕 This Dog figures out how to carry his sled up the hill in order to sled for hours & hours & hours.
Reply Retweet Like
Mischa Hildebrand Jan 6
Replying to @objcio
I really love the idea and the way you refactor the code! However, I think the function naming could be improved: It's counter-intuitive for me that `flowLayout(...)` returns an array of frames and not a layout, or that `add(...)` returns a frame rather than a sum.
Reply Retweet Like
Mischa Hildebrand Jan 5
Great article with ideas on how to be more without torturing yourself too much 😉 by :
Reply Retweet Like
Mischa Hildebrand Jan 3
Replying to @khaledealy
Thanks! Glad it helped. 😃
Reply Retweet Like