Bockit

I don't think people think they're arrogant. I think people find them unsuited to the task at hand. If you felt that way already, this incident would have been another nail in the coffin.

It all comes down to the idea that if you the user have concerns with the app, you the user can take the approrpriate measures to verify, given enough time.

On the topic of github emails, I'd love the ability to set an email for notifications on a per repository, instead of just per organisation basis.

No, you don't.

Whether or not you choose to go ahead with something that will offend people is up to you, but you don't get to choose whether it will or won't affect people.

In Sydney, our largest cinema chain isn't even showing it!

A case where it would make sense, if bitcoin ends up worth nothing. It doesn't matter if they're scarce when they're still worth nothing.

I hope it doesn't end up so, luckily I'm not in a position where I need to try and work it out!

> I am someone who reads the man pages and does a lot of experimentation before turning to a Q&A site

I feel similarly. I'm uncomfortable asking for help on stackoverflow, a mailing list or IRC if I haven't tried everything I could think of to work something out. I always have this[1] in mind when I do end up writing a question. I almost think it should be required reading.

[1]: http://www.catb.org/~esr/faqs/smart-questions.html

I think there is an argument to be made that newer developers, who might not be familiar with hiring practises, and see this job from Penny Arcade might leave thinking that's the norm.

That's a pretty fair point about the CSS url rewriting, it's possibly the kind of thing you can fix with a browserify transform, but iffy and as you say component is doing it already.

What do you think of browserify coupled with transforms providing html templates[1] and css inclusion[2].

[1]: E.g., https://npmjs.org/package/browserify-jade

[2]: E.g., https://npmjs.org/package/stylify

http://run.south.im/tech for an explanation of how it was made.

It is part of the constitution. What they're referring to is the events of 1975 when Gough Whitlam and the Labor party government failed to pass a budget by the hostile senate, leading to the dissolving of parliament by the Governor General.

Basically the Governor General is the Queen's official representative in Australia and officially our head of state. They have the power in specific circumstances to dissolve parliament and force an election. One of those circumstances is if the government fails to legislate a budget. It's complicated how the scenario occurs, but it happened, the powers of the governor general were exercised and a new election was held.

In this case the scenario is only possible because we recognise a power higher than our own parliament, that of the Queen. The USA doesn't have that but perhaps an alternative system could be worked out (if it's even desired, I think it's a useful thing to have).

[1]: http://en.wikipedia.org/wiki/1975_Australian_constitutional_...

I know there is probably an actual definition of the 80/20 rule somewhere, but here's my interpretation, which I think gels with the article. 80% of the work is done quickly , which is the absolute core stuff, with 0 polish and full of edge-case data and interface bugs. Then the last 20% of the work takes roughly equal to the first 80%. The percentages have nothing to do with actual work completed or time spent, rather how complete it looks to the client/your boss/someone with no details of the technical implementation.

And that's only to get to 1.0. Some of these features would be unnecessary for launch but should be added post-launch, e.g., the editor imo.

EDIT: Looking it up there is an 80-20 rule that I think is in a similar vein but if applied properly to this situation would say that 80% of the work exists in 20% of the features.

Which may even be true sometimes.

When you say things like "realizing how large the universe is", "how meaningless life is", do you really mean that your mental state is impacted by the answers to these questions/implications of these realisations? How does it affect you?

I ask because while the ideas are interesting to me, they have always seemed fairly irrelevant. Sure, the universe is huge, but I don't think knowing that is going to change me. The way I see it, it has no impact on the way I live my life and I can't see anything I do having an impact on that.

I mean the questions genuinely, I realise that not everyone sees things the same way.

Back up for me.

Wow. Because this surprised me so much, I just found out that if you open up a node REPL and type 'hello'.blink() you get '<blink>Hello</blink>' returned. So I guess it's an ES thing and it boggles my mind.

I was trying to find the ES standard where it's specified but I'll settle for this[1] instead. Interestingly enough you have quite a few HTML wrapping functions as part of the spec.

[1]: http://javascript.spec.whatwg.org/#string.prototype.blink

I use a similar one for OSX, "DaisyDisk"[1].

[1]: http://www.daisydiskapp.com

We've done this for a lot of data vis work. Clients have access to a cms which lets them stage and publish their data. Doing so puts JSON files on s3 where we also serve the site. There are some trade offs, sometimes you miss having that rest api, but you also gain a lot too.

If I were to guess, I'd say operation based synchronisation is based on syncing user actions and then executing them on the other side to catch up. E.g., user deleted record 23. User added a record with this data. User changed this field to be this new value.

I think there is room for a distinction between saving my own skin, and making sure that even if I am killed the information gets out.

That went from "Oh, another article about the parts of a URI" to "wow..." very quickly. The path parameters were kind of neat, I was under the impression ; could be used instead of & and was only for query string parameters (Didn't even know path parameters were a thing).

I was helping a designer-only friend of mine with the implementation of a basic website theme. After an hour of trying to talk them through how to use the github app (let alone git command line) I gave up and we just used dropbox.

The point being, sadly, I think that we're a ways off before the average non-technical person is comfortable using git.

I wonder how we would have reacted if rather than spacing all these out, they batched them up an did one big announcement with plans for all lines being discontinued. Quick and clean sort of deal.

If it works how I hope it does, I might have a compelling reason to use LESS instead of SASS.

I think the barrier you describe has helped lead to the phenomenon of claiming 'I was just trolling' or some variation of that comment when people are called out on inappropriate behaviour on the internet.

In the week I do 7.5 hours a night. 9:30 to 5am. I find I wake up feeling best if I get sleep in blocks of 1.5 hours (with a bare minimum of 4.5) so depending on circumstance I do 6 hours some nights (go to bed later) or 9 if I need to catch up some sleep (wake up later).

I find that consistently getting 6 hours is survivable, but if I do it for too long I feel quite sluggish mentally.

On the weekends the strict schedule goes out the window. I go to bed when I get home or if its a night in when I'm tired, and wake up whenever it feels right.

I think he was referring to those instances where you have something which as far as you can tell at the moment should be a certain height but inexplicably (at the moment, because you need it fixed now!) has this weird margin underneath it. With a quick look at the web inspector and your code you can't work out where it's coming from so in the interests of fixing a problem now, you might `overflow-y:hidden` it with the intent to come back later.

That when we're developing, you edit a sass file, and when you request the CSS file it compiles the SASS to CSS before serving the file. It has been a little while since I set it all up but I think for the SASS example I've made a gist[1] showing the settings you need to make it work. If I recall correctly the key bit is using the .scss as the source file. Then, in production make sure to set `PIPELINE = True` to stop compiling per request.

[1]: https://gist.github.com/Bockit/5408958

Would you mind expanding on the issues you have with pipeline? I use pipeline at the moment and beyond a couple of small things (mainly working with vendor apps) I'm really happy with it, but I'm open to the idea that it's because of what I don't know than because it solves every problem.

Specifically for me, pipeline fits into django's collectstatic way of doing things. And because of this it works fantastically with django-storages as well. My projects are set up so that `python manage.py collectstatic` trawls all my apps static folders, compiles everything if required (r.js, sass) and uploads any changes to an S3 bucket. And in development it compiles over the wire (except r.js, we let requirejs do the async loading thing in development).