adambyrtek

I think you are talking about Lyft not Uber.

Tusk might be open source but it's still a client for the proprietary Evernote service, so it's not significantly better according to your criteria.

You're absolutely right, thanks for refreshing my memory :)

Dune II came before both of them, but as far as I remember it wasn't a pure RTS, it had an adventure aspect as well.

This is definitely deliberate, upgrading everybody (almost) at once could work, but would have been a huge risk at their scale. You want to roll out big features like that incrementally so that you can monitor the load, catch any issues early, and give yourself a chance to revert if things go wrong without pissing off the whole world.

I actually prefer QHD screen since it looks great with 2x scaling (and I don't really care about text mode which is only useful for recovery). I have no problems with HiDPI or touchpad after upgrading from the ancient 16.04 LTS that comes preinstalled. I hope that the next edition would come with 18.04 LTS which should offer a much better user experience out of the box.

Dell XPS 13 has build quality comparable if not better than MacBooks, comes with Linux preinstalled, and has an optional high resolution QHD+ screen.

http://www.dell.com/en-uk/shop/laptops-notebooks-and-2-in-1-...

There is no new value created there, it's just transferred from the buyer to the seller (with some being diverted as transaction costs).

When somebody claims that a stock is a "bargain" it's not unreasonable to expect to base that on something more concrete than just a gut feeling.

Respectable sites usually include a list of corrections and changes made to an article after publication.

When it comes to submission titles, HN has a tendency to change them for no obvious reason even if the original title hasn't changed.

I really like how Inbox encourages getting to "inbox zero" (and maintaining it). It makes it very easy to archive things, snoozing emails for later is great, and reminders allow to add some short todos to the inbox where they are less likely to be missed.

Many tiling windows managers like i3 and XMonad have a tabbed layout:

https://i3wm.org/docs/userguide.html#_changing_the_container...

https://hackage.haskell.org/package/xmonad-contrib-0.13/docs...

If that was the case then it wouldn't be anything specific to microservices.

Great article, but I'd like to dispute one point:

> A new version of the subscriptions service may store data in the subscriptions database in a different shape. If you are running both services in parallel, you are running the system with two schemas at once.

Microservices should manage their own separate data stores and communicate with others through a well-defined API. Only then services can evolve independently, and each team is free to change the internals (including schema migrations) without coordinating with everybody else.

Multiple services sharing the same database is the perfect example of the "monolith in disguise" anti-pattern mentioned in the article, with all of the costs of microservices but few benefits.

Then they should constructively respond to these misleading results not suppress publication with legal measures.

Most teams that require pair programming during the interview process don't actually pair on the job. They just use it as a convenient way to assess the candidate in conditions as similar to the real job as possible, and see how they solve problems and collaborate with others.

I suggest to ask your contact at the company about their practices if you're concerned about pairing. They should be happy to answer and would probably appreciate your interest.

> That being said, I'm personally excited about the managed Kubernetes offering AWS recently announced.

Another alternative for managing containers on a cluster of machines is AWS ECS. It has been around for a while and integrates really well with other AWS services (e.g. Cloudwatch, ALB). Unlike Kubernetes the scheduler is proprietary, but the agent running on individual instances is open source.

We've been using ECS for a while together with Terraform for managing the whole infrastructure in immutable and declarative way, and it has been great so far.

mosh[1] provides the buffering you're looking for and some other useful features, at the cost of extra complexity that could lead to other issues (e.g. no scrollback unless you use tmux as well).

[1] https://mosh.org/

Of course you could always do better, but the specific feature mentioned in the parent comment (completing flags for "tar" instead of checking the man page) has been around for ages.

Regarding contextual analysis, the fundamental problem is that command execution relies on a list of strings (argv) with no types or meaning. Each command is responsible for parsing its own arguments, either manually or using a shared library (e.g. getopt). This provides loose coupling and flexibility, but makes introspection really difficult, and features like completions become an afterthought reimplemented in every shell either by special cases for each command or hacks like parsing help messages.

Pretty much any modern shell (bash, zsh, fish, etc) provides command line completion.

I would say yes, since web browsers should prioritise performance and security of their primary use case which is accessing the web. In my opinion extensions are just a nice add-on, not the reason browsers exist in the first place. Most developers understand from their own experience that backwards compatibility while admirable can be very costly to maintain forever.

Like most on this thread, I think that injecting code is a step too far, but I definitely appreciate that you took the time to explain the motivations behind this.

Like pension funds and passive ETFs that are shareholders of most if not all public companies?

That's more or less what ETFs do.

So they paid him to investigate claims they argue are baseless? That doesn't make any sense.

You said yourself that you're a "technical person", so probably not the target audience of this article.

This is supported by GNOME Shell 3.26 which I'm currently running under Ubuntu 17.10.

Well-designed ORMs like SQLAlchemy (and others) are a pleasure to use and make your life so much easier without overreaching and taking over your domain models (in contrast to more opinionated frameworks like Active Record).

Work on real-time ad auctions is definitely technically challenging, but I'm not convinced about the fun part, and I definitely wouldn't describe that as rewarding (unless you mean that in a purely financial sense).

Better languages can help to avoid certain classes of errors, but won't prevent bugs in the business logic of your code, so I'm not sure how this is relevant to contracts.