Long story short we now live in Manhattan, New York.
Why move again? Because Natasha got an offer she couldn’t refuse. More from her soon.
So once again we packed, but this time also sold the non easily movable stuff like our espresso machine and although tiny, non packable, Fiat 500.
About 7 days before departure I misplaced our sons recently renewed passport and we realised that we had the wrong visa. Before that, July was planned to be mostly vacation but also apartment hunt. The vacation part was replaced by visa hacking and the apartment hunt took more effort than expected.
Mid August the apartment hunt was over and we are now in the process of making the apartment livable. We can confirm that it is the landlords market.
In July and August we lived various places in Williamsburg, Brooklyn, which we all liked, but I have since leaving Denmark wanted to live near Central Park, mostly for the kids sake. The place we have found is on the Upper West Side near Central Park.
The visa hacking included trips to Cape Cod in Massachusetts and Prévost in beautiful Quebec, Canada, so it wasn’t all just hard work.
I even got freelance work offered, but their approach is to do many startups fast without caring about quality, which isn’t how I work, so I’m still looking. I haven’t had time to communicate nor attend meetups yet, but I’m looking forward to meet the NY tech scene.
It’s been hectic and we all look forward to fully enjoy the city.
Ever since 2000, where I spent hours of hours optimizing the relatively small server Hewlett-Packard had sponsored my bootstrapped startup at the time, Eksperten, I’ve speculated in going all in on static pages.
I do not use WordPress but I assist some small businesses with theirs, and the hassle of making it fast and keeping it and it’s plugins up to date makes me want to reboot my other startup Webalogic, where content is edited at webalogic.com then pushed to the clients server via FTP. Webalogic have served clients since 1998, and while it needs a makeover, the idea is simply that there is no sanity in having a webserver call a script that calls a database several times to fetch text and then produce HTML that the webserver will send to the user. Why not just build the HTML the microsecond after the content was edited and utilize the powerful caching mechanism built into the webserver. If you do need dynamic pages, Webalogic can output files as scripts such as PHP, ASP etc.
There are many ways to build static pages. One I and many others use is GitHub Pages, which is great for hackers.
Here are the three advantages of static content I see as the most important ones:
To me, this is sad news as I had high hopes for Parse as the groundstone to build apps or even rewrite cluttered ones onto.
My reason to recommend services like Parse is that most apps need to be fast and utilize real time look and feel. To do that the frontend should intelligently be fed with data from the backend so that it can be shown instantly when the user requests it. With tools like Backbone most logic can be pushed to the frontend, thus the backends job is to be fast, reliable and at a bare minimum make it easy for the frontend to store and obtain data.
Since I heard about Parse I have recommended it to the startups I work with and others who would like to get into programming. I would still recommend Parse if your focus is on getting into building web or mobile apps as in that case you need a simple way to store data and should only focus on the client.
For a business I wouldn’t use Parse. Facebook is a behemoth and will most likely stick around for a very long time, but their focus isn’t Parse but to nurture their money machine, the timeline. Besides Facebook’s lack of focus on making Parse a sustainable business your app is most likely interested in social network integrations other than Facebook and as important as that is, I wouldn’t trust Facebook.
Luckily there are alternatives.