rojoca

I found this advertisement from Mercedes interesting: https://i.redd.it/wwxk8nqh88ex.gif

I can't speak for the quality of Mercedes interface (and this is obviously marketing for non-programmers) but LOC seems like an odd thing to be emphasising.

You can always use a VPN, register with a dummy email account, and pay with a prepaid credit card if you're concerned about such things. Alternatively, subscribe to everything so your preferences disappear.

I had the same experience moving from NZ to Canada in 2010. I could not believe how terrible the banking experience was. Everything was so slow. Opening an account, depositing or transferring money. People still writing cheques for everything. Before Canada I'd never had a cheque book and could count on one hand the amount of cheques I had dealt with in my life.

I agree with the general sentiment that someone's technical experience should in almost all cases be able to be presented independent of their political views but I would append to that the following: "but conferences can do whatever they like providing it is lawful".

Usually used for long running queries but sometimes appropriate for this problem is creating a "query" resource via POST after which you have a URI for the results:

  POST /queries
  
  {"query": "..."}
  
  201 Created
  Location: /queries/1001
  

GET the results:

  GET /queries/1001
  
  {"results": ...}

You could optionally return results in the POST response too but I'm unsure whether that strictly conforms to the HTTP spec or not.

Start with a problem, then decide if it can be best solved by a website or an app.

If you sign an agreement with your friend behind your girlfriend's back you're looking out for your own interests. You're in effect controlling or limiting her choice without her knowledge.

Interesting title given that Netflix has just released pricing for their upcoming New Zealand release undercutting the local offering from Spark (formerly Telecom).

My first job was building something like this into sugarcrm circa 2005. It was more of a generic workflow tool and is a great way to automate business process. Not not sure how enjoyable it was for people to come into work, check their taskboard, and find 20 identical tasks on their list of things to do that day though.

It certainly exposes bottlenecks if they weren't obvious already.

I downloaded and installed in about 3 hours but the download kept "failing" and had to be manually resumed from the App Store.

If you watch the linked video above you will see how clever persistent data structures mean that nothing is ever cloned or copied.

> This is important: the really painful part of being stuck in traffic is not, really, the actual amount of time that it takes to get from Point A to Point B. Rather, it’s the “stuck” bit.

I've noticed this tends to not matter so much if you're not the one driving, more so if you're in the backseat. Self-drive cars anyone?

Has anyone made a todomvc implementation using this?

Some people like to run their browser without sending REFERER headers. I know chrome and firefox can both be configured to do so. That would mean these users would not be able to use your site/app. Better to stick with the tried and true method of a random-ish variable that goes into both the form and the cookie with their values being checked against each other on submission.

I don't think it is that unsurprising either, nor do I have a problem with this kind of advertising. My only gripe would be that I believe you can opt-out of targeted gmail ads now so it would appear this is either out of date or inaccurate.

Don't forget that this is Pike's ideal setup. Presumably in this "ideal" the security issues no longer exist and my "setup" is available at any interface I interact with - instantly.

It should be noted that the post explicitly recommends using free/fun to play games and links to a problem gambling site.

To get benefits from testing you really need your team to buy into it. In my experience developers are much more inclined to try things that they had an active part in suggesting or formulating. It's likely your team has some experience or knowledge when it comes to testing. Assuming you are the team leader, talk to them, let them make suggestions, or ask them to look into it and present their own ideas.

I was taught TDD on the job via pair programming and really enjoyed it that way.

In my experience I have found that explicitly passing your dependencies around through constructors or method arguments leads to more robust abstractions. Defining an object as a Singleton from the get-go can lead to its overuse.

If you have to pay the cost of adding a parameter to a method or a constructor you really evaluate whether you need that object in that method in the first place. This doesn't stop you from enforcing a single instance.

I can see this as a useful tool in prototyping. You can create these short DSL phrases to describe the behaviour you want, then implement as much as you need.

The other benefit is the documentation (in DSL form) you get. It's always nice to have concise descriptions of your application's behaviour.

> we've all seen OK/Cancel prompts before

It's interesting to think about common patterns and if they really are in the user's best interest or if a new pattern might offer some benefit. I'm undecided in this case.

When it comes to non-standard button labels, when there are more than 2 options, or on dialogs where the user should think about what they are doing (e.g., actions which cannot be undone) having the most used option last doesn't sound like the worst idea.

I'm not sure about the terms of Apple's in-app purchasing (perhaps someone could elaborate), but can a publisher add a surcharge to the native app, to cover apple's cut, then offer the original (now discounted) price to users who pay through the web app or via a webpage?

I imagine the main reason they moved to PHP5 was not for features but simply because the PHP development team ended support for PHP 4. That means no more security fixes for version 4. This point was mentioned explicitly by WordPress.

WordPress didn't end support until 3 years after PHP 4's end of life. I think that's a more than reasonable amount of time to wait before enforcing an upgrade.

The fact that WordPress does not have any code that benefits from PHP 5 is undoubtedly, in part, due to its extended support for PHP 4.

There is the EFF: https://w2.eff.org/patent/

Taking it a bit further it's often useful to invite criticism. Next time you show off your latest prototype instead of asking "What do you think?" ask "What do you hate about this?". Sometimes your peers are reluctant to criticize; make them feel comfortable to do so.

While not an option for everyone, serving static content from a different domain is another way to avoid this bug.

After riding this train I started to wonder why driverless trains are not more prevalent. It seems so obvious now.

One other tip I got was to make sure you understand your solutions. When you finally resolve a problem it is tempting (albeit sometimes necessary) to move straight on to the next problem without thoroughly understanding what you just did.

Forcing yourself to go over your own solutions, and in particular extracting the steps involved, can really consolidate your knowledge.

This is one of those hard work things.

It seems this is mostly about organizing your application consistently. It's easy (particularly with jQuery) to quickly amass large collections of event handlers which are later consolidated into the logic of an application. This library provides an abstraction to make it easier to switch that process around. Logic/API first; implementation second.

Of course you can still do that with plain jQuery...