HN user

chadfowler

1,853 karma
Posts0
Comments24
View on HN
No posts found.
[GET] "/api/user/chadfowler/stories?hitsPerPage=30&page=0": 500 Failed to fetch user stories

For a long time we’ve treated frameworks as the target of software development. But if systems are meant to be regenerated and replaced safely, the real compilation target has to be the architecture itself.

When code becomes cheap to generate but expensive to understand, the most durable systems will be built from implementations meant to die. This series explores architectures where we regenerate rather than maintain.

Wunderlist API 11 years ago

We aren't working on it now since we don't use PHP internally but we'd be happy to support a developer who wants to build support!

Re-read it as a reminder to myself and thought it would be good for people to read on Sunday before starting the work week. :)

The Magic of strace 12 years ago

Oh we used those too, but in this case there were also native libraries. I was a regular user of jad, even sometimes recompiling and replacing stuff (ooooweeee) in production.

A beautiful thing that this demonstrates is that no matter how old a concept is, there's always room to explain it clearly so that those who didn't already understand it have the benefit of finally being enlightened. I learned this many years ago as an author, thinking that my most basic ideas weren't worth writing down. It turns out that what's obvious to one person isn't obvious to everyone else.

Thanks for the reminder and for the clear explanation of how git deploy might work!

Thanks Joren! Great points about opening and closing. Conferences use the word "Keynote" really loosely, but I think they're best when used to open and/or close to set the context and mood for the event.

From the 6Wunderkinder Android team:

When we started developing Wunderlist 2, our product design team came to us with this beautiful layer concept for Wunderlist’s Detail View. Since we strive to create a consistent Wunderlist experience for our users across all platforms, it was very important for us to have the Detail View behave the same way on Android than it does on iOS and the Web.

First, we tried to use existing open source code, but they just didn’t offer the behaviours and quality that we and the design team needed. So, equipped with a big pot of coffee and a few long nights, we worked on what is now SlidingLayer. After the launch of Wunderlist 2 we received a lot of email from Android developers that were interested in the techniques we used for the Detail View element.

It works the same as any other container on Android. For flexibility it extends from FrameLayout, so it’s as easy as to drop it inside of your XML layout and so you can adjust the parameters as usual. You tap to open, rather than sliding and you can place it on the left, right or middle. After opening, you can dismiss it by sliding it away. To make things extra simple, we introduced an auto mode within the parameter that determines which side to stick your view to. For instance setting the gravity of the SlidingLayer to the right in any container or using alignParentRight = true from within a RelativeLayout will automatically stick your SlidingLayer to the right.

We are super happy to be opening it up to the Android Community and hope to see more and more developers getting inspired to use the component in their apps.