749 karma · joined January 6, 2017
Technically a year is the limit IIRC but I have heard of issues with even six months away. It's at the discretion of the immigration official as to what constitutes abandonment of your permanent residence.
I haven't followed the development with anything more than a casual, occasional glance and accompanying eye-roll. I doubt I'll ever see anything come of it. A shame, not necessarily a surprise.
I'm fully aware and prepared that kickstarting a game confers no guarantee, but the feature creep in this case is staggering. I suspect that if this case were to succeed they'd suddenly find themselves underwater with all the pledges clawed back once the precedent was set.
But they have three portable product lines: the MB, and Air and the Pro. Surely the point of that is to allow them to differentiate? It seems strange that "thin and light" is the priority above all others, for all three.
I'd happily sacrifice a couple of millimetres and a few ounces of my 2016 MBP to a return to the 2015-era keyboard.
"For there was no doubt in his mind that in a world congested to overflowing with girls Eve Halliday stood entirely alone."
I realised a while ago that my main issue was with nebulous tasks -- that is, the more concrete, defined, and _meetable_ a task was, the less trouble I had with it. So I started to break down large tasks, which never got started much less finished, into smaller ones, in the same way you might break a scrum-poker 20-pointer into a bunch of 3s.
You want to go from this:
- I should really write [some great app idea]
To this:
- I'll make a list of technologies that I want to use
- I'll read the docs, like a book, for the ones that are new
- I'll write a single api endpoint
- I'll flesh out the api for the rest of a feature
- I'll MVP a UI for that one feature, without any concern for design
- etc.
In my case, a combination of the size of and amount of ambiguity in a task is inversely proportional to the ability I have to both get it underway and get it finished.