Many programmers and designers with little startup experience are colliding with the "business folks" at a company in the beginning, since the latter always are optimising for financial success. The former are usually optimising for correctness, order, and simplicity in all their forms. In a startup's case, its survival is hanging on financial success (VC, profitability – in one way or another), so the former group has to release their desire for correctness, and get on the train. It's painful, but totally doable.
Psst! There's more stuff at my personal blog too!
So I started going to the gym and wrote about my initial experiences in FAQ form, since it's easier writing dialogue as opposed to ranting by myself.
For every creator, publishing your work for the masses is both exhilarating and mortifying. For a startup, you're dying for feedback and usage, in order to boost your metrics, and if you're charging money, it even becomes more serious. In one way or another, you're in for interacting with users/customers (I'll use the former term in this post).
The White Duck was, on the surface, lonely. She was not vicious, stupid, or bad in any way. She was just different from the rest of the ducks. It is not known whether it was the colour of her feathers, or lack thereof, who set her apart. Even though I am skeptical to that, it surely didn't strengthen her case.
One thing I've noticed during my past half ish year of traveling outside of Europe is the difference in how young people interact and socialise with each other, compared to the customs in my native country Sweden.
A short ode to the ocean.
In Lookback, we've had the notion of being able to work remote as a baseline since day one. Here are some of my thoughts on the deeper end of working remote, on personal levels.
There is a thing that every developer has to do at some point – ship. By ship I refer to the act of deploying, pushing the button, publishing your work for a wide mass. This act is central in our industry: blog posts like this one have been written, there have been talks on the subjects, and methodologies (like Continous Delivery, Continous Integration) invented to deal with the pain points associated with shipping. Hell, there are even roles (devops, sysops) for easening the burden of moving code from one system to another. Why, oh why are we conscious and sometimes afraid of shipping our work?
I'm attending WWDC 2015, and during the web development session, Apple's Safari team showed off what's new in Safari 9. It includes iOS style effects, such as backdrop filters and scroll snapping with CSS, ES6 updates, other CSS niceties.